Hi Carsten, I will try to answer your question from an IVI point of view.
The reference UX for MeeGo IVI is a means to demonstrate the capabilities of MeeGo and to exercise the underlying software stack. Car manufacturers, so called OEMs, together with their suppliers will replace the UX with a branded UX that fits the images and style of their make and models. The UX is a differentiating factor for them that ties into the design of the vehicle. Commonly, OEMs today use the same or a very similar UX for IVI systems in all of the models. That has to do with brand recognition as well as with economies of scale imposed by their current product development models. However, with a platform where the UX can easily be changed without huge cost it is quite likely that different models of the same manufacturer will have different UX's. A sedan targeted for business users will have a UX that is conducive to communication, business services, etc. A family van may have UX that is geared towards entertainment. A vehicle marketed to young drivers may have a UX that facilitates social networking. There is a catch-22 for the reference UX. Since the reference UX is what potential users and evaluators of MeeGo will see first it has to be sleek and capable enough to convincingly convey the message that MeeGo is a capable and powerful OS for mobile connected devices. Hence, it has to evolve continuously with the capabilities of the underlying software stack. On the other hand it needs to leave room for imagination and improvements. Otherwise it will hamper the adoption of MeeGo because the room for differentiation will be too little. :rjs On Wed, Jun 15, 2011 at 9:59 AM, Carsten Munk <[email protected]> wrote: > Hi, > > So, there seems to be a bit of confusion if "MeeGo UX" (as manifested > by the components, reference applications, design, etc) is supposed to > be a base reference UX for all/most verticals (IVI, Handset, Tablet > and even Netbook was proposed in a mailing list thread). The naming > would imply that - as well as that I believe IVI is using the > components too/apps? > > Can someone help provide a straight answer on what exactly reference > UX plans are (from design team, architecture, program management or > whoever)? Representatives from design team doesn't seem to think of > MeeGo UX design as anything beyond tablet[1] (thanks to Ned for > engaging us and discussing a difficult topic), so confusion is total > by now. > > I personally see good potential in the MeeGo UX (as defined above) on > many different verticals, but let's get the story straight, please - > so we can collaborate and contribute easier. Right now 1.3 seems like > a totally unknown road besides the Wayland plans and the EDS/Security > stuff - let's get some roadmaps on the table for UI side too. > > BR > Carsten Munk > > [1] https://bugs.meego.com/show_bug.cgi?id=19019#c11 > _______________________________________________ > MeeGo-dev mailing list > [email protected] > http://lists.meego.com/listinfo/meego-dev > http://wiki.meego.com/Mailing_list_guidelines > -- *Rudolf J. Streif* Director of Embedded Solutions The Linux Foundation [email protected] Mobile: +1 858 583 1683 Skype: rudolfstreif Linux Foundation Events Schedule: events.linuxfoundation.org Linux Foundation Training Schedule: training.linuxfoundation.org Join us this year in celebrating the 20th Anniversary of Linux! Watch the "Story of Linux" here: http://www.youtube.com/watch?v=5ocq6_3-nEw See all of the 20th Anniversary activities here: http://www.linuxfoundation.org/20th
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
