Quote:
Originally Posted by jbjb
Incorrect. Before iOS6 scalable interfaces could be built using "springs and struts". It wasn't great (hence the introduction of auto layout), but it did work for some interfaces
|
Well then either developers didn't know about it or it was impractical to implement. Because when new resolutions were introduced in iOS back then, you had people living with apps that had black bands in areas where apps didn't scale -- a situation Android users never have had to deal with. This wasn't fixed until developers got around to putting out a new version of their app with new artwork to fit the new resolution.
Quote:
|
I'm not saying that all scalable interfaces are bad - I only stepped in to correct the common misinformation that you can't do scalable interfaces on iOS - you can. It's a supposed iOS limitation that many Android advocates try to use to beat up iOS, but it's bogus.
|
Well then there goes that myth that Apple always has pixel perfect layouts. They didn't always and don't now.
Quote:
|
The point is that developers have the choice - you can do pixel-perfect or you can do scalable (nothing forces you to use auto layout). The practical difference between android and iOS is that the difference in number of screen sizes available frequently leads to different choices on the two platforms.
|
From a developer perspective, there probably is little difference today in terms of accommodating different screen sizes. If you want your app to accommodate more devices on either iOS or Android you have to add in different artwork to cover all your bases.
From a user standpoint, I don't see the difference either. Apps on Android today are not substantially different from those on iOS in terms of GUI quality. In the early days of Android, there may have been a big difference, depending on the app, but not in 2013.
--Pat