Matthew Panzarino for The Next Web:
We reached out to a few active iOS developers to get their thoughts on whether the larger screen would mean delays or a more difficult development process. The general consensus was that it shouldn’t pose too many huge problems, but that it would be a lot easier to test their apps if they had a device in their hands.
Glad to hear it is a surmountable issue, but there’s no question that it’s going to take a while for iOS developers to get up to speed with the new hardware.
Can devs buy the cheaper (not cheap enough imho) iPod Touch to test their apps for the new ratio? I think yes, unless I’m missing something. Like the importance of the a6?
Yes, unless their app has performance implications. If they’re pushing the limits on the smaller screen, they really need an iPhone to test the larger. Though it’s a challenge, it’s the business they’re in. If you want to develop for a platform, you have to test on it.
Instead of “isn’s a surmountable” did you mean
is a surmountable
OR
isn’t an insurmountable
if you cant buy the device youre developing for, youre not a developer. 🙂
As a developer, I cringe at the idea of anyone shipping untested code. Even the simplest application should, at the very least, be run on the new hardware before a release triggering 16:9 mode goes public.
This a very relevant issue and one I can contribute nothing.
I am posting here because I have yet to see this same issue of “how to make the apps fit this screen size” in the context of the Kindle Fire 8.9″ HD. Existing apps for 7″ tablets don’t magically “up-size” to the screen do they? And speaking of the HD aspect of the KF 8.9″ and 7″ I don’t hear the commotion people have made about “standard resolution” apps looking terrible on “retina-display” quality screens for the Amazon products.
Just saying, where’s the fuss with Amazon that Apple got when it broke this ground with retina-display resolution and now that it has a different screen size?
I’m an app developer and today I made our app iPhone-5 ready simply using the emulator. We won’t release until we’ve tested on real hardware, in case there are any embarrassing bugs (especially with the camera code), but it wasn’t difficult to do that way. It will certainly be less simple if you’ve pre-canned a bunch of 960×640 images, or set too many co-ordinates in code. In those cases it’s a fairly involved task changing things to not depend on a single resolution,
one word- android. it makes a world of a difference. resolution is meaningless in the android world.
bs. Also, I’m no developer.
Forgive my ignorance and Thanks for taking the time to reply and please forgive my ignorance. I don’t understand your reply, please elaborate if you have the time.
Android programs are not resolution dependant, they program based on densities. If a phone and tablet both have 720p resolution, it will look different on both because phones use a lower density (DPI) and tablets use a much higher one because the physical size of the screen is different. That’s why there are a million different screen sizes and resolutions for android and nobody complains the program adapts to fit the screen based on its DPI. Its actually really smart.
Thanks again, now I get it.