Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

uMobile Phase 2

uMobile's phase 3 will consist of additional portlet development, feature enhancement, and bug fixes resulting in a uMobile server and native app 1.2 release.

Architecture Updates

Application State Save and Restore

The application currently exits the app completely when the user closes the app or navigates to another app (like the native map). This was due to iOS memory issues causing the app UI to degrade after opening up other apps that require a lot of memory. The newer Titanium SDKs claim to have better memory management, so it may require little effort to implement. Otherwise, the app should save the state (what portlet is opened, and what data is being viewed) as the app is used, and restore to that state when the app is opened again.

UI Enhancements

When the device is oriented in landscape mode, the primary title bar and secondary nav bars take up a significant amount of screen real estate. We should evaluate strategies for handling landscape-mode navigation that are compatible with WebView-based portlets.

Module Updates

Map

The current map implementation might be enhanced by adding multi-campus support.

Features important for making the map module more competitive in the uMobile 1.1 release include:

  • Multi-campus support
  • Allow user to center map to geolocation
  • Tablet-specific UI, particularly utilizing the iPad Split View to display results in list view and on map with one view.

Courses

Alternate merged announcement view

Discussion at the Sakai conference indicated that some institutions would prefer a merged view of synoptic information for announcements, etc. While the current by-course view is valuable, we might add an alternate view that merges information from multiple courses.

LMS integration implementations

As of uMobile 1.1, the courses module has a basic open-source connector for Sakai, with a Moodle connector in-progress.  These integrations should be enhanced, preferably in collaboration with campuses currently using each LMS.

It would also be beneficial to implement the new uMobile search API in the courses portlet, allowing the portlet to report search results from implemented LMSs.

Directory

Contact download

uMobile users should be able to download directory contact information to their phone's local address book.

Attribute Copy

Users should be able to copy the value of a particular field, to paste in another program (such as a note, an existing contact, email, etc).

Tablet-specific UI

The directory's native interface would benefit from a tablet-specific UI that makes use of the additional available screen real estate, particularly use of the iPad Split View.

News

Media

RSS and Atom feeds support inclusion of media such as images, video, and audio. Some initial support is available for parsing simple feed thumbnail images and parsing mp4 video from Berkeley's Opencast implementation. The support is by no means complete, and adding additional support for more common video types and iTunes' podcasting format would be valuable.

Import/Export

The news portlet's import/export system is currently incomplete and will not support a full export and import of news feed sets.

Calendar and News Common Features

User Configuration

Users currently may turn on and off predefined calendar and news feeds for which they originally received default registration, but have no access to non-default feeds. Both portlets need more complete mobile user customization interfaces that allow selection of non-default feeds and allow users to add their own custom feeds.

Announcements/Notifications

uMobile is in need of a high-quality announcements and/or notifications portlet. Jasig does not currently offer such a portlet with a jQuery Mobile-based interface, though the Announcements Portlet might be a good starting point, as it already has a custom mobile interface. Alternatively, the in-development Notification Portlet from the University of Manchester might be a good fit.

  • No labels