The Mobile Web Framework UC Panelists: Rose Rocchio UCLA Tom Tsai - - PowerPoint PPT Presentation

▶
the mobile web framework
SMART_READER_LITE
LIVE PREVIEW

The Mobile Web Framework UC Panelists: Rose Rocchio UCLA Tom Tsai - - PowerPoint PPT Presentation

Dec 11, 2023 254 likes •585 views

Engage, Em power & Mobile Enable! The Mobile Web Framework UC Panelists: Rose Rocchio UCLA Tom Tsai UC Berkeley Mojgan Amini UCSD Rich Trott UCSF Introducing our Panel Rose Rocchio, Director ECTG, OIT,

slide-1
SLIDE 1

The Mobile Web Framework

UC Panelists:

  • Rose Rocchio – UCLA
  • Tom Tsai – UC Berkeley
  • Mojgan Amini – UCSD
  • Rich Trott ‐ UCSF

Engage, Em power & Mobile Enable!

slide-2
SLIDE 2

Introducing our Panel

  • Rose Rocchio, Director ECTG, OIT, UCLA
  • Tom Tsai, Manager, Architecture &

Middleware, UC Berkeley

  • Mojgan Amini, Manager UXT, UC San Diego
  • Richard Trott, Director, UCSF
slide-3
SLIDE 3

What is this about?

  • The Mobile Trend
  • The UC Mobile Strategy
  • Device/Technology Agnostic
  • Mobile Web Framework as Enabler
  • Benefits (hard & soft)
  • Savings & ROI
  • Engagement: Staff, Researchers &

Students

  • What’s next:
  • App (Store) Sharing Environment
  • MWF as platform for Research
  • Mobile Phone as “Clicker”
slide-4
SLIDE 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 by 2015, 90% of the earth will have mobile coverage

slide-5
SLIDE 5
slide-6
SLIDE 6
  • UCLA Mobile launched in Sept 2010

– 22 Campus units involved – MWF as a platform for Innovation

  • Student engagement
  • Research Platform – mhealth, crowd sourcing etc
  • Made MWF Code Available Spring 2011
  • UC Mobile Collaboration Status: @ 8/10
  • 5 Campus mobile sites launched
  • 3 Mobile Campus mobile sites in development
  • 2 Campuses evaluating Framework

MWF Background & Status

slide-7
SLIDE 7

MWF Core Principles

  • Device Agnostic
  • Graceful Degradation
  • Unified mobile presence
  • Technology Platform Independent
  • Scalable, distributed architecture
  • Modern web standards (HTML 5 , CSS 3, etc…)
slide-8
SLIDE 8

Key Take Aways: MWF is:

  • Device Agnostic
  • Technology Agnostic

MWF (CSS, HTML5, JS) PHP Apps Java Apps Ruby Apps Python Apps Epic Apps .NET Apps

slide-9
SLIDE 9

The MWF is an example of a

Distributed Collaboration:

The MWF strategy relies on leveraging both students and faculty researchers

Com m unity Collaboration

Student built Mobile Apps Researchers ( mHealth etc.) Distributed Developers Campus Central IT MWF

MWF Board

slide-10
SLIDE 10

11-12 Investm ent & Savings

  • In House
  • Unit specific
  • Staff only

UC Saved: ~$1.5 Million

Investment Analysis

SYSTEM TOTAL

Type of Staff FTE

MWF Core development 1.63

Campus Mobile Management

1.50

2011‐12 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

slide-11
SLIDE 11

UC Berkeley and the MWF

404 Not Found http://m.berkeley.edu Launched: March 2011

slide-12
SLIDE 12

Im plem enting UC Berkeley’s Mobile Strategy

  • 1. Leverage
  • 2. Central campus mobile site
  • 3. Web App Mobile Use Cases
  • 4. Innovation
  • 5. Data Freedom

https://wikihub.berkeley.edu/display/itac/UC+Berkeley+Campus+Mobile+Strategy

slide-13
SLIDE 13

Power to the People!

slide-14
SLIDE 14

10 Apps in 3 days…

slide-15
SLIDE 15

UC San Diego em braces MWF

http://mwf.ucla.edu/edu11/mwrs

