1 / 12

MIT Mobile Platform

MIT Mobile Platform. Mobile Platform Services. MIT Mobile Web m.mit.edu Hosts mobile “modules” for MIT services Optimized for and accessible to all mobile browsers Native apps iPhone and Android apps Native-only features Content comes from m.mit.edu

afra
Télécharger la présentation

MIT Mobile Platform

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. MIT Mobile Platform

  2. Mobile Platform Services • MIT Mobile Web • m.mit.edu • Hosts mobile “modules” for MIT services • Optimized for and accessible to all mobile browsers • Native apps • iPhone and Android apps • Native-only features • Content comes from m.mit.edu • Device Capability Detection Service (DCD) • Mobile-service-prod.mit.edu • Classifies mobile browsers by capability • Simplifies mobile development for all of MIT

  3. A Brief History of MIT Mobile

  4. Future-proof device support • Mobile browsers are grouped into 3 “buckets” • Featurephone, Smartphone, and “Touch” (WebKit) • m.mit.edu displays custom look for each bucket • Grouped via Device Capability Detection Service • mobile-service-prod.mit.edu • Groups browsers according to capability • Free web service for all MIT applications • How Touchstone chooses its mobile interface

  5. Modules on m.mit.edu Sorted by 2010 popularity — does not include native app traffic.

  6. Choosing new projects • What is most useful to students? • What has the broadest impact for MIT? • Does it make sense in a mobile context? • Is its data readily available to us? • If it requires authentication, it should use Touchstone (no certificate support on most phones).

  7. Why Native? • Features not available in web browsers • Push notifications, background processing, offline use, better performance, rich SDK • Greater student involvement • Students are more interested to work on a native project than a website. • Can give students an official place to publish interesting native projects. • Marketing tool for the Institute • MIT’s name on the App Store. Helps MIT stand out because not many schools have native apps.

  8. Easing development burden • All code shared under MIT License • iMobileU • Group of 22+ schools around the world, most base their mobile site on MIT Mobile • Potential for student projects leveraging m.mit.edu • Accepting code contributions

  9. Questions • Do we consider tablets to be mobile devices? • iPads are used more like laptops than phones, should they default to the mobile web or the desktop web?

  10. m.mit.edu Web Demographics Page views during December 2010 Does not include native app traffic

  11. Mobile Web Traffic Does not include native app traffic

  12. Native App Statistics Native app traffic is not a meaningful statistic due to predictive caching and periodic checks (e.g. ShuttleTrack polls every 15 seconds).

More Related