View Single Post
Old 09-05-2012, 11:14 AM   #35
Graham
Wizard
Graham ought to be getting tired of karma fortunes by now.Graham ought to be getting tired of karma fortunes by now.Graham ought to be getting tired of karma fortunes by now.Graham ought to be getting tired of karma fortunes by now.Graham ought to be getting tired of karma fortunes by now.Graham ought to be getting tired of karma fortunes by now.Graham ought to be getting tired of karma fortunes by now.Graham ought to be getting tired of karma fortunes by now.Graham ought to be getting tired of karma fortunes by now.Graham ought to be getting tired of karma fortunes by now.Graham ought to be getting tired of karma fortunes by now.
 
Posts: 2,743
Karma: 32912427
Join Date: Feb 2008
Location: North Yorkshire, UK
Device: Kobo H20, Pixel 2, Samsung Chromebook Plus
Quote:
Originally Posted by holymadness View Post
The essential problem of developing for phones and tablet is graphics scalability. Because apps are full-screen, they need to be designed for specific pixel widths and heights.

On Windows PCs, programs can be windowed and resized without any issues. Moreover, there is a limited number of universal stock resolutions (1024x768, 1440x900, 1920x1080, etc.) which help programmers optimize their software for display on different screens.
You realise that that's the way it's done on Android as well don't you? Android apps build to a set of standard frames (small, medium, large, etc) and adapt to the device.

Yes, it's easier on iOS where there is a standard screen size. No, it's not insanely hard to work in an environment where your UI needs to adapt. What this does mean is that iOS apps can look slicker, but it's not the issue for Android that you're making it out to be.

It's also the reason why Android apps written for a phone cope reasonably well with display on a tablet, even without specific coding for the larger screen. The interface is drawn according to the relative screen size.

Graham
Graham is offline   Reply With Quote