We created a few applications targeting iPhone 3 and iPhone 4. When we tested these apps on iPad, they worked well. We thought we do not need to create separate apps targeting iPad. We went with that decision. A few months later, we realized that the graphics are not looking as good as are on the iPhone. Even the text is not that sharp. Now we are wondering whether to create these apps targeting iPad as well. Do people usually create separate apps for iPhad and iPhone or they just create one for these two platforms? If we need to create separate apps, what is the best way to do?
You just need to change the images and size for ipad. A few changes in xibs that are for ipad. you can make same app work on iphone as well as ipad...
Check out this Link that convert iphone app to universal ipad apps
Link here
You can place this condition if(UI_USER_INTERFACE_IDIOM()==UIUserInterfaceIdiomPad) and then load the respective xibs. Hope you are getting my point.
The iPad uses "pixel doubling" to expand an iPhone app to completely fill its screen in 2x mode. That is usually why it won't look as sharp as a native iPad app. The best way to answer whether or not you should make an native iPad app is a matter of customer base and funds for R&D. Do you think your customers will demand (and pay for) a separate app? Is it worth the additional costs to design, develop, support and maintain it?
Also, do the activities involved in your app scale to the iPad platform? When I say this I mean are they complex enough where they would benefit from redesigning to accommodate the extra screen space and UI elements the iPad offers?
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!
It is recommended by Apple to make universal apps, i.e. one ipa for iPhone and iPad. If I make a standalone iPhone app, it gets approx. 6Mb. If I make a universal app it becomes approx. 19Mb... For iPhone users this is a waste... (size is build up of iPad image resources). This feels wrong to me... Please comment.
If you sell your app, users which own an ipad and an iphone would need to buy your app twice, if they want to use it on both devices. I would prefer the waste of 12mb.
Contra: extra size.
Pro: you will need promote two apps, users who own iPhone and iPad will need buy twice.
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 :).
I started to develop an iPhone App for a client but the binary not yet submitted to Apple. My client asked me whether they can run the iPhone App also on the iPad. I am not sure what to answer. I am away from home and cannot even check how this all works in XCode. I wonder whether I have to submit two binaries two Apple - one for iPhone and one for iPad - or how this all works? If somebody with experience can explain me. Basically I need to figure out how much more effort I have to consider if it is only making the app work on the iPad. I do not mean the effort to redesign the whole app being a real "iPad app". Just to make it work and when somebody downloads the app and it can be for an iPhone and for an iPad and it does not matter.
An iPhone app can run on an iPad anyway, but that's not a great experience (get your iPad out, download a free iPhone app, and try it). You could make a 'universal' application that works properly on both types of hardware, most of the code you've written will already work properly on the iPad side but you'll need new views and view controllers (and graphics).
If you have well applied the MVC pattern, you only need to create new viewController made for iPad.
Got your question #hol.
that you dont wanna redesign the application for iPad but you want your application to run on iPad also.
iPhone applications can be installed in iPad and when we run it it gives 2X button in the right bottom corner which zooms the iPhone application in iPad. But the problem is it gives blur images as the images are zoome to double.
And the question that your client is asking whether it is iPad compatible or not then the answer is NO.
For making both iPhone and iPad compatible as mentioned above by all you have to develop universal application.
where either you have to make 2 nibs for each view controller..
Hope this helps..
hAPPY iCODING...
I am new to iPad,I am having iPhone distribution build, can i upload to apple for iPad Device?Will it run? will it be accepted by Apple?otherwise i have to create new Ipad application for existing iphone application?
Practically all iPhone apps will run unmodified on the iPad. They will simply be scaled up pixel-by-pixel (with a little "2x" button so the user can choose scaled/unscaled mode).
For the best user experience, you should create a universal binary that provides customised behaviour for each platform, but this isn't required.
Any iPhone application, an application that has not been optimized for the iPad, will run on the iPad in 'compatibility mode', which means it will get its own iPhone-sized frame in the center of the iPad screen. The user also has the option to zoom in the application 2 times, so it takes up almost the entire iPad screen.
So if you want your app to run at all on the iPad, you don't have to do anything exciting, just submit it to Apple as usual, and iPad users will be able to download and use it.
If you want to optimize your application for the iPad, which is almost always preferred over 'compatibility mode', you can either make your current application into a Universal one, which is an app which contains both iPhone and iPad versions, in one binary, or you can create two different applications, one for the iPhone and one for the iPad. You can find more information on this on the Apple Developer website.