uMobile: Jasig-Sakai 2012

530 views

Published on

Published in: Technology, Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
530
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

uMobile: Jasig-Sakai 2012

  1. 1. uMobile OverviewTaking Mobile Applications and Devices to theNext LevelJennifer Bourey, UniconJasig-Sakai Conference 2012
  2. 2. About UniconTrusted Partner since 1993Expertise in Open Source Software for EducationProfessional Services for uPortal, Sakai, CAS, Shib,Grouper, and soon Student Success PlannerInnovative Cooperative Support Program
  3. 3. Common Themes to DateStudent or visitor-focusedCater to campus life use cases News, events Maps, transportation Maybe some course featuresOften no authentication or personalization
  4. 4. Current Challenges
  5. 5. Diverse AudiencesStudents Provide course resources, grades, schedules Support campus life and activitiesFaculty and Staff Payroll information, administrative resources
  6. 6. Diverse AudiencesProspective Students Admissions sessions and deadlines Visitor parkingAlumni Increase engagement and donations
  7. 7. Content CreationMany departments want to publish mobile contentDepartments have varying resources, technicalexpertiseNeed for delegated authoring, administration
  8. 8. DevelopmentMust develop code separately for each platform,mobile webRequires developers to work with new and diversetechnologiesNew APIs for mobile modules May change rapidly Might not offer enough flexibility
  9. 9. Complex IntegrationRequirementsComplex higher ed environments Data resides in many different systems One university many have many campuses, schoolsComplex audience Diverse user populations Users with overlapping roles
  10. 10. Collaboration ChallengesDesire for collaborationEvery university isdifferent!Harder to share open-source code effectively Graphic copyright Educause Mobile IT in Higher Education, 2011 http://www.educause.edu/MobileITinHigherEducation
  11. 11. App Distribution Must republish to make even minor changes to app Submission process adds delay, reduces control Potential for mismatch between server and app
  12. 12. Introducing uMobile
  13. 13. uMobile is a Campus Solution Delivers rich mobile campus platform for: Visitors Recruits Students Faculty Staff Alumni
  14. 14. uMobile is Native iPhone Android
  15. 15. 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
  16. 16. uMobile is open sourceDeveloped directly in Jasig control with all source codeavailable under Apache Software License 2.0Maintained by a community of developers governed bythe Jasig uMobile Steering CommitteeThis is real open source enterprise software (i.e. noseparate proprietary version that requires a licensingfee)
  17. 17. uMobile is Higher Ed 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
  18. 18. Personalizing the MobileExperience
  19. 19. Authentication Display user-specific information Calendars, course schedules Support single sign-on to other mobile university websites
  20. 20. Role-based ContentUse existing campus roles to drive personalizedcontentPotential data sources LDAP, Active Directory, Grouper Local (app-specific) group definitions Attribute-based ad-hoc groupsUse roles to distribute both module list and contentwithin modules
  21. 21. CustomizationImprove app usefulness and user engagement byallowing users to override defaults Toggle optional calendar, news feeds Select defaults and favorites Add/remove optional content modulesIntegrate with any desktop-side portal customizations
  22. 22. Authorization Control permissions on modules and module content Support privacy and data protection Protected department resources Directory data
  23. 23. Integrating with CampusResources
  24. 24. Development StrategyWhere possible, support open data formatsEnable common implementations out of the boxPublish open APIs for custom integrations
  25. 25. Standards-based DevelopmentEnable single sign-on CAS, ShibbolethConsume common data formats RSS, iCalSupport common user attribute and group datasources LDAP, Active Directory, Grouper
  26. 26. SIS DBMoodle Sakai
  27. 27. Campus Integration
  28. 28. Easing Development andDistribution
  29. 29. Native App ChallengesUnfamiliar and varied technology, dev environments iOS: Cocoa Android: JavaNeed to implement a feature multiple timesPublishing apps takes time and effortStill need another strategy for mobile browsersHard to leverage existing investment
  30. 30. A Better Strategy What if we could . . . Write features once Using familiar technology While offering both native and browser-based views And re-using existing application logic
  31. 31. Web-Centric ContentSingle codebase produces all mobile views Multiple native applications Multiple mobile web browsersNo update to the mobile client app requiredFamiliar development environmentPotentially share logic with desktop functionality
  32. 32. Native componentsprovide navigationWebView presentsmarkup from portal
  33. 33. Multiple Views Often need a different feature or interface on one platform Share backend logic as much as possible Business logic Controllers Render separate view layers as needed Separate layout / CSS for desktop, tablet, mobile May need to omit chrome from native views
  34. 34. Multiple Views Controller View Resolver Model Desktop Mobile View View
  35. 35. Calendar Views Desktop in-page Tablet Phone
  36. 36. Native App CodebaseBased 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
  37. 37. Native Components viaRESTREST services provide JSON data for User layout Map data Contacts informationREST feeds can easily be created for other areas
  38. 38. uMobile ServerRequest data from Return locationuPortal map service data as JSON Present native components uMobile based on portal data App
  39. 39. Portlet-based ContentJSR-168 / JSR-286 portlet standards Enables collaboration beyond uMobile projectGoogle Gadget integrationAlternate language modulesProvides a familiar, well-defined development modelAssures modules will work across uMobile versions
  40. 40. External ContentLeverage existing mobile investmentAllow departments to develop and control their owncontentEnable web-based development in other frameworksInclude external content via WebView, IFrame,WebProxy
  41. 41. External Content
  42. 42. Application Skinning
  43. 43. Administrative Access
  44. 44. Data Migration StatisticsCache Management Content Creation
  45. 45. Looking AheadAugmented reality map integrationEnhanced course and grades portletCustom mobile layoutsAdditional native app platforms
  46. 46. Augmented Reality
  47. 47. uMobile is Unique Truly Free & Open Source Software Provides Native App and Mobile Web Provides personalized experience and information Build on mature, proven, scalable, enterprise integration portal framework Ready for deployment at your campus nowNo other platform has all of these characteristics
  48. 48. More ResourcesJasig uMobile web site jasig.org/umobileYouTube channel youtube.com/jasigumobileuMobile Manual wiki.jasig.org/display/umobile
  49. 49. Questions? Jennifer Bourey jbourey@unicon.net

×