Linked by Thom Holwerda on Mon 19th Dec 2011 20:11 UTC
Google Once upon a time, in a land, far, far away, there were two mobile operating systems. One of them was designed for mobile from the ground up; the other was trying really hard to copy its older, desktop brother. One was limited in functionality, inflexible and lacked multitasking, but was very efficient, fast, and easy to use. The other had everything and the kitchen sink, was very flexible and could multitask, but had a steep learning curve, was inconsistent, and not particularly pretty.
Thread beginning with comment 500900
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: Some corrections...
by Not2Sure on Wed 21st Dec 2011 23:29 UTC in reply to "RE[3]: Some corrections..."
Not2Sure
Member since:
2009-12-07

This isn't the same as Application Components. The review is spends quite some words on that.


As other commenters have already pointed out content handling is most certainly a component model of software architecture but one that relies a little more heavily on convention for proper decoupling.

The key difference lies in the process model between iOS and Android. In addition, Android also allows the user to select (via system preferences app) which among several competing registrations for the same content request to use whereas on iOS it is the last run app that wins. Finally, Android allows for the "auto-install" of functionality on the device when the content handler requested is not present which is not possible on iOS. For example, a shopping list app that uses a UPC or QR bar code scanning activity will cause the OS to download and install it when the app makes the first request.

It really is a strawman argument however as the whole component model has never been much of a success no matter whether it has been Google or Microsoft who pushes it. Just generally leads to too disjointed a user experience.

Reply Parent Score: 1