6. uMobile is Web
webOS 1.4.1+
Android 1.5+
iOS 2.2.1+ Windows Mobile 6.5.1+
(via Opera)
bada 1.0+ MeeGo 1.1
6 / 42 30 Sept 2011
7. uMobile is Open Source
• Developed directly in Jasig control
with all source code available under
Apache Software License 2.0.
• Maintained by a community of
developers under governed by the
Jasig uMobile Steering Committee.
• This is real open source enterprise
software (i.e. no separate proprietary
version that requires a licensing fee).
7 / 42 30 Sept 2011
8. uMobile is uPortal
• uMobile builds on Jasig’s
experience in enterprise
higher education integration portals.
• Sophisticated and mature framework for
personalization, aggregation, access control,
integration, and administration.
• Production instances supporting millions of users.
• uMobile can be adopted stand-alone or as an
extension of a “traditional” enterprise portal.
8 / 42 30 Sept 2011
9. Mobile
Browser
Native App Native App
Application Server
Application Server
...
Enterprise Enterprise Learning Student
Directory Calendaring Management Information
9 / 42 30 Sept 2011
12. Framework Support
• Authentication and Authorization
• Groups and Permissions
• Layout Management / Personalization
• Administration and statistics
• Deploy and configure various modules
• Update static content information
12 / 42 30 Sept 2011
17. Why Native Apps?
• Discoverability
– Users expect to find something in
the App Store / Android Market
– If you don't put something there, someone else will...
• Native Controls / Abilities
– Access to camera, microphone, accelerometer, GPS, etc
– Access to platform APIs
• Make phone calls, send emails, etc.
17 / 42 30 Sept 2011
18. Native App Codebase
Based on Titanium Appcelerator
• JavaScript-based platform-
independent development
framework
• Compile shared codebase to
iPhone and Android
applications with native
controls
• Open source under the
Apache 2.0 License
18 / 42 30 Sept 2011
19. Portal REST Services
• REST services provide JSON data for:
– User personalization and layout
– Map location data so it can use local mapping
– Contacts information
• REST feeds can easily be created for other areas
19 / 42 30 Sept 2011
20. Map JSON Service Example
uMobile Present native
components based on
Native App JSON data
Request data
Return
from
location data
uMobile map
as JSON
service
uMobile
App Server
20 / 42 30 Sept 2011
21. Web Views
• Portlets easily included as mobile modules using a
Web View
• Portal omits portlet chrome for native app views
• jQuery Mobile provides
– Skinning framework with support for multiple mobile
browsers (not just WebKit)
– Event listeners for mobile interactions such as tap,
swipe, and pinch
21 / 42 30 Sept 2011
22. Native components
provide navigation
WebView presents
markup from portal
22 / 42 30 Sept 2011
23. Advantage of Web Views
• Single codebase produces all mobile views
– Multiple native applications
– Multiple mobile web browsers
• No update to the mobile client app required
• Familiar development environment
23 / 42 30 Sept 2011
26. Additional Configuration
• Skinning / Branding
– Simple skin file defines colors and styles for native app
– Uses CSS-like attributes
• Localization
– Messages file defines strings for message keys
– Default language defined in configuration file
26 / 42 30 Sept 2011
27. Development Standards
• JSR-168 / JSR-286 portlet standards
• Google Gadget integration
• Alternate language modules
• Provides a familiar, well-defined
development model
• Assures modules will work across uMobile
versions
27 / 42 30 Sept 2011
29. uMobile 1.0 Released
• 1.0 GA Released September 15, 2011
• Reliable platform for delivering web-based and
native content
• Provide high-quality, easily customizable browser
and native skins
• Develop portlets that exercise and demonstrate
the framework
• Baseline documentation
29 / 42 30 Sept 2011
30. Portlet & Native Development
• Mobile Portlets • Native Mobile App
– jQM views for portlets – Persistent
with mobile support Authentication
– Mobile support to – Appropriate Caching
additional portlets – Maps
– Performance tuned on – Contacts
mobile devices
– Brand new portlets
targeted for mobile
30 / 42 30 Sept 2011
31. Upcoming Roadmap
• More native app integration
– File upload / download, video
• Broader native support
– Blackberry, tablets
• Custom layouts
• Working with institutional members of the
Steering Committee on specific campus use cases
31 / 42 30 Sept 2011
32. Invitation to Contribute
• Opportunity to be a contributing stakeholder
• Request for resources to accelerate the project
• Influence the direction of uMobile
• Participate in regular, interactive status calls
• Take a leadership role in the communications
32 / 42 30 Sept 2011
33. More Resources
• Jasig uMobile web site (learn more and download)
– jasig.org/umobile
• YouTube channel
– youtube.com/jasigumobile
• Twitter
– @jasigumobile
• Jasig uMobile wiki
– wiki.jasig.org/display/umobile
33 / 42 30 Sept 2011
34. uMobile is Unique
• Truly Free & Open Source Software
• Provides Native App and Mobile Web
• Provides personalized experience and information
• Built on mature, proven, scalable
enterprise integration portal framework
• Ready for deployment at your campus now
No other platform has all of these characteristics
34 / 42 30 Sept 2011
Initial native apps for iPhone and Android. Talk about having a presence in the app store.
Browser-based support phone build on recent versions of Android, iOS, Palm, Windows Mobile, Bada, and Meego. Provides support for phones that don’t have a good app story or users who don’t want to download the app.
Emphasize that the project is already in the Jasig sandbox, documentation and planning is in Jasig wiki, and project has been submitted for incubation.
Various native appl platforms Mobile web experience Content modules provide capabilities to users New modules can easily be implemented, integrated, and deployed <wait for guest view> Anonymous guest view for visitors / prospective students Personalization to different users students, faculty, staff, alumni, etc Some modules can be personalized administratively Example: calendars and news can be pre-configured Users can further customize with their own preferences Some provide content unique to the user, calendars, courses <wait for server view> uMobile server provides rich administrative console Delegated administration of content, groups, and permissions maintenance and configuration, caching and usage statistics Add new content from variety of sources: rss/atom, calendar, etc WYSIWYG static content creation with scheduled publishing <wait for development screen> Easy to include other external mobile websites Simple configuration file entry
Talk about uPortal permissions framework, using person directory as an example. We can set permissions for viewing users by group, as well as user attributes. For example, we can make students visible only to other students, or restrict viewing a physical address to administrators.
Talk about new tools for managing permissions, power of uPortal frameworks.
Additional administrative tools and frameworks - includes WYSIWGY content creation, cache management. Portal can track usage stats, and have a well-tested strategy for migrating between versions. Slide is only a subset of what’s available.
Don’t have to create component API from scratch. Get access to a well-thought-out, well-tested API.
