Hi, please keep the "MeeGo compliance" part in the subject of this spin
off thread - thanks!

Ibrahim from The Linux Foundation is driving the MeeGo compliance
definition. Hopefully we can have a first version of the guidelines
published soon, currently under private drafting and review to sync
legal, technical, marketing and resourcing aspects.

ext Cornelius Hald wrote:
> So how far may companies go if the differentiate the UI? What is allowed
> to still be called Meego or Meego-Compatible? Is it only theming or can
> they provide their own UI framework?

The main objective behind the MeeGo compliance is to guarantee
                      binary compatibility for applications across
multiple MeeGo products. All the rest (definition of the official MeeGo
API, architecture...) is a consequence of this basic goal.

This gives a lot of freedom to whoever wants to deploy a MeeGo based
product. The MeeGo project doesn't go after a single user experience
common to all MeeGo based products. Then again, if we do things right
the MeeGo reference user experience will be a good default candidate and
any vendor having to rationalize resources will probably think it twice
before departing from it at own cost and risk. It's a choice for
platform developers.



> How will you manage that users always have a consistent look & feel even
> with 3rd party applications? And how should a developer face this issue
> - it's surely not a solution to implement every 3rd party application
> for every vendor specific UI framework.

Thinking out loud only, but we can see two basic trends in application
UIs: the ones prioritizing platform look&feel integration and the ones
pushing their own look&feel across different platforms. It's a choice
for application developers.

Going back to the original point, what really matters is that MeeGo
users can enjoy the combination of MeeGo devices and applications of
their choice no matter what choices have been made by the developers of
those devices and applications.



> Too many questions, I know :)

But good ones!  :)

-- 
Quim Gil
open source advocate
MeeGo Devices @ Nokia
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev

Reply via email to