I have developed an iPhone app and preparing to upload it to iTunes store.Later on I want the iPad version of the app as well which I am currently working on.
So I would like to know whether it is possible to release the iPad app later as an update to the existing app in the store?
So long as the iPad version is part of a universal bundle (iPhone and iPad resources in the same app) it would be treated as an update.
I don't believe you can. However, I think that you may be able to update it to a Universal application.
Most people just make the iPad version separate and call it App HD or provide universal versions.
Yes. You can make it Universal with an update, but you can't stop support a device after you published a universal app!
If you want to upload a different iPad-Version (e.g. AppXY HD) you can also create this in the same Xcode project and upload them as different versions.
Related
I've uploaded the 2.0 version to the appstore having to support both iPhone and iPad.but the previous version does supports only iPhone. This version having the resolution issues in the iPad. I've created the version 3.0 for iPhone only, but the iTunes connect is not accepting this build and saying that " This bundle does not support one or more of the devices supported by the previous app version. Your app update must continue to support all the devices previously supported.You declare supported devices in Xcode with the Targeted Device Family build setting."
any one please suggest me the best solution.
You can't change an app from universal to iPhone or iPad only once it has been approved and was live in the App Store. Your only option is to remove the app from the App Store completely and submit a new one that's iPhone only but then you lose most of your customers probably.
I'd suggest that you just solve whatever issues you have with the universal version as soon as possible and submit an update.
We have an iPad game on the appstore and decided to make an iPhone version of it.
After adding a new target, modifying the necessary views and classes the game runs perfectly on both iPhone and iPad (devices and simulators).
My question is, do I have to upload the new iPhone version as a completely different app to itunesconnect or is there a way to use the same name/app id for both?
Will users who already purchased the iPad app have to pay again for the iPhone app?
Anyone who can shed some light on multiple targets and universal apps would be great.
Thanks in advance.
Yes , You would have to upload the new iPhone app separately and the users who purchased your iPad app would have to pay for the iPhone version again. This is only when you have not developed a universal app in the beginning for both iPhone and IPad. If it was for both then there would not have been an issue. Also the app you would now put up as the iphone one cannot be the same name as of the iPad one as the name has been reserved for the iPad one only.
I've had an iPhone product on iTunes for a while and have superseded it with a universal app which has been met with approval except from one customer who wants to run the iPhone version on his iPad as he preferred the larger inputs and working of the iPhone.
Is there any way to configure the app to run either as native iPad app or iPhone app on iPad at runtime? Seems an odd request but customer is quite insistant.
Thanks
/Fitto.
No way to do that, except making separates versions for iPhone and iPad.
Theoretically, you could have some setting that would load the iPhone storyboard on the iPad, but it would still display full screen, and not in compatibility mode, which is probably the way this particular user wants it
Assuming you are running some sort of source control, you could change the project to be "iPhone Only" and then test on the iPad, then later revert the changes made to make it a Universal app again
I am creating an app which has version for both iPhone and iPad, iPad version has different GUI and some more functionality. Currently, I separate them in 2 projects.
After reading this article: Jump from iphone to ipad development...
And see:
"All iPad users who have already downloaded your free or paid App to their iPhone or iPod Touch will be able to download your iPhone App – only if you have updated your binary submission to the App store to make your iPhone App compatible with iPad. If you do not update and create the separate binaries, then you are potentially losing out. Using the new SDK you will be able to create a single binary which will install one version of your app when used on the iPhone or iPod Touch and a different binary when installed on an iPad"
I don't know if my current way is correct when separate them in 2 different apps! and how to create single binary which will install one version of your app when used on the iPhone or iPod Touch and a different binary when installed on an iPad?
Does anyone know about this please help me!
There are two ways to have an app on both iPhone and iPad. One is to build two separate apps that do the same thing. This is what you are doing, but not what you described. It creates two applications, one for iPhone and one for iPad, that do the same thing. As such, purchasing one will not give the user access to the other.
If you want the user to be able to use a single app on both the iPhone and iPad with different interfaces, you need to build a universal app. It will contain code and resources for both the iPhone and iPad. See iOS Application Programming Guide: Build-Time Configuration Details. About two thirds of the way down is a section on universal applications.
Edit: I found another document specifically about universal applications: http://devimages.apple.com/iphone/resources/introductiontouniversalapps.pdf
Whether to have two separate SKUs on the App Store or not is usually more of a business question than a technical one. Separate apps lets you segment your users and charge more for the iPad version. On the other hand a universal app is usually better received by users and can make the most sense if what you have is a premium, 'expensive' niche app.
If you want to go the universal route:
If you have an iPhone application that
you want to upgrade to run on iPad
devices you need to upgrade the target
that builds your iPhone application
into a target that can build both an
iPhone and an iPad application, or add
a target to your project for building
the iPad application.
To upgrade an iPhone target for iPad
development, select the target in the
Groups & Files list and choose Project / Upgrade Current Target for iPad.
We have an app (runs on iOS 3.0 or later) in app store already and , we planned to upgrade that app as an universal app.
I believe that, when we submit an universal app ( runs on iOS 3.2 or later) , App store retains a copy of iPhone-only version of that app , and serves that copy to iOS 3.0 Customers (if OS Deployment target in Universal app is set to iOS 3.0).
(Ref: https://devforums.apple.com/message/297572
Correct me if I have misunderstood that.)
After submitting my Universal app , can I update my iPhone-only version without affecting Universal app?
Simply, Can I address any feature requests of iOS 3.0 user (or) can I edit the retained copy, after upgrading my app as an Universal app?
There are two ways you can go when it comes to deploying an application for iPad and iPhone. The first is to create two different applications with the same name, one for the iPad and one for the iPhone. This approach lets you independently update the two versions, as well as make people pay for each version.
The second way is to create a universal iPhone / iPad application that consists of a single binary which alters its function and interface depending on which device it is running on. When you update this application, it is updated for both platforms at once. This is the approach Apple recommends, because it simplifies the user experience. If a user buys or downloads your application, it will transparently work on all of their devices. They only pay once for it.
If you upgrade your existing iPhone application to an iPhone / iPad universal one, the universal one replaces the previous iPhone-only version on the store, just like every update you do replaces the previous version.
I prefer creating universal versions, and it is what I've done for my applications. However, I can see why people would want to create separate versions of their applications if the iPad version is vastly different than the iPhone one (see OmniFocus as an example of this) and they want users to pay for the effort in creating the new application.