How to make a 4.8 inch iPhone appealing to both consumers and developers

antihaze · Feb 11, 2013, 11:37 AM

First of all, I am sorry if this idea has come up before, but a quick Google search turned up zero results for the matter (in the 5 seconds I took to research this).

There has been a lot of talk about the screen size(s) for the next iPhone(s). Some are suggesting that Apple should follow suit after companies like Samsung, who have seen a lot of success releasing devices that are 4.8”+, once considered too big for the mass market. I think that consumers would appreciate the option of a larger iPhone, but it is a double-edged sword for Apple. Knowing Apple, they will keep as many things the same as possible while trying to appear to be different. In order to make a device with a larger screen, they would have to either dilute their screen resolution density if opting to keep the same resolution as the iPhone 5 (and tarnish their Retina reputation), or introduce an entirely new resolution (and risk alienating developers, not to mention enter Android-esque fragmentation territory).

I’m assuming that the move to 16:9 with the iPhone 5 will be the direction Apple continues to follow, so a larger 16:9 device makes sense. However, at 4.8 inches, the iPhone 5’s resolution (1152x640) takes a noticeable hit in density (330 ppi to 275 ppi).

If Apple wants to offer a larger device that still offers a retina screen (by today’s standards) and does not force developers to adopt an entirely new resolution to use and test, I propose that Apple use the original iPad’s resolution (1024x768) and extend it to a 16:9 ratio like they did with the iPhone 4S to the 5. This would result in a screen that has a resolution of 1366x768 and a screen density of 326 PPI at 4.8 inches; just shy of the 330 that the iPhone 5 currently has. Assuming that users would be able to hold this device further away from their face than the iPhone 5 to read it, it would still qualify as retina.

Other than pleasing developers and capturing some of the large-display market, there are other benefits to introducing a screen this size with this resolution:

Less drain on battery than a display with a previously-proposed 3x resolution (1440x960) or a 1920x1080 display

Less manufacturing problems as Apple’s suppliers are already quite adept at making displays of this pixel density

Encouragement of developers to make their apps universal from the beginning instead of rolling it out at a later time

TacticalDesire · Feb 11, 2013, 11:51 AM

iOS could just scale apps like android does...

antihaze · Feb 11, 2013, 12:01 PM

Quote:

Originally Posted by TacticalDesire

iOS could just scale apps like android does...

Wouldn't that look kinda janky though? I'm no developer, but I thought objects are assigned to certain pixels, etc. Blowing up the app would make it look weird.

TacticalDesire · 01:33 PM

No. There's a difference between just zooming something in and actually have it scale. Apps look just fine and crisp on android. Text and elements are crystal clear (that's obviously dependant on the display). How do you think desktop apps do it?

antihaze · Feb 11, 2013, 12:42 PM

Quote:

Originally Posted by TacticalDesire

No. There's a difference between just zooming something in and actually have it scale. Apples look just fine and crisp on android. Text and elements are crystal clear (that's obviously dependant on the display). How do you think desktop apps do it?

Fair enough. But why has Apple tried so hard this whole time to keep the resolutions direct multiples of one another? e.g. 480x320 --> 960x640, 1024x768 --> 2048x1536, etc. I thought it was so the developers didn't have to change too much when designing the new retina apps.

MarcBook · Feb 11, 2013, 01:01 PM

Quote:

Originally Posted by antihaze

Fair enough. But why has Apple tried so hard this whole time to keep the resolutions direct multiples of one another? e.g. 480x320 --> 960x640, 1024x768 --> 2048x1536, etc. I thought it was so the developers didn't have to change too much when designing the new retina apps.

Yeah, they've opted for the pixel doubling tactic because it involves far less inconvenience than resolution independence (adaptive scaling). All developers have to do is develop for the Retina resolution and their apps will automatically look fine on non-Retina displays.

macMD · Feb 11, 2013, 07:53 PM

While it would be nice to say the resolution being doubled was so developers would have an easier time supporting the new resolutions, so many have simply not done so. So the question is are they lazy, unwilling or simply don't care. Apple should be telling developers get it done by a certain date or risk having your app pulled. Lost revenue would be a good motivation.

Feb 11, 2013, 11:37 AM	#1
antihaze macrumors newbie Join Date: Aug 2012	How to make a 4.8 inch iPhone appealing to both consumers and developers First of all, I am sorry if this idea has come up before, but a quick Google search turned up zero results for the matter (in the 5 seconds I took to research this). There has been a lot of talk about the screen size(s) for the next iPhone(s). Some are suggesting that Apple should follow suit after companies like Samsung, who have seen a lot of success releasing devices that are 4.8”+, once considered too big for the mass market. I think that consumers would appreciate the option of a larger iPhone, but it is a double-edged sword for Apple. Knowing Apple, they will keep as many things the same as possible while trying to appear to be different. In order to make a device with a larger screen, they would have to either dilute their screen resolution density if opting to keep the same resolution as the iPhone 5 (and tarnish their Retina reputation), or introduce an entirely new resolution (and risk alienating developers, not to mention enter Android-esque fragmentation territory). I’m assuming that the move to 16:9 with the iPhone 5 will be the direction Apple continues to follow, so a larger 16:9 device makes sense. However, at 4.8 inches, the iPhone 5’s resolution (1152x640) takes a noticeable hit in density (330 ppi to 275 ppi). If Apple wants to offer a larger device that still offers a retina screen (by today’s standards) and does not force developers to adopt an entirely new resolution to use and test, I propose that Apple use the original iPad’s resolution (1024x768) and extend it to a 16:9 ratio like they did with the iPhone 4S to the 5. This would result in a screen that has a resolution of 1366x768 and a screen density of 326 PPI at 4.8 inches; just shy of the 330 that the iPhone 5 currently has. Assuming that users would be able to hold this device further away from their face than the iPhone 5 to read it, it would still qualify as retina. Other than pleasing developers and capturing some of the large-display market, there are other benefits to introducing a screen this size with this resolution: Less drain on battery than a display with a previously-proposed 3x resolution (1440x960) or a 1920x1080 display Less manufacturing problems as Apple’s suppliers are already quite adept at making displays of this pixel density Encouragement of developers to make their apps universal from the beginning instead of rolling it out at a later time
	0

Feb 11, 2013, 11:51 AM	#2
TacticalDesire macrumors 65816 Join Date: Mar 2012	iOS could just scale apps like android does... __________________ LG Nexus 4 8gb (Android 4.2.2) Black iPod Touch 5th Generation 32gb (iOS 6.1.2) Black iPad Mini 1st Generation 16gb (iOS 6.1.2) http://www.nrastandandfight.com/
	0

Feb 11, 2013, 12:32 PM	#4
TacticalDesire macrumors 65816 Join Date: Mar 2012	No. There's a difference between just zooming something in and actually have it scale. Apps look just fine and crisp on android. Text and elements are crystal clear (that's obviously dependant on the display). How do you think desktop apps do it? Last edited by TacticalDesire; Feb 11, 2013 at 01:33 PM.
	1

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Feb 11, 2013, 07:53 PM	#7
macMD macrumors 6502 Join Date: Nov 2005 Location: New York	While it would be nice to say the resolution being doubled was so developers would have an easier time supporting the new resolutions, so many have simply not done so. So the question is are they lazy, unwilling or simply don't care. Apple should be telling developers get it done by a certain date or risk having your app pulled. Lost revenue would be a good motivation.
	0