1. You Need to go Mobile NOW…But HOW?
In-session Poll:
You Need to go Mobile NOW…But HOW?
Collaborate with the UC !
UC Panelists:
Rose Rocchio, Eric Bollens – UCLA
Bill Allison – UC Berkeley
Mojgan Amini – UCSD
Rich Trott - UCSF

2. Introducing our Panel Rose Rocchio, Director ECTG, UCLA
Bill Allison, Director, Campus Technology Services, UC Berkeley
Eric Bollens, MWF Architect, UCLA
Mojgan Amini, Manager UXT, UC San Diego
Richard Trott, Director, UCSF

3. What is this about? The Mobile Trend A UC Collaboration
The UC Mobile Strategy
Device/Technology Agnostic
What is a Mobile Framework?
Benefits (hard & soft)
Savings & ROI
Engagement: Staff, Researchers & Students
Imagine: A Learning Toolshop

4. Mobile is global
half the planet has a mobile device (3.4 billion people)
mobile data usage is expected to grow
10 fold over the next four years
Just look at these stats.
by 2015, 90% of the earth will
have mobile coverage

6. MWF Background & Status
Educause 10/09
UCLA Mobile launched in Sept 2010
Made MWF Code Available Spring 2011
UC Mobile Collaboration Status: @ 7/10
5 Campus mobile sites launched
2 Mobile Campus mobile sites in development
3 Campuses evaluating Framework

7. SOLID PRINCIPLES Technology Agnostic Device Agnostic
MWF (CSS, HTML5, JS)
PHP Apps
Java Apps
Ruby Apps
Python Apps
Epic Apps
.NET Apps

8. Distributed UC Collaboration
Student built Mobile Apps
Researchers ( mHealth etc.)
Distributed Developers
Campus Central IT
MWF
The MWF is an example of a Distributed UC Collaboration:
The MWF strategy relies on leveraging both students and faculty researchers
MCG

9. 11-12 Investment & Savings In House Unit specific Staff only UC Saved:
Investment Analysis
SYSTEM TOTAL
Type of Staff
FTE
MWF Core development
1.63
Campus Mobile Management
1.50
for MWF infrastructure & hosting support
0.71
Campus Mobile Presence - Central (tools, training, support)
4.33
Campus Mobile Presence - Distributed
2.20
Totals for Staff/Students
Total FTE investment by Campus:
10.36
Units on campus utilizing the MWF 53
FTE Estimate to mobilize w/o MWF
0.50
26.50
Estimated Savings in FTE by using MWF
15.26
Avg FTE cost to mobilize data/unit
0.20
In House
Unit specific
Staff only
UC Saved:
~$1.5 Million

10. UC Mobile Momentum! Critical Success Factors
Based on Solid Principles
Collaborative UC Environment
The MWF Engages, Empowers and Enables Developers
Student Demand is high
Fiscally Responsible/ Long Term strategy
Poll Results:
Panel Preview
(Berkeley, UCLA, San Diego’s Re-envisioning and SF’s Technical Contribution)

11. UC Berkeley and the MWF http://m.berkeley.edu Launched: 1/1/11
404 Not Found
August 2010

12. Implementing UC Berkeley’s Mobile Strategy
Leverage
Central campus mobile site
Web App Mobile Use Cases
Innovation
Data Freedom

13. Power to the People!

14. 10 Apps in 3 days…

15. Takeaways
Given volatility and rapid technical evolution, huge UCB upside for aggressive, agile posture.
Investment in mobile multi-point: baked-into vendor products (Box.net, Google, Microsoft), leveraging traditional web at presentation layer (MWF), enterprise strategies (MWF/Kuali).
Deploying technology platforms centrally for distributed use, & then magnifying investment via proper incentives
The Happy iPad Winner

16. UCLA: Mobile Now! But How?
Why hadn’t people already gone mobile?
Lacked resources or experience
Didn’t view mobile as a priority
Distributed campus environment
No central strategy or guidance
What would change this for them?
One easy to learn development platform
No need to worry about device-by-device nuances
Freedom to run in their own environment

17. UCLA: Framework Details
Available frameworks not distributed enough
And so the MWF is born…
The mobile web presents a common platform
One set of HTML markup can work on all devices
Any language can leverage CSS and Javascript
Framework serves different levels to difference devices
Apps just need to output HTML that uses the MWF API
Federated infrastructure reduces costs
CSS and Javascript can be hosted/maintained centrally
Applications using MWF can be distributed anywhere

