a glimpse on meego
Post on 12-May-2015
Embed Size (px)
DESCRIPTIONA Glimpse On MeeGo
- 1.A glimpse on MeeGo
- Amanda Lam
- BEng Computer Systems Engineering, University of Warwick, UK
- Technical Writer of a multinational online services company
- Founder of Hong Kong Maemo / Moblin / MeeGo User Group
- HKPUG Executive Committee Member & Podcaster
- UMPCFever / Digital XY Voluntary IT News Editor
- Blog:http:// dadablog.net /
2. What is MeeGo?
- MeeGo is
- An open-source project
- Initially announced by Intel and Nokia at Mobile World Congress, Barcelona in February 2010
- A cross platform / architecture Linux distribution
- Merged from IntelsMoblin& NokiasMaemoprojects
- For Netbooks, Handsets, In-Vehicle Infotainment, Connected TVs, Media Phones and Tablets
- Maintained by theLinux Foundation
- Open to everyone who wants to use or contribute
- Supported by
3. 4. What MeeGo is not?
- MeeGo is NOT
- solely owned by Nokia
- solely owned by Intel
- just a smartphone OS
- replacing Maemo by totally ditching it
- totally replacing Symbian in Nokias smartphones
- having the same UI design for all products
- ready yet!
5. MeeGo Architecture 6. Why MeeGo?
- MeeGo is maintained by the Linux Foundation and is a full-feature, community-supported Linux distribution.
- Flexible UI customization
- Flexible architectural customization of the Core OS layer (e.g. Fedora 14, SuSE MeeGo, DeviceVM Splashtop etc.)
- Support multiple platforms and CPU architectures
- Easy application development and deployment using Qt
- To end-users:
- More advanced features can be made available
- More freedom to take over the control of the device
- More fun!
7. MeeGo Netbook UX UI design highly inherited from Moblin 8. MeeGo Handset UX UI concept seems to be borrowed from Maemo, WebOS and Android 9. MeeGo In-Vehicle Infotainment UX UI design looks like a mixture of Handset UX and Netbook UX! 10. MeeGo Tablet UX Finger-friendly UI design. Multi-touch supported. 11. MeeGo UX images: Some facts
- MeeGo Netbook, Handset and IVI UX images are available in MeeGo.com for public download.
- They are just demonstrating thereference UIsthat device manufacturers and developers should refer to.
- Commercialized end-user productsmay NOT look the same .
- By following theUI Customization Guidelines , end user products can have:
- Different icons, themes, visual effects, motion graphics, sounds and haptics for their branding
- Additional tailor-made plug-ins and applications
- Better device drivers
- Different app stores, e.g.
12. UI Customization Guidelines: Example 13. UI Customization: Examples Reference UI: Customized UI: 14. Commercialized Products vs Reference Platforms ofMaemo / MeeGo handsets and Internet tablets 15. Common Myths
- Myth #1:Since Nokia is pushing both Symbian^3 and MeeGo, it will be troublesome for developers to spend double-effort for app development.
- Huh, are you a developer?
- If you are, then you are cute. Because we haveQt !
16. Qt Cross-Platform App Development What is Qt and Why Qt?
- Qt supports app development on many platforms, including (but not limited to) Symbian S60, Symbian^3, Maemo & MeeGo.
- WebKit integration.
- Support hardware graphic acceleration operations with DirectFB and OpenGL ES.
- Support industry-standard audio and video formats, IP streaming, DRM, etc.
- Wrap hardware-specific operations into generic APIs.
- Native C++ support, but also provide bindings for other programming languages, e.g. Python, Java, Ruby, Perl etc.
17. Qt Cross-Platform App Development One IDE, multiple platforms: Qt Creator
- Provide simulators of different devices.
- Debug, test and deploy your app for different devices and platform in one single IDE.
18. Qt Cross-Platform App Development Qt Web Runtime
- Concept similar to Adobe AIR and HP Palm WebOS apps.
- Supported in Maemo 5, MeeGo, and Symbian^3.
- Example app:
19. Qt Cross-Platform App Development Real-Life Example: That Rabbit Game
- Developed in Qt.
- Runs on both Symbian^3 and Maemo 5.
- How did the developer tackle with different resolution of the devices (e.g. N900 vs N8)?
20. Common Myths
- Myth #2:MeeGo is still very immature, slow, buggy and feature incomplete. Why does it take Nokia so long to develop it?
- The MeeGo project was announced in February 2010, and at that point of time, development work was starting from ZERO!
- Android took around 2 years to develop before its 1.0 product was seen in the G1 phone; whereas Apples iOS took around 3-4 years to complete, before Steve Jobs announced iPhone.
- High transparency of the community development and audit processes might have misled the average-Joe consumers.
- Nokia is NOT the only one who is working on MeeGo. Intel, SuSE, Fedora, DeviceVM, Tencent, and many FOSS developers from the community are also involved.
- MeeGo Handset UX 1.2 will be released in April 2011with all major features completed.
- Thats why we will seeMeeGo-Harmattan(the original Maemo 6, or the Half-MeeGo) products in early 2011 first, before the development work of MeeGo Handset UX is complete.
21. Common Myths
- Myth #3:I just bought my N900 and now Nokia ditches Maemo and goes for MeeGo, and then announces that there is no MeeGo product for N900. WTF?
- Nokia did NOT ditch Maemo; instead, MeeGo is in fact the natural evolvement of Maemo.
- Nokia will not release commercialized MeeGo products on N900, but no one would stop users to install community versions of MeeGo if they wish. In such case, no support from Nokia is expected, of course.
- In fact, N900 is a reference hardware of MeeGo Handset UX development.
- There will still be bug fixes for Maemo 5, either from the official firmware upgrades or from the community maintained firmware.
- Multi-boot between Maemo and MeeGo is already supported.
22. MeeGo 1.1 Handset UX Demo 23. References
- Check out my blog athttp:// dadablog.net /
- Join the Hong Kong Maemo / Moblin / MeeGo User Group (facebook) athttp:// groups.to/hkmaemo
- Thank you!