[MeeGo-ivi] meego ivi UX working group
rudolf.streif at linuxfoundation.org
Mon Apr 18 11:04:17 PDT 2011
Within the MeeGo project context Working Groups are defined for the
different device categories or verticals. Please refer to
http://wiki.meego.com/Working_Group_Process for the details. A Working Group
addresses all the requirements and the roadmap for its vertical. That
includes the reference UX and APIs etc. to enable the UX. So launching a
separate Working Group for the UX is technically not possible within the
MeeGo project context.
I encourage everybody to collaborate on the UX using this mailing list and
the MeeGo IVI Wiki as well as MeeGo's feature tracking system. Like anything
in MeeGo these are open collaboration platforms.
If you are interested in IVI UX design and have ideas, a prototype, etc.
please add them to the still blank IVI UX Wiki page (
http://wiki.meego.com/In-vehicle/Roadmap/UX) and notify this mailing list
about your thoughts.
On Wed, Apr 6, 2011 at 12:37 PM, Kevron Rees
<kevron_m_rees at linux.intel.com>wrote:
> I'm pondering about the meego-ivi UX and how it can be improved. Would
> it be helpful to establish an IVI UX working group where we could
> collaborate over a "reference" UX and establish design and
> implementation of core IVI specific apps in the open? This group would
> establish a process where UX designers can collaborate over core
> application design that incorporates core features and requirements that
> are currently defined and the the actual implementation of those
> There are a number of community members, myself included that I think
> would work with together on well defined/well designed core
> applications. Otherwise, they may end up doing their own thing which
> may not fit well in the meego ivi ux.
> Does this seem like a reasonable thing to have?
> Comments and discussion welcome.
> MeeGo-ivi mailing list
> MeeGo-ivi at lists.meego.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the MeeGo-ivi