The document summarizes information about Moodle Mobile, including upcoming speakers at Moodlemoot Spain 2012, a brief history of Moodle Mobile releases, new features being developed for mobile and tablet apps, considerations around using HTML5 for the apps, differences in mobile and tablet browsing designs, and factors to consider when choosing HTML5 and JavaScript frameworks. It concludes with a demo link and thanks for attending.
2. Speakers
Martin Dougiamas:
CEO & founder Moodle
Juan Leyva:
Moodle Developer (since 2003) working @ CV&A Consulting
Developer of plugins:
Configurable Reports
jmail
LTI Provider
UMM (Unofficial Moodle Mobile)
Anonymous posting in forums, Collaborative real-time editor,
ConfigTabs, Forum discuss subscription,
3. Brief history
Moodle 2.1 (1st July, 2011)
Mobile service
Mobile app for iPhone and iPad
Browser detection
Moodle 2.2 (5th December, 2011)
MyMobile theme
Content button in the mobile app
Moodle 2.4 (December 2012)
Mobile and tablet HTML5 app for Android, iPhone, iPad
And hopefully Windows Phone, BlackBerry and Firefox OS
4. New features
Mobile and tablet version
Different design
Same app
Notifications
Push notifications (Android and iPhone, iPad)
Polling notifications plugin for other platforms
Remote configuration
Remote CSS for styling the app
Remote configuration for default settings (language, app name, etc..)
Customizable
Custom themes and plugins
5. HTML5 apps
Advantages
Open web standards technologies
Write once, deploy everywhere
Usually cheaper to develop and maintain because:
There is a big number of HTML, CSS, Javascript developers
The technologies are very close to Moodle ones
Disadvantages
Performance
Look and feel
Use native mobile functionalities
Browser and mobile fragmentation
6. Mobile and tablet browsing
Different design (layout, animations and browsing) for mobile and tablets
Mobile
Similar to the current navigation
Tablet
Facebook style navigation
7. Choosing the right technology
Which HTML5 framework should we use?
(jQuery Mobile)
Which Javascript framework should we use?
(Backbone)
Key points:
Performance
Learning curve
Documentation
Integration with HTML5 technologies
Community support
Roadmap
Maturity
License