Would a Bigger iPhone Cause Developers Headaches?Erica Ogg
If those pesky “people familiar with the matter” are to be believed, Apple will move to a larger screen on its next iteration of the iPhone, thought to arrive sometime this fall.
The Wall Street Journal and Bloomberg News reported separately last week that Apple will introduce a screen of “at least 4 inches diagonal” or “bigger than 3.5 inches,” the current screen size. What’s not clear is how Apple would go about this and satisfy both users—who may enjoy a larger screen but also want to keep the Retina display quality—and its army of third-party developers—who don’t want to have to come up with a wide variety of different screen sizes.
There are several theories as to how Apple could build a larger-screen iPhone, including scaling up the screen and dropping the pixel density a bit; changing the aspect ratio, increasing the screen height and keeping the pixel density the same; increasing the width and height; or going bigger than 4 inches and using a standard 16:9 resolution. Rene Ritchie at iMore has a good explanation of how Apple could get there.
But what do the developers who will have to deal with the implications of a larger screen think? I talked to a few iOS app makers, and many of them interestingly are not convinced Apple would actually “pull an Android,” as one developer put it, and make it more complicated to design for a bunch of different screen sizes (iPhone 3GS, iPhone 4/4S, and something new).
Sam Shank, the chief executive officer of Hotel Tonight, a hotel-finding app for both iOS and Android, said if Apple does change the screen size, he believes the phone itself would become slightly wider but not much taller. But he doesn’t believe Apple would mess with either the aspect ratio or the pixel density.
“Changing the aspect ratio would be a lot of work for development teams. We found that maybe 50 percent of iOS development is [spent] in layout,” he said in an interview on Friday. “If we had to do two versions of that—the current aspect ratio and a new aspect ratio—and had to lay it out again, that would add considerably to our development time.”
Lenny Rachitsky, who heads Localmind, a social discovery app for iOS and Android, said he doesn’t see Apple creating fragmentation problems for its developers. “We haven’t put a lot of thought into it yet, partly because we assume Apple isn’t going to pull an Android and fragment the device market unnecessarily. If they do, they must have a really good reason to do it, and we’re confident they’ll provide tools to make it easy to migrate. The last thing they want to do is put more friction in front of developers.”
Localmind’s lead iOS developer, Nelson Gauthier, sounded equally confident that Apple would make any transition, if needed, smooth. “Apple often changes the requirements for iOS applications, but they usually give developers fair warning and decent tools to accommodate new devices. The transition to Retina display and iPad were both relatively straightforward,” he said.
Gauthier continued in an email:
A bigger display could mean a few things. It could mean the display has a higher resolution while retaining the same aspect ratio. The new display might be a different shape. Finally, the display might simply grow while retaining the old resolution. But changing the resolution or aspect of the display need not have an effect on user interface elements, just their layout. Bars and controls could stay the same size while content areas expand to fill the additional screen real estate.
Apple might help developers transition between form factors by providing a system that would automatically adjust layouts for new resolutions and display aspects. Last year at WWDC (Worldwide Developers Conference), they revealed a component for Mac OS X called Cocoa Auto-Layout that allows developers to define layouts using fairly simple, freeform constraints. A system like this could also work on iOS.
Massive Damage, which makes location-based iOS games, is also betting against major changes for developers. As CEO Ken Soto points out, there are already two resolutions many developers have to worry about for iPhone games: standard resolution for older iPhones, and Retina for the iPhone 4 and iPhone 4S.
“I can’t quite imagine how they will introduce yet another retina resolution standard. Overall, I think if Apple does increase the screen size, they will be careful to not introduce too much fragmentation. They will likely keep the aspect ratio the same so developers won’t have [to] re-factor their UI,” he said. “I have a feeling a bigger iPhone will automatically scale up existing retina resolutions as the screen would likely only get a little bit bigger.”
But the feeling that any change would be negative isn’t necessarily universal. Donnie Dinch, the co-founder of iOS last-minute ticketing app WillCall, said because of the content of his company’s app, a screen size change may not have a huge impact for it, especially if Apple went the route of simply making the screen taller.
“It doesn’t really matter how tall it is for us; it’s probably a bigger deal for games. … I think a lot of the things we do is just list screens [of ticket information], so having a taller screen makes sense,” he said.
But lowering the pixel density to accommodate a larger screen? The screen is the most important part of the iPhone, said Dinch: “If they augment that in any way negatively, that would be insane.”
Also from GigaOM: