I have an app available for the iPhone only now not the iPad. I've already released 2 updates for the app(current version 1.2). Im about to release a third and in this update im adding a feature but thought Id also make it compatible for the iPad. Will apple accept that? Will I have to make a new project file for the iPad version?
You don't have to submit a separate project because all iOS applications are supported by the iPad by default, but you can if you feel the need to.
Right-click your target, and select "Upgrade current target for iPad".
I'd also recommend reading through Apple's guide on the subject.
No need to create the new project. There are two ways to solve your problem.
Change the device target to Universal and also change the logic to support both iPhone and iPad. In applicationDidFinishLaunchingWithOptions method put a condition to check the device.If the device is iPhone then load the iPhone screens and if not then load the iPad screens. This case when you upload the binary to App Store then the version number is same for both the binaries(iPhone & iPad) .
Change the device target to iPad and also change the version number whichever you want. For this also need to create separate nibs and change the logic to load only the iPad screens in applicationDidFinishLaunchingWithOptions method. For this case need to upload a separate binary with your specific version.The advantage of this step is you can make it as paid app for iPad or iPhone.
Note: My suggestion is if both are free apps then go with 1st step. If not then go with 2nd step. Still if you are not clarified feel free to ask.
Related
We know that in monotouch we have 2 solution for developing a project for both iPhone and iPads.
First is using Montouch iPad Application projects for iPad, and Monotouch iPhone Application projects for iPhone and create two separate project for each of them.
Another solution is using one Universal Projects for both o them.
The question is: what solution is better and with witch one the result has more quality?
Pros and cons of Universal app.
Pros:
One place to fix bugs in app's business logic;
Convenient to users (after install on one device it could be automatically installed on other device);
Marketing costs could be half as much;
Cons:
It could be too many if -blocks, which are checks for UIDevice.CurrentDevice.UserInterfaceIdiom;
Bigger app size;
Some of the features (mostly in games) do not fit well on iPhone's display.
If you used XIB-based interfaces, you must make separated XIB for iPad OR update XIB content layout in UIViewController's ViewWillAppear event (in which iOS updates View frame according to display size);
If your app is not free, you couldn't release "HD version" with bigger price.
Basically, universal app is better for users, but harder for developers and designers.
I think, you are asking about iPhone and iPad. Because, universal app includes iPhone and iPad (not iPhone and iPod).
So considering this:
You should go with Universal app because of below reason:
1) There will be one source file of the app which will work in both iPhone and iPad.
2) If user has both devices (iPhone and iPad), then they get a single copy of the app and can install in both devices.
3) Your app supports both devices, so users will be highly attract and download your app quickly.
4) If your app will more downloaded (because of Universal app) then there are chances that, your app comes into "New and WhatWorthy" section and even "Feature" section of the apple.
There can be main reason why we should go for Universal app instead of separate app for iPhone and iPad.
Hope, you got an idea.
Cheers!
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 have a Universal app existing in the app store for a client. The client wants to release an update just for the iPhone and ignore the iPad.
I said this wasn't possible because the app is already Universal, however, im not sure if I am right now.
Can I release an update that reverted to a non-universal app?
If so will the iPad customers get the update as a 2x app?
Are there any other options? Can I push an upstate just to iPhone customers?
if it is a universal app, then you can just change the iPhone code and leave the iPad code as it is. Both devices will get possibility for an update. I'd recommend adding something like
Update for iPhone side, nothing changed for iPad
to the release notes.
Answering your questions:
No idea, but I wouldn't do it
I don't think so
Other option: change only iPhone side and then test it on devices before publishing. That will show you if something will go wrong on iPad
I do believe one of the apps installed on my iPhone had something like that.
Hope it helps
You can revert to a non-universal app by making the appropriate changes to your project settings. This will cause all devices to receive the update when released, and on the iPad the app will revert to the 'iPhone 2x' interface. You cannot (as far as I can see) push an update to iPhone only.
Reverting to a non-universal app might upset some of your client's customers if they have become accustomed to using the iPad User Interface for the app when they find themselves back in the iPhone UI.
However - if the change you need to make is only to the iPhone User Interface, and doesn't affect the iPad UI or your application logic; Or if the change is to the application logic and won't break the iPhone or iPad UIs, you could still make that change and stay as a universal app ... In other words an iPhone UI update doesn't need to change or remove iPad UI functionality, and a logic-only change which doesn't break either of the UIs won't need you to revert to iPhone only even if that logic change only affects the iPhone.
If you need different behaviours within the app for iPhone and iPad, you can check which device your app is running on and carry out different functions automatically.
Basically, check what the update will affect in each of the UIs, and if the iPad UI won't break just leave it universal.
A customer is interested in releasing a universal app. However, the first release will contain only the iPhone version, the second release will contain both versions.
I found a few links where ppl figured out how to make this work in the simulation environment. However, i could not find claims about apps that finally were released to the AppStore successfully. I need verification of this.
Do you have links of people claiming to have universal apps released for iphone only or did you do it yourself?
In the application's Build Settings change the Targeted Device Family to iPhone, instead of iPhone/iPad.
In the latest xcode you can do this by summary screen too.
Thanks
It's not possible to only release the iPhone version via iTunes Connect, but you can set the Target Device to iPhone-only for the first version and it'll only be released for iPhone/iPod touch.
You need to make two changes. First, Set the Target Device Family back to iPhone. Second, in the info plist remove the Main nib file base name (iPad) entry. If you don't do that last step it will run as though it was an iPhone app (small view port with 2x button) but your iPad main window and delegate will be triggered.
Here is a more details post with some images for illustration:
http://www.fullboarcreative.com/labs/2012/04/20/tip-going-from-a-universal-to-single-device-app/
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.