Summer 2009 iPhone app Winter 2010 New Mobile Strategy Evaluation & Selection Spring 2011 m.ucsd.edu Spring 2011 Self‐service tools, decorators, governance Spring 2011 ‐ present Proliferation of mobile apps!

Student Affairs Libraries

ulted 7 pus IT

  • ups

ated 7 g Mobile eworks

slide-16
SLIDE 16

UCSF: A Unifying Experience

  • MWF’s open and collaborative environment
slide-17
SLIDE 17

20 12 MWF Conference

  • Save the date: Sept. 5th – 7th @ UCLA
  • Open to the MWF Community + Public

– Educational and student rates – Special invitation to CSU’s and California CC’s

  • Session tracks for break out sessions

– MWF development and architecture – MWF as a platform for research and mHealth

slide-18
SLIDE 18

MWF Crowd Sourcing Contests

  • MWF Contest Process (first piloted by Berkeley)

– Host an MWF training Seminar – Submission eligibility: demonstrate value of MWF

  • Ease of use
  • Speed of development
  • Ease of deployment

– Defined eligibility, then use a Random drawing

  • MWF Conference contest = 8 apps in 2 wks
  • MWF Student contest = 6 apps – over the break
slide-19
SLIDE 19

MWF Conference - 8 Apps

slide-20
SLIDE 20

UCLA MWF Student Contest

  • Evening workshop was

held on 11/28

  • 28 Attendees
  • Students have break

to create app

  • iPad2 was the prize
  • 7 Entries, one was

disqualified

  • Prize was a random

drawing

slide-21
SLIDE 21

6 Student MWF Contest Apps

slide-22
SLIDE 22

MWF 1.3 Roadm ap

  • Forms UI and Javascript Libraries
  • Messages UI
  • Customizable Home Page / “Preferences"
  • Javascript Unit Tests
  • Javascript Decorators
  • Javascript Interactivity Libraries
  • Javascript‐based Handlers
  • Lean CSS Markup Entities
  • Basic Native Container
  • Form Decorator
slide-23
SLIDE 23

MWF 1.4 Roadm ap

  • Mobile App Sharing Environment
  • Enhanced Native Container
  • Installation Process
  • Unit Tests
  • Tablet and Desktop Support
  • Software as a Service Support
slide-24
SLIDE 24

Mobile Web Response System

  • In Beta this spring
  • Interactive Polling for classrooms

– Geo‐distributed classes – Online ‐ Synchronous Office Hours

  • Will work with all Internet enabled devices
  • Current market quiet large and burden on

students is significant

slide-25
SLIDE 25

MWF App (store) Environm ent

  • Phase I – Apps shared Local to an Institution
  • Phase II – Peer to Peer ‐ web service gets MWF

Apps from Community instances

  • Phase III – Federated Aggregator/Caching

– Federated Model – Apps Vetted by each Institution – Need Mobile Web App Standards for this to work – Multiple frameworks working together ?

  • Phase IV – CENIC/Internet2 or IMS GLC App

Registry

slide-26
SLIDE 26

Vision: MWF Com m unity Apps

Scandinavian flash cards Generic flashcard app Student Created Study tools Cool places to Study Great Restaurants nearby Garbage Watch Cool Research Opportunities Best TA Review Session German Flash Cards Calculus Study Tips Best International Experiences UCSD Housing Guide Wellness Activities Garbage Watch LOSE your freshman 15 Finding a Mentor How to get a summer job Generic flashcard app Student Created Study tools Local Internships San Francisco Hangouts Garbage Watch Cool Research Opportunities Best TA Review Session
slide-27
SLIDE 27

Educause ACTI – MWF Working Group

slide-28
SLIDE 28

How to Get Involved:

Main website: http://mwf.ucla.edu Get the Source: https://github.com/ucla/mwf/wiki/ Join the List serve: click here

(http://lists.ucla.edu/cgi‐bin/mailman/listinfo/mwf)

Attend the MWF Conference in Sept 5th – 7th

Questions?

slide-29
SLIDE 29

Appendix

slide-30
SLIDE 30

MWF App Environment vision – ph2

Current Affairs Lang conv Ethics

UCLA Mobile UCSD UC Berkeley UCI UCR UC Santa Barbara UCSF

slide-31
SLIDE 31

UCLA Mobile – Google Analytics

slide-32
SLIDE 32

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