Comments on: Deploying Internal Enterprise Application for iPhone http://iphonecto.com/2009/09/09/deploying-internal-enterprise-application-iphone/?utm_source=rss&utm_medium=rss&utm_campaign=deploying-internal-enterprise-application-iphone iPhoneCTO is the authority on iPhone in the enterprise. You will find enterprise & business application reviews, news, editorial and best practices for deploying and administering iPhones in corporate and small business environments. Wed, 18 Jan 2012 14:29:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Skmic's Blog http://iphonecto.com/2009/09/09/deploying-internal-enterprise-application-iphone/comment-page-1/#comment-968 Skmic's Blog Thu, 06 Jan 2011 12:02:19 +0000 http://iphonecto.com/?p=2495#comment-968 [...] Deploying Internal Enterprise Application for iPhone | iPhoneCTO (tags: iPhone Deployment) [...] [...] Deploying Internal Enterprise Application for iPhone | iPhoneCTO (tags: iPhone Deployment) [...]

]]> By: Challenges in developing an app for Android | Enterprise Mobility iPass Blog: Smarter Connections http://iphonecto.com/2009/09/09/deploying-internal-enterprise-application-iphone/comment-page-1/#comment-945 Challenges in developing an app for Android | Enterprise Mobility iPass Blog: Smarter Connections Fri, 08 Oct 2010 04:03:49 +0000 http://iphonecto.com/?p=2495#comment-945 [...] apps and profiles, which is easier with Android (and like Windows, as discussed above), than through the Apple process. Tags: Android  Print This Post [...] [...] apps and profiles, which is easier with Android (and like Windows, as discussed above), than through the Apple process. Tags: Android  Print This Post [...]

]]> By: Quora http://iphonecto.com/2009/09/09/deploying-internal-enterprise-application-iphone/comment-page-1/#comment-941 Quora Sun, 26 Sep 2010 03:17:30 +0000 http://iphonecto.com/?p=2495#comment-941 <strong>Can I develop for iPhone using C#? What tools do I need to get started?...</strong> Your corp gets a provisioning profile from Apple and apps get installed onto the corps iOS devices by dragging the .app file into the users iTunes or using the iPhone Configuration Utility to install them. See page 65 of http://manuals.info.apple.com/e... Can I develop for iPhone using C#? What tools do I need to get started?…

Your corp gets a provisioning profile from Apple and apps get installed onto the corps iOS devices by dragging the .app file into the users iTunes or using the iPhone Configuration Utility to install them. See page 65 of http://manuals.info.apple.com/e…

]]> By: Ian Kynnersley http://iphonecto.com/2009/09/09/deploying-internal-enterprise-application-iphone/comment-page-1/#comment-895 Ian Kynnersley Tue, 27 Jul 2010 15:24:53 +0000 http://iphonecto.com/?p=2495#comment-895 No, I haven't found a way to do this. My proposal for this client was just to provide the app through the app store but to lock it down with a password screen. Not ideal. No, I haven't found a way to do this. My proposal for this client was just to provide the app through the app store but to lock it down with a password screen. Not ideal.

]]> By: PV http://iphonecto.com/2009/09/09/deploying-internal-enterprise-application-iphone/comment-page-1/#comment-874 PV Wed, 30 Jun 2010 00:54:07 +0000 http://iphonecto.com/?p=2495#comment-874 I'm wondering the same thing as well... I haven't find an answer to this yet... have you?<br>I would like to use the Enterprise Developer license to install applications on our best client devices. I'm wondering the same thing as well… I haven't find an answer to this yet… have you?
I would like to use the Enterprise Developer license to install applications on our best client devices.

]]> By: kpopper http://iphonecto.com/2009/09/09/deploying-internal-enterprise-application-iphone/comment-page-1/#comment-784 kpopper Wed, 21 Apr 2010 21:54:01 +0000 http://iphonecto.com/?p=2495#comment-784 Do you think it would be possible (and indeed permitted) for a company to use the Enterprise Developer license to manually install a given application on its customers' devices?<br><br>Say you own a business and your customers spend a lot of money with you, you might want an app that you can give them as a thank you or as a value add but that you don't want generally available on the App Store.<br><br>I realise there are other ways to restrict access to a freely-available app but if you have the means to easily install an app manually, it would make life much easier (and the app cheaper to build).<br><br>Thanks Do you think it would be possible (and indeed permitted) for a company to use the Enterprise Developer license to manually install a given application on its customers' devices?

Say you own a business and your customers spend a lot of money with you, you might want an app that you can give them as a thank you or as a value add but that you don't want generally available on the App Store.

I realise there are other ways to restrict access to a freely-available app but if you have the means to easily install an app manually, it would make life much easier (and the app cheaper to build).

