View Single Post
Old 01-01-2013, 06:03 AM   #21
jbjb
Somewhat clueless
jbjb ought to be getting tired of karma fortunes by now.jbjb ought to be getting tired of karma fortunes by now.jbjb ought to be getting tired of karma fortunes by now.jbjb ought to be getting tired of karma fortunes by now.jbjb ought to be getting tired of karma fortunes by now.jbjb ought to be getting tired of karma fortunes by now.jbjb ought to be getting tired of karma fortunes by now.jbjb ought to be getting tired of karma fortunes by now.jbjb ought to be getting tired of karma fortunes by now.jbjb ought to be getting tired of karma fortunes by now.jbjb ought to be getting tired of karma fortunes by now.
 
Posts: 471
Karma: 3550358
Join Date: Nov 2008
Location: UK
Device: Kindle PW, iPad, iPhone
Quote:
Originally Posted by afv011 View Post
I don't see this happening. We know how inflexible iOS is with resolutions; developers would have to rework all apps to run on yet another resolution.
That's a bit misleading. Firstly, iOS isn't as inflexible with resolutions as many people seem to think - it's perfectly straightforward to scale interfaces automatically using using springs and struts, and iOS 6 introduced a more sophisticated auto-layout feature. Many developers choose not to use these, however, as a scaled interface doesn't always produce something as satisfying as a pixel-perfect design for a particular resolution. Android fragmentation means that developers often don't really have much choice but to use resolution-independent designs, but the number of iOS platforms is sufficiently small that it's often entirely feasible to design the ideal interface for each device.

In the case of a watch it seems vanishingly unlikely that a scaled version of an existing interface is what you'd want, so to claim that the need for a custom interface design is due to some perceived iOS limitation is misleading.

/JB
jbjb is offline   Reply With Quote