On Sep 16, 2010, at 1:02 AM, ext Skarpness, Mark wrote:
On Sep 15, 2010, at 1:16 PM, Graham Cobb wrote: On Wednesday 15 September 2010 17:13:43 Skarpness, Mark wrote: But that would mean that app stores would not be able to sell all compliant apps - which is not what we want. But app stores are not going to be in the business of selling compliant apps! yes they will - that is the whole point of MeeGo compliance - to get scale in the application ecosystem by enabling applications to run across multiple devices. Allowing applications to depend extra libraries that are also compliant does not affect this at all. It does not make difference any bit if application uses some library X is X comes with application or comes from public quality controlled repository. This whole "MeeGo compliant" thing is about creating very high volumes of low-end, mainly free, apps. The high value apps that app stores care about are not affected. And for low end apps, it has to be quick, easy and cheap to develop or port them. And many of them will be in MeeGo Extras. No, I don't agree. MeeGo compliance is about creating a large, unified application ecosystem with apps sold through multiple app stores on multiple devices. High end applications made by pig companies usually does not need to depend some extra libraries and they has man force to maintain packetize all libraries they need. In other end, there are big amount of smaller developers that rather would like to use ready made libraries tested and proof to work and without all hassle involved integrating and maintaining library. But mostly i where is the point, what we will achieve by forcing every developer pack and maintain copy of library and not allowing them to use tested and quality controlled version from repository ? Kate
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
