Child pages
  • Home
Skip to end of metadata
Go to start of metadata

This is the home of the IU Mobile Collaboration Space space. This is a work in progress for the upcoming meeting with UCLA, Berkeley, and IU to discuss evolving strategies.

IU Mobile 2.0 Technology Strategy

We are strongly considering moving away from native applications and towards an HTML5/CSS3/JavaScript compliant solution. There are a number of reasons to move in this direction. One of the leading reasons is to better collaborate since the IU skill set is based in web application programming and not in native programming. We have found it very difficult to keep up with the demand for new services in the native space, let alone the bug fixes. Combine that with the slow to market Apple approval process, and it's a easy choice to move to a web friendly solution. In addition, open source products like PhoneGap and JQuery Mobile have come a long way in the past few years. PhoneGap is used to wrap an HTML webapp in a native application while providing a cross platform JavaScript API to the device's capabilities and also allow IU to deploy IU Mobile into the various App Stores as if it were a native application.

PhoneGap

  • Currently available for: iOS, Android, BlackBerry, Palm, Windows, and Symbian
  • Vary slightly but goal for each platform: accelerometer, camera, compass, contacts, file, geo location, media (audio recording), notification via sound and vibration, and storage.

JQuery Mobile

  • Currently available for: iOS, Android, BlackBerry, Bada, Palm, Windows, WebOS, Symbian, and MeeGo
  • Built on the very powerful open source JavaScript Library JQuery
  • Lines up with Kuali Rice KRAD v2.0's use of JQuery UI
  • Skin-able and touch optimized
  • Currently sponsored by: Filament Group, Mozilla, Palm, BlackBerry, Nokia, Device Atlas, Adobe, and DotMobi

Screenshots of the JQuery Version of IU Mobile

IU Mobile Architecture in Relation to Shared Services Vision

The IU Mobile architecture follows the vision of shared services coordinating over a service bus, passing secure data between systems, and then presented to the user with a common look and feel.

Passing Personal Data Securely through Web Services

These days it's not enough that web services solely provide public data feeds. We now need a secure two-way session based and sticky communication model. We have chosen REST-style web services authorized between systems via OAuth, specifically OAuth 1.0 Revision A. A great article that overviews OAuth can be found here. The authentication is based on a mobile version of Jasig CAS, which is the same as desktop CAS except that a cookie can be stored locally for a fixed amount of time (2 weeks) so that entering credentials on a mobile device is not a tedious task.

  • No labels