On Saturday 18 September 2010 19:48:04 Skarpness, Mark wrote: > I don't agree that having MeeGo compliance support componentised > applications is an objective we should take for the near term. I would > rather us focus on solving the core problem (self-contained compliant app > runs on any compliant device).
I could agree with, and support, that view if you remove the term "compliance". That is what is causing a lot of the concern and heat on this topic. There is nothing non-compliant to MeeGo about componentised apps but there are good, practical, reasons to first solve the "run anywhere" problem for non-componentised apps. So, how about taking the heat out of the argument by replacing the concept with words that are more neutral. Also recognise that the compliance doc is essentially technical and any term used should be independent of the marketing brand used to publicise the concept. Instead of MeeGo Compliant apps create a new term for the compliance document to describe those apps which are simple (one package) and which only depend on the MeeGo Core. How about "MeeGo Core Apps"? The name doesn't have to be perfect because it is a technical definition, not a marketing term. Then get the Marketing team to decide on how those MeeGo Core Apps will be branded in the outside world. My suggestion: "MeeGo World -- a world of apps for all MeeGo devices". The MeeGo 1.1 version of the branding rules will state that only apps that meet the defintion of "MeeGo Core Apps" can call themselves "MeeGo World" apps. > Before we require compliant devices to support apps with external > dependencies, I think we need to demonstrate that the value of that > justifies the cost and complexity. For example - show what can be done > with MeeGo Extras following this model. We can add this to a future > version of compliance if everyone says "wow, that's great - I really want > this on my next device" Fine, but just delete the concept of "compliance" for apps altogether and replace it with what we really need -- a simple marketing concept which can be explained to both vendors and users but which does not imply that there is something bad about apps which don't meet the criteria. Graham _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
