As the mBook images appeared this morning, so too have images of the MoodleTouch (mTouch) iPad App.  Check them out at  Looks like both mBook and mTouch for iPad will provide users with novel and unique displays for Moodle-based learning.

Post Pages - Post Inline - WIRIS

Kudos to both development teams!

Previous articleExclusive images of the first Moodle #iPad App: mBook
Next articleThe developers of MoodleTouch talk about their new #iPad app


  1. Well done to the developers – looks nice. I do wonder what this will bring to the iPad though (and similar future devices). The screen real estate of the iPad means pages are rendered nicely anyway and do not have the space constraints of mobile, where a custom Moodle skin seems more justifiable.
    Also, as a content developer, need to start realising that people will be operating their Moodle courses with their fingers rather than cursor and mouse.

    Well done and look forward to trying it out when it hits the store.

  2. Each mobile device will have its own UI experience standards and optimizations. So technically speaking one mobile Moodle skin for all devices is a hard goal. Another problem is HTML,it is a static markup, it does not matter you generate it dynamically the characteristics are still static. JavaScript also falls short on implementing UI optimizations popular for the new generation mobile devices. If you stick on a standard JavaScript it is a very hard and expensive task to handle some multi-touch scenarios.

  3. I forgot to mention HTML5. I hope HTML5, the new dynamic HTML standard, will change the way web sites/apps render content. Powered with the new CSS standards perhaps all web applications will render nicely on any kind of mobile device.

    When all this web story started developers cared about how they can produce content compatible on both Netscape and Internet Explorer, time went by and the problem become how web apps will support multiple browsers (Firefox, Chrome, Opera and IE to name few). Now the problem is producing content compatible both on desktop and mobile. And I guess some time later the problem will become producing compatible content for consumer electronics, mobiles and desktops.


Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.