Designing for iOS4’s screen resolution

The updated platform uses a higher resolution screen (960×640 as compared to 480×320). This additional resolution also means that any graphic elements need to be designed twice. One set of images for the lower resolution and optional high resolution set for iPhone 4. iOS4 still considers itself 320×480, but introduces a scale factor you can check or provide upscaled graphic assets for it to automatically use. In other words, the iOS4 requires low resolution artwork and can scale it up, but you can’t expect to simply build out a high resolution version and have the OS scale it down.

We’re currently working on updating our iPhone GUI PSD to reflect the forthcoming iOS4 update. We’ll likely release 2 new PSDs. One for 480×320 and another for 960×640. We’re going to try and make everything as pixel perfect as we can while maintaining assets as shape elements for easy scaling. We’ll be sure to post an update when it’s done.

Categories: Apple, iPhone5CommentsJun 99:13 amSijo said:

thanks for all ur previous posts…..thanks for sharing all these things….

Jun 99:13 amJJ said:

Hey, in the current version of your GUI PSD, anything drawn as a vector shape and styled with layer effects is not snapped to pixels, yielding some blurry edges and general weirdness that makes your toolkit look not so convincing. Perhaps in this update you’d consider ensuring only whole pixels are used for all shapes? (especially buttons!)

Jun 910:41 amMark said:

Legend

Jun 910:57 amhezral said:

has the interface guidelines been updated?

Jun 92:31 pmDan said:

I believe the introduction of high res screens is going to bring a revolution in the way in which we use devices, particularly in making reading easier. It will also pose some exciting challenges and new opportunities for us designers. Pixel shavers everywhere will be rubbing their hands!

Looking forward to seeing your new GUI.

Post Your CommentYour Name:Your Email: (this will not be published)Your Website Address:Your Comments:

Search our blogGoFollow us on Twitter:


View the Original article