Linked by David Adams on Thu 29th Jul 2010 17:15 UTC, submitted by Panajev
Permalink for comment 434805
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
More News »
Sponsored Links



Member since:
2008-12-26
I actually took some time to take a look at LiMo ;-).
From
http://blogs.ft.com/techblog/2009/11/limo-grabs-limelight-from-andr...
LiMo is especially suited to carriers - it offers a software stack and middleware but, unlike Android, no specific user interface.
So basically, you get LiMo by grabbing MeeGo, throwing away the user interface and replacing Qt with Gtk. And letting the operator make the user interface by themselves using Gtk+.
If I were a LiMo member, I'd seriously consider joining the MeeGo initiative and contribute to making a reference "Feature Phone UX" implementation in Qt. The current "Handset UX" may be a bit too heavy for low end phones, but I believe MeeGo would already offer more than LiMo even without the pre-existing UX work.