18. UCLA: Coalition of the Willing
Initial groundwork [Mar – Jun 2010]
Began approaching core data owners
Helped other data owners build apps
Wider developer outreach [Jun – Aug 2010]
Campus-wide IT presentation
Enthusiasm was high: simplicity & low entry costs
Launched UCLA Mobile in September 2010
Released to the UC in August 2010
Source available on Github in May 2011
Prototyped the framework and Centrally developed a few apps

19. UCLA: Project Status 22 campus units participating
Engaging researchers with MWF
Ohmage, cross-platform mobility campaigns tool
Mobile learning tools under development
Glossary of Organic Chemistry
Mobile Web Response System
Student MWF contest coming this winter
Prototyped the framework and Centrally developed a few apps

20. UCSD’s Framework Selection1
Involved Campus IT Groups
ACT
Student Affairs
Libraries
A focus group, consisting of IT-leads across the campus, took part in evaluating and defining the recommendation for a campus mobile framework. The following campus departments were represented in this group:
Academic Computing and Media Services (ACMS)
Administrative Computing and Telecommunications (ACT)
Biological Sciences
The Colleges
Libraries
Scripps Institution of Oceanography (SIO)
Student Affairs

21. UCSD’s Framework Selection2
Defined Selection Criteria
Sustainable over 1-2 years
Open source or industry standards
Support various mobile devices
Little training for development
Easy to replace in the future
Selection Criteria:
Sustainable over a 1-2 year period of time.
Include open source or industry standards.
Support various mobile devices.
Require little training for development.
Easy to migrate to a new technology in the future.

22. UCSD’s Framework Selection3
Reviewed Mobile Frameworks
Reviewed 8 Mobile Frameworks: UCLA Mobile Web Framework,
MIT Mobile Web Project,
SproutCore,
PhoneGap,
jQuery Mobile,
WebApp.Net,
Sencha Touch,
iMobileU

23. UCSD’s Framework Selection4
Unified Recommendation
Ease of use
Framework features
Documentation
Cross-platform support
Maturity
Extensibility
Learning curve
Integration with Campus CMS
Perform in-depth review of proof-of-concepts of chosen platforms.
5 different campus entities (IT/programmers) presented their proof-of-concept mobile applications of UCLA Mobile, and Sencha Touch to the focus group.
The following categories were addressed: ease of use, framework features, documentation, cross-platform support, maturity, extensibility, learning curve, and integration with our campus CMS.

24. UCSD’s Mobile Empowerment
Self-Service Mobile Web Toolbox
Campus-branded Mobile “Decorator”
Kitchen Sink Sample Application
UC San Diego empowers users to build mobile apps by providing tools, documentation, and guidance:
Mobile Decorator
Kitchen Sink
SLA
Governance QA
Usability/UX

25. UCSD’s Enabling Students
(My TritonLink Screens)
Well now students can access their class schedule on their mobile device through MyTritonLink. Their class locations are plotted on google map that provides them walking directions using GPS.
Lost your notes today? no worries, you can pull the podcast of the professors lecture and hear what he had to say.
That’s what we’ve focused on for the new UCSD mobile. Our goal is to make life easier for students, staff, faculty, visitors and others no matter what mobile device they are using.
Ok, I’d like to set the stage for a video I’m going to show

26. UCSF’s MWF Experience
MWF helped us turn competing projects into collaborating project teams.

27. UCSF: Advocacy & Challenges
People want a solution that does not require them to have to think about handhelds at all.
Mobile-First design

28. MWF Conference 2011 2 days of presentations
MWF, mHealth, Mobile in Research, Mobile Web Architecture & Engineering, etc.
22 speakers from 7 campuses
182 attendees (local + remote) from 9 campuses
1 day mobile development workshop
Moving forward:
Conference & Events App
MWF Conference 2012

29. 2011 UC MWF Conference Conference
Attending
Speakers
In Person
Remote
Total Attendees
UC Berkeley 2 22 24
UC San Diego 3 23 26
UC Davis 1 6 7
UCSF 9 12
UCSC
UCLA 44 35 79
UC Irvine 17 19
UC Riverside 4
UC Santa Barbara 5
UC Merced
UCOP
TOTALS: 61
121
182

30. MWF Conference Mobile App

31. Conference Administration

