Note that there are some explanatory texts on larger screens.

plurals
  1. POIs it reasonable to consider a future Retina / HD iPad when starting a new project?
    primarykey
    data
    text
    <p>A few days ago a client asked me if the transition to the iPhone 4s retina display was a difficult one, development-wise.</p> <p>This made me ask myself whether I should have considered iPhones with high resolution dispays even before the iPhone 4 had been announced - creating artwork with higher resolution, preparing codepaths... (while, of course, creating high resolution artwork is never a bad idea, considering its use for marketing, porting to other platforms etc.)</p> <p>Now, with the iPad being around for some months, first rumors of a future iPad with retina display emerge from the depths of the www. And I start wondering - would it make sense to prepare new projects for such an iPad? I'm pretty sure that apple will in fact release a retina iPad at some point in the future, because it would be quite a logical step. So, I guess the important question is "how soon can we expect such a device?". There is much to consider when thinking about that, most of all production difficulties and the impact of a resolution of 2048 x 1536 (if apple sticks to simply doubling the "old" specs) on a mobile devices performance...</p> <p>So, what do you think? Will it pay up to prepare new projects for a retina iPad, starting now? Or do you think the overhead is not worth it, yet?<br> Maybe some of you are already developing with the retina iPad in mind..?</p> <p>I'd be glad to hear some of your thoughts! Thanks alot, guys!</p> <p><strong>Edit:</strong><br> Well, Apple just answered my question. Yes, it was in fact reasonable to consider a Retina iPad..!</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload