Linked by Thom Holwerda on Thu 26th Apr 2012 22:09 UTC
Permalink for comment 515859
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
More News »
Sponsored Links



Member since:
2009-07-18
The fact that Android essentially had no legacy code base to try to move to a touch platform made it much easier. Microsoft was worried about keeping the PocketPC / CE apps going, RIM had their Blackberry users, and Nokia had their base. Adding fundamental touch support without screwing over existing apps where UI interactions were designed totally differently (interface elements too small to touch effectively) because of the working assumption of a keyboard, buttons or stylus - not as easy to respond to. Look at Microsoft's final answer: drop the old mobile OS entirely.
From Thom's original article: "In other words, unlike iOS, Android was built to be flexible, and run on many sorts of devices, with different screen sizes and form factors."
The fact that Apple optimized their specific UI for a more controlled set of sizes and touch input certainly doesn't mean the OS is somehow less flexible. If you mean the UIKit framework, sure, that assumes a touch interface - but the core of the OS has made it from NeXT workstations to current desktop machines, laptops, and phones and across quite a few CPU types to boot, and the lack of multitude of screen sizes had more to do with Apple not making 15 product variants because they didn't think it made sense.