32. MWF Contest Drawing modeled after UCB’s recent drawing
Demonstrate the value of the MWF
Ease of use
Speed of development
Ease of deployment
Entries from participants of the UC MWF conference
Originally local and remote participants from UCLA
Opened up to all conference participants, both local and remote

33. 8 Apps in 12 Days

34. 2012 MWF Conference Open beyond the UC Proposed tracks
Educational, non-profit and student rates
Special invitation to CSU’s and California CC’s
Proposed tracks
Mobile development and architecture
Mobile strategy and governance
Mobile learning and services
Mobile research and mHealth

35. Working with Higher Ed Educause ACTI Group MWF Working Group (6 goals)
Track the Mobile Web Framework space
Share best practices to engage and mobilize a campus
Agree on a Web Services architecture (Rest/Soap)
Mobile Interoperability (web services) with the LMS -
for student, course, enrollment, notices
for collaborative tools (wiki, discussion board…)
for Quizzes, polls, interactivity
Presenting our Interoperability goals to IMSglobal
HEMC: Higher Ed Mobile Coalition -> Educause ACTI

36. Looking Ahead as a System
MWF Roadmap
UC Strategic Mobility Goals
Engage & Mobile Enable Students
Envisioning a mobile “Toolshop”

37. MWF Roadmap & Plan

38. Engage & Mobile Enable UC
Engages staff in new technologies
Encourages sharing of code & best practices
Impact: Affinity groups form across the UC
Medical Schools & mhealth researchers
Extension schools
Launching a Student Workshop/Contest
Allows usage to define value & priority

39. Learning & Research Toolshop
Survey
Conference
Clicker
Geo- Aware
Glossary
Student tools
Classes
Syllabus
Study List
Grades
Roster
Notifications
MWF 1.2/3: personalization, Javascript interactivity
Student tools:
clicker
glossary
studylist
gradebook
account balance
dining menus

40. http://mwf.ucla.edu Questions? Get Involved:

41. Appendix

42. Educause ACTI MWF’s 6 Goals
Share strategies to Enage, Empower and Enable HE to Mobilize
Goal 3:
Explore and understand the tradeoffs between Web Services architecture
Crowdsource it!
Favor Agility & Flexibility
Goal 1:
Track activity in the Mobile Framework arena
Goal 4:
Define Course Data Web Services
Goal 6:
Define Interactive Data Web Services
Make
Real
Time
Feed
Back
Count
Learn Anytime, Anywhere
Goal 5:
Define Collaboration Data Web Services
Communicate

43. The UC’s Mobile Strategy
UCLA (22)
UCSD (6)
UCSF (8)
UCI (3)
UCR (2)
UCSB (5)
UCB (5)
51 UC Units have an MWF Mobile Presence

44. UC Data Interoperability? (Courses/Students/OIPP Enrollment/Grades)
Fig 1: Point to point campus Integration
Figure 2: UC Course/Student Web Services OR

45. UC Mobile Usage Statistics
~3/4 Million Total Visits to UC Mobile Sites
2.2 Million Page Views

46. The Approach: Native vs. Web
Native Application
Con: Lack of cross-platform portability
Pro: Commonly have robust APIs and features
Con: Central architecture and distribution
Web Application
Pro: High portability among comparable browsers
Con: Apparent lack of deep features and APIs
Pro: More flexible with architecture and distribution
Pro: Maintenance of application significantly lower

47. UCLA Welcome Week App

48. UCLA Welcome Week App Intended outcomes for students:
Deliver information about back to school activities
Raise student awareness about UCLA Mobile
Intended outcomes for staff & administrators:
Show how conducive mobile is to such a context
Show how simple it is to implement MWF
Live demo:

49. UCLA Welcome Week App From POC in 2010 to Marketing Tool in 2011
Intended outcomes for students:
Deliver information about back to school activities
Raise student awareness about UCLA Mobile
Intended outcomes for staff & administrators:
Show how conducive mobile is to such a context
Show how simple it is to implement MWF

50. UCLA Welcome Week App

51. UCLA Welcome Week App

52. TOTAL DEVELOPMENT TIME:
UCLA Welcome Week App
The process:
Gathered information in spreadsheets from content providers responsible for the events
Developed a few lightweight data models
Created HTML output that used MWF
TOTAL DEVELOPMENT TIME:
3 DAYS

53. UCSD’s Enabling Students