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.
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 need to develop some app for iPad and iPhone users.
I understand that there are 3 ways:
Two distinct Apps, one for iPhone and one for iPad. (Not linked in apple store)
One Universal app (appear with + sign in Apple Store, the app store choose the desired app depending on the device) (I choose from xcode to make the app Universal).
One application with two targets, One for iPhone and one for iPad. (using Duplicate target for iPad in xcode) (Linked in apple store).
I need to understand the differences between 2 and 3 above.
Thanks.
The difference is that in 2 you are creating one single binary from one Xcode project that works on both iPad and iPhone. It has a universal target meaning it runs on both iPad and iPhone requiring you to adapt the user interface appropriately.
In 3 I believe you are implying that you create one Xcode project and create two build targets inside the project. I have done this before and it allows you to easily share files between applications. Just add references to the files you want to share in both targets. As far as how 3 looks in the AppStore it looks the same as 1, two separate applications.
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.
I have a rock solid iPhone app and wanted to know how I could get an iPad app out through iTunes Connect.
What steps are required in Xcode (or AppCode) to compile the app iPad friendly?
What features (like gps) should I pull from the iPhone code base to prevent strange crashing on the iPad?
How do I link and publish the iPad app in iTunes Connect so users who search see my app with a + sign in the App Store (assuming this means it's iPhone and iPad friendly)?
And finally, what else should I look out for doing this from a single obj-c codebase?
There are two types of porting possible one is universal app (in which a plus sign is shown with your app in itunes) and the other is two device-specific application (in which two targets are created one for iphone and one for ipad and both get released as complete independent apps). Now it depends on you which modal you choose. Yet I ported my apps using the second option as I want user to buy each time for each of his device :). Anyways, solely depends on you, here's a good tutorial for this http://www.raywenderlich.com/1111/how-to-port-an-iphone-application-to-the-ipad. I haven't came across any such thing which can crash a similar app on the ipad but might there'd be some. Though there are somethings which I came across that the ipad (ipod too) doesn't have any vibrator available, as my iphone app was using vibration to give some indication, so if you're using it you might need to circumvent it with some alternatives plus your app should support the PortraitUpsideDown orientation. It's weird that APPLE rejected my third ipad app due to this after releasing my first two apps with the similar limitation :).
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.