Thanks

]]> By: kpopper http://iphonecto.com/2009/09/09/deploying-internal-enterprise-application-iphone/comment-page-1/#comment-694 kpopper Wed, 21 Apr 2010 17:54:01 +0000 http://iphonecto.com/?p=2495#comment-694 Do you think it would be possible (and indeed permitted) for a company to use the Enterprise Developer license to manually install a given application on its customers' devices?<br><br>Say you own a business and your customers spend a lot of money with you, you might want an app that you can give them as a thank you or as a value add but that you don't want generally available on the App Store.<br><br>I realise there are other ways to restrict access to a freely-available app but if you have the means to easily install an app manually, it would make life much easier (and the app cheaper to build).<br><br>Thanks Do you think it would be possible (and indeed permitted) for a company to use the Enterprise Developer license to manually install a given application on its customers' devices?

Say you own a business and your customers spend a lot of money with you, you might want an app that you can give them as a thank you or as a value add but that you don't want generally available on the App Store.

I realise there are other ways to restrict access to a freely-available app but if you have the means to easily install an app manually, it would make life much easier (and the app cheaper to build).

Thanks

]]> By: kenny's me2DAY http://iphonecto.com/2009/09/09/deploying-internal-enterprise-application-iphone/comment-page-1/#comment-683 kenny's me2DAY Thu, 15 Apr 2010 07:50:54 +0000 http://iphonecto.com/?p=2495#comment-683 <strong>케니군의 생각...</strong> 이용석 아이폰 앱 in-house 개발 및 배포에 대한 이해... 케니군의 생각…

이용석 아이폰 앱 in-house 개발 및 배포에 대한 이해…

]]> By: craikpyke http://iphonecto.com/2009/09/09/deploying-internal-enterprise-application-iphone/comment-page-1/#comment-561 craikpyke Thu, 12 Nov 2009 01:27:30 +0000 http://iphonecto.com/?p=2495#comment-561 apologies - I hadn't noticed your comment... As with any outsourced development, you require a solid NDA and legal contract/agreement between your company and the developer company. You should ensure that all documentation and software is properly assigned to your company in terms of ownership - whether or not it's ever launched as "generally available". Make sure you protect yourself from agreements where IPR isn't assigned until the application is published. Also, be aware that many designers may demand a higher rate or some other compensation for immediate assignment of IPR (anecdotal note: I'm aware of an arrangement where the designer assigned IPR only after payment in full was received. The App was published to the AppStore under the designer's development certificate, not the contracting companies. This created a problem whereby the designer pulled the application from the store and withheld the documentation and source when the net-payable terms weren't satisfied. It was all worked out in the end, but it created a bit of a scary moment for the contracting company). apologies – I hadn't noticed your comment… As with any outsourced development, you require a solid NDA and legal contract/agreement between your company and the developer company. You should ensure that all documentation and software is properly assigned to your company in terms of ownership – whether or not it's ever launched as “generally available”. Make sure you protect yourself from agreements where IPR isn't assigned until the application is published. Also, be aware that many designers may demand a higher rate or some other compensation for immediate assignment of IPR (anecdotal note: I'm aware of an arrangement where the designer assigned IPR only after payment in full was received. The App was published to the AppStore under the designer's development certificate, not the contracting companies. This created a problem whereby the designer pulled the application from the store and withheld the documentation and source when the net-payable terms weren't satisfied. It was all worked out in the end, but it created a bit of a scary moment for the contracting company).

]]> By: craikpyke http://iphonecto.com/2009/09/09/deploying-internal-enterprise-application-iphone/comment-page-1/#comment-539 craikpyke Wed, 11 Nov 2009 23:27:30 +0000 http://iphonecto.com/?p=2495#comment-539 apologies - I hadn't noticed your comment... As with any outsourced development, you require a solid NDA and legal contract/agreement between your company and the developer company. You should ensure that all documentation and software is properly assigned to your company in terms of ownership - whether or not it's ever launched as "generally available". Make sure you protect yourself from agreements where IPR isn't assigned until the application is published. Also, be aware that many designers may demand a higher rate or some other compensation for immediate assignment of IPR (anecdotal note: I'm aware of an arrangement where the designer assigned IPR only after payment in full was received. The App was published to the AppStore under the designer's development certificate, not the contracting companies. This created a problem whereby the designer pulled the application from the store and withheld the documentation and source when the net-payable terms weren't satisfied. It was all worked out in the end, but it created a bit of a scary moment for the contracting company). apologies – I hadn't noticed your comment… As with any outsourced development, you require a solid NDA and legal contract/agreement between your company and the developer company. You should ensure that all documentation and software is properly assigned to your company in terms of ownership – whether or not it's ever launched as “generally available”. Make sure you protect yourself from agreements where IPR isn't assigned until the application is published. Also, be aware that many designers may demand a higher rate or some other compensation for immediate assignment of IPR (anecdotal note: I'm aware of an arrangement where the designer assigned IPR only after payment in full was received. The App was published to the AppStore under the designer's development certificate, not the contracting companies. This created a problem whereby the designer pulled the application from the store and withheld the documentation and source when the net-payable terms weren't satisfied. It was all worked out in the end, but it created a bit of a scary moment for the contracting company).

]]>