Thread: Angry Birds and Nokia’s Perception Problem
View Single Post
gerbick
2010-09-17 , 17:33
Guest | Posts: n/a | Thanked: 0 times | Joined on
#52
Originally Posted by bergie View Post
It ensures that application developers have a stable set of APIs that they can rely on across devices and manufacturers. But manufacturer can add whatever they want on top of that, as seen in the WeTab MeeGo tablet being able to run also Android applications.
You state that as if any of the aforementioned UI options on top of Android are breaking API's. To my knowledge, none are.

Not much. But based on what I've read of Android 3.0, it seems Google is seeking to limit that type of customization
Sounds like they're becoming more MeeGo-like in that endeavor.

I guess what I'm gathering from your statements is that MeeGo has a API framework that explains what UI calls and changes that each and every UI on top of the MeeGo framework will have to follow. As it stands, in very loose terms; that's the exact same thing that's in place for Android.

So with that said, why was it brought up like one had an advantage over the other? I'm not seeing it. Both seem to have rigid frameworks whereas UI/UX is in question. And to me, that's a very good thing.

One isn't more limited than the other... which is also a very good thing (sticking with the UI/UX sections).
 

The Following 2 Users Say Thank You to For This Useful Post: