Another solution could be to have a generic UI, usable for any device, with a choice for the manufacturer to improve, skin or implement a different UI. That will allow the use of MeeGo on any device not designed to be shipped with MeeGo.
Le 2 avr. 2010 à 21:36, Deepak D a écrit : > Hi, > > Well I don't know the answer. But I strongly feel it should be different. > As I can see with Android, the difference is only with the manufacturer > (Brand) and rest all looks the same. > I feel presently what is happening with Android is if you have brand name to > show case thats it! The content remains same. > This should be totally avoided because it takes out the edge from a > manufacturer to make their mobile phone distinct. > It should be more or less similar to J2ME, which enables manufacturers to > have their own implementation but core part works same across devices. > This will also enable lot of low end device manufacturers to adopt to Meego > sooner rather than later and make distinct looking phones. > > Thanks for starting off this debate, its the right time to decide what should > be the case. > > - Deepak > > On Fri, Apr 2, 2010 at 12:28 PM, Matthieu Chaton <[email protected]> wrote: > Hi, > > I've just a question concerning the UI in MeeGo. > Will the UI be common to every device using MeeGo (at least common for a > specific target : phone, notebook, etc), or will the UI be specific for each > device (eg : if nokia and samsung decide to use MeeGo for a device, will they > share the same UI (like android) or will they have different implementations > ?) > > Thanks > > _______________________________________________ > MeeGo-dev mailing list > [email protected] > http://lists.meego.com/listinfo/meego-dev > > > > -- > Thanks, > Deepak
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
