Let's recap: MeeGo's promise is vertebrated basically through the MeeGo API. If we don't assure a "MeeGo compliant" app runs across MeeGo devices within a range of releases then the success of the project is at stage.
This is already complex. You can see the problems you might get looking at the Android fragmentation, and the reactions it gets. The Qt / Qt Mobility / Web Runtime game combined with the different UXs is already more complex than the setup offered by Android and iOS. We should find there all what it takes to build a great commercial developer offering under the "compliance flag". Then you have MeeGo Extras, hosted at meego.com and handled by the MeeGo community, containing compliant apps and also compatible apps departing from the MeeGo official API. The MeeGo commercial offering doesn't *require* Extras but can benefit from a successful Extras anyway. Letting Extras out of the Compliance program makes sense, especialy now that the comercial part still needs to be created and consolidated. -- Quim
_______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
