Open Source Enterprise Mobile Campus Solution. September 30, 2011

Transcription

1 Open Source Enterprise Mobile Campus Solution September 30, 2011

2 umobile is a Jasig Project Sponsor open source software projects for higher education. Non-profit membership organization. Provides: Community, Infrastructure, Consortium of higher Governance, Licensing, education institutions Incubation, Funding, and commercial Conferences, Outreach. affliates. 2 / 42

3 What is umobile? 3 / 42

4 umobile is a Campus Solution Delivers rich mobile campus platform for: Visitors Recruits Students Faculty Staff Alumni 4 / 42

5 umobile is Native iphone 5 / 42 Android

6 umobile is Web webos Android 1.5+ ios bada / 42 Windows Mobile (via Opera) MeeGo 1.1

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

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

9 Native App Mobile Browser Native App Application ApplicationServer Server Enterprise Directory 9 / 42 Enterprise Calendaring Learning Management Student Information...

10 umobile Demo 10 / 42

11 umobile Application Server 11 / 42

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

13 Managing Users & Groups 13 / 42

14 Managing Permissions 14 / 42

15 Statistics Cache Management 15 / 42 Data Migration Content Creation

16 umobile Architecture 16 / 42

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 17 / 42 Make phone calls, send s, etc.

18 Native App Codebase Based on Titanium Appcelerator JavaScript-based platformindependent development framework Compile shared codebase to iphone and Android applications with native controls Open source under the Apache 2.0 License 18 / 42

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

20 Map JSON Service Example umobile Native App Request data from umobile map service Return location data as JSON umobile App Server 20 / 42 Present native components based on JSON data

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

22 Native components provide navigation WebView presents markup from portal 22 / 42

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

24 Including Existing Sites config.js UPM.LOCAL_MODULES.twitter = { title: 'Twitter', fname: 'twitter', url: ' externalmodule: true}; 24 / 42

25 Configuring umobile Native App Simple configuration file controls Base portal URL Authentication method Person directory information Emergency contact numbers 25 / 42

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

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

28 umobile Roadmap 28 / 42

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 Portlet & Native Development Mobile Portlets Native Mobile App jqm views for portlets with mobile support Persistent Authentication Mobile support to additional portlets Appropriate Caching Performance tuned on mobile devices Contacts Brand new portlets targeted for mobile 30 / 42 Maps

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

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

33 More Resources Jasig umobile web site (learn more and download) jasig.org/umobile YouTube channel youtube.com/jasigumobile Jasig umobile wiki wiki.jasig.org/display/umobile 33 / 42

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

35 Questions & Answers 35 / 42

36 36 / 42

37 37 / 42

38 38 / 42

39 39 / 42

40 40 / 42

41 41 / 42

42 42 / 42