Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I'd like a Retina display in the 27" Thunderbolt display. I'd be a buyer right there. We've been stuck at low PPIs forever. Time to move up.
 
Won't a new resolution in the iOS cause issues with fragmentation of the apps on the platform? I thought Apple was standardizing iPhone and iPad resolutions? Could the higher-res designations be for a future version of iOS for Mac?
 
Apple halve already done this when they went from the iPhone3GS to 4.

It really wasn't much of a problem. If the developer didn't want to update their app at all, it still worked via pixel doubling. If they did update it, it would scale 'down' to the 3GS just fine. There is no need to create 4 sets of images

Wrong actually. Images dont 'scale down' to the 3G you have two sets of images. One for the 3G (lets call it 'image.png') and another for the retina display, which has to be called 'image@2x.png'. The app then uses the '@2x' images on retina resolutions.

The only real way around it is a fixed size across all apps. Its not a problem for an app that only uses images for tiled backgrounds and such, but lets say for example you've got an app that shows information about different holiday destinations. It has a page for each hotel, along with a thumbnail sized photo in the corner, which when tapped opens a photo of the hotel larger.

Thats two images: the thumbnail and the full sized image.

Now, the fullsize image you'd probably need 2 sizes as you can get away with a pinch/zoom on the retina iPhone. However the thumbnail is designed to be a fixed, 'static' image that has to be pixel perfect or all your buttons and text overlap and screw the app up. Lets say that the image has to be 1/4 the width of the device, you then need 4 images:

80px wide for the iPhone 3G
160px wide for the iPhone 4
192px for the iPad
384px for the iPad 'Retina'

When you've got hundreds of hotels to list, thats going to make the filesize 4x the size it should really be, all because Apple failed to include a decent way of cross resolution management with one set of files.
 
Won't a new resolution in the iOS cause issues with fragmentation of the apps on the platform? I thought Apple was standardizing iPhone and iPad resolutions? Could the higher-res designations be for a future version of iOS for Mac?

What people forget is that 'retina displays' don't get you more "real estate" on screen as with prior resolution updates over the past 20+ years. The point of the retina display is to make things sharper so you can't see the pixels. The new iPad screen would have 4 times as many pixels, so you could simply use 4 pixels to reproduce that which is now done by 1 pixel. This means that old apps are backward compatible - and new apps will make use of the increased resolution.
 
Wrong actually. Images dont 'scale down' to the 3G you have two sets of images. One for the 3G (lets call it 'image.png') and another for the retina display, which has to be called 'image@2x.png'. The app then uses the '@2x' images on retina resolutions.

The only real way around it is a fixed size across all apps. Its not a problem for an app that only uses images for tiled backgrounds and such, but lets say for example you've got an app that shows information about different holiday destinations. It has a page for each hotel, along with a thumbnail sized photo in the corner, which when tapped opens a photo of the hotel larger.

Thats two images: the thumbnail and the full sized image.

Now, the fullsize image you'd probably need 2 sizes as you can get away with a pinch/zoom on the retina iPhone. However the thumbnail is designed to be a fixed, 'static' image that has to be pixel perfect or all your buttons and text overlap and screw the app up. Lets say that the image has to be 1/4 the width of the device, you then need 4 images:

80px wide for the iPhone 3G
160px wide for the iPhone 4
192px for the iPad
384px for the iPad 'Retina'

When you've got hundreds of hotels to list, thats going to make the filesize 4x the size it should really be, all because Apple failed to include a decent way of cross resolution management with one set of files.

You are forgetting to mention that you are talking about universal apps: apps that both work on iPhone (iPod touch) and iPad.

iPad specific apps have completely different lay-outs. It's not like a developer needs 4 times the same image for something, because developers don't recreate an iPad app one-to-one.

I think it's pretty decent how the double resolution is 'managed'. Double the resolution (or half it if you've already got high-res), and upload it. It will be the same for iPad and requires very little work from developers.

And let's not forget, it's expected that Apple will drop iPhone 3GS support next year. From than on, developers won't have to deal with 'low-res' displays anymore unless Apple is going for a 1920*1280 display in the 6th generation iPhone. Than the iPhone 4S' display will be 'low-res'. In that case, nothing really changes.
 
Coming iPad is not really iPad3, but iPad Pro.

iPad Pro:
- x86 Processor
- OSX 10.7 Lion
- Retina Display

Next year, Windows 8 tablets will rush out. In this situation, do you think that Apple can battle against them with their Giant iPhone? :rolleyes:
 
Wow :O

There's gonna have to be massive power for GPU, I wonder what they are going to do :)

A Quad-core CPU/GPU? Using the Cortex A15? That would be insane...but so would the price :D
 
Coming iPad is not really iPad3, but iPad Pro.

iPad Pro:
- x86 Processor
- OSX 10.7 Lion
- Retina Display

Next year, Windows 8 tablets will rush out. In this situation, do you think that Apple can battle against them with their Giant iPhone? :rolleyes:

One of the big things about Windows 8 is that it will support ARM processors. Chances are that will be what most W8 tablets use. Not a battery hogging x86 processor.
 
Consumers response: YAY!

Developers response: Oh crap!

---

I know I'll get downvoted for this, but its got to be said as its completely true...this WILL unquestionably be the start of fragmentation on iOS. People will still be using the iPad 1 and 2 for a good 3-5 years from now, meaning developers who do universal iOS design will have to create 4 sets of images.

You simply cant keep messing around with screen resolution changes.

I don't think so.

Reason being is that there is a finish line in site. Once a display gets to Retina Display quality, it doesn't need to keep going.

So yes, in these last final marches towards a final resolution beyond which there are no additional benefits detectable to the naked eye, there will be a bit of fragmentation. But soon all of the devices will catch up, and the older ones will slip off the map, and it won't matter at all.

This is just the possibility of some short term fragmentation depending on how lazy or resource strapped developers are. It will all re-align by 2013 likely where all development is at one resolution per device, with fragmentation continually dropping from there.

Finally, if the share of older displays are greater and resources are limited, developers can just develop at the lower 'universal' resolution. Nobody says the have to take advantage of the higher if the payoff isn't there for them.
 
And let's not forget, it's expected that Apple will drop iPhone 3GS support next year. From than on, developers won't have to deal with 'low-res' displays anymore unless Apple is going for a 1920*1280 display in the 6th generation iPhone. Than the iPhone 4S' display will be 'low-res'. In that case, nothing really changes.

I doubt they will drop support for the iPhone 3GS because the power is about on a par with the iPhone 4 as it only has to drive a quarter the number of pixels. Plus they are still selling the 3GS.

The iPad 2 has up to 9x the speed of the iPad 1. Hopefully there will be a similar increase for the iPad 3, but much of that will be swallowed up by the new resolution (in the same way that the iPhone 4 speed increase was), and I'm fine with that as it is a really meaningful improvement.
 
I hate the timeframe for new iPads, the beginning of a year is not a good time for new products, everyone that buys a iPad for christmas is ****ed because of that.

Christmas is how they clear their inventory. Much like second breakfast, Apple after December is second Christmas. :D
 
The lack of this display is why I didn't buy the ipad 2. Now i'm running out of excuses.
 
Maybe this will clarify the resolution increase:
 

Attachments

  • Screen Shot 2011-11-22 at 10.38.03 AM.png
    Screen Shot 2011-11-22 at 10.38.03 AM.png
    9.6 KB · Views: 367
I doubt they will drop support for the iPhone 3GS because the power is about on a par with the iPhone 4 as it only has to drive a quarter the number of pixels. Plus they are still selling the 3GS.

Of course they will drop the 3GS, it's just a matter of time. You understand that if you want to. The question is when, and I think that will be with the release of the next iPhone and I don't think 3GS will support iOS 6. If Apple were to release iPad 3 next year with retina display I believe they will maybe do the same as with iPhone now and keep the iPad 2 as a low-budget option and maybe the iPad 3 will start at $599?

iPad Pro will never happen. That's too much of a fragmentation for Apple. The jump up from iPad will be the MacBook Air.
 
Wirelessly posted (Mozilla/5.0 (iPhone; CPU iPhone OS 5_0_1 like Mac OS X) AppleWebKit/534.46 (KHTML, like Gecko) Version/5.1 Mobile/9A405 Safari/7534.48.3)

Am I just naive to think that nexus prime at 4.65 screen with somewhat of 1200x960(?? Somebody double check this)..... Is it so far fetch to say iPad 3 will do 9.7 screen with aforementioned resolution?????
 
Assuming the next iteration of the iPad will have four times as many pixels:

will 4 small pixels require more electricity than one large pixel (that is as big as 4 small ones)?
 
Wrong actually. Images dont 'scale down' to the 3G you have two sets of images.


Fair enough, but if the resolution is exactly doubled, it only takes a couple of seconds to generate a good quality half-size version of your artwork in photoshop.

It's not exactly a great hardship for developers. I do exactly that on some of the shopping sites I work on, it's just a matter of running a batch job and photoshop does it for you.

It's not even as if this is an issue with every app. It's mostly just 2D games. 3D games, web, vector and text based apps, would all be able to scale up with only minor code changes.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.