a mobile web framework for the uc system
Post on 29-Jun-2015
740 Views
Preview:
DESCRIPTION
TRANSCRIPT
Mobile ComputingA mobile web framework for theUniversity of California System
Brett Pollak
13 years in the Web field
3.5 years working in higher ed.
2 years experience in mobile@campusweboffice
Audience participation
bit.ly/rm6Vsi
Where is the web today?
bit.ly/rm6Vsi
Where is the web tomorrow?
bit.ly/rm6Vsi
Where is the web in 6 months?
bit.ly/rm6Vsi
Mobile devices outnumber the US population
Mobile data traffic rose 111% from this year to last
Today… 33% of the U.S. Populationuse Smartphones
Smartphones
By October, 2012…
Over 50% of the U.S. population will use SmartphonesAsymco, July 2011
14% of prospective studentsaccessed admissions sitesfrom their mobile device
65% of 18-29 year olds have accessed the mobile internet
The next generation is growing up with it
How do we do keep up?
The Higher Ed landscape
Students Staff
Faculty
AlumniVisitors
Parents
Students with the latest gadgets
Staff and faculty with older devices
Where is ouriPhone app?
Decentralized IT groups that own the data
Background: UCSD’s iPhone App
• June ‘09 UCSD first public university to provide iPhone app
• Provided web services and data feeds to TerriblyClever.
• Blackberry and generic mobile site launched soon thereafter
• In early 2010, TerriblyClever was bought out by Blackboard
Our investigation begins in thespring of 2010…
UCLA MWF was in the works and provided a light footprint
The mobile web was our target solution
Most higher ed packages like MIT and Kurogu needed to be hosted centrally
Front end frameworks like Sencha were very JS heavy and were more than what we were looking for.
JQuery mobile looked promising but was in alpha
UCSD’s Framework Selection
• Involved Campus IT Groups
ACT
Student AffairsLibraries
1
UCSD’s Framework Selection
• Defined Selection Criteria
• Sustainable over 1-2 years• Technology agnostic• Open source or industry standards• Support various mobile devices• Little training for development• Easy to replace in the future
2
UCSD’s Framework Selection
• Reviewed Mobile Frameworks3
UCSD’s Framework Selection
• ease of use and learning curve• framework features, • documentation, • cross-platform support, • maturity, • extensibility, and • potential integration with our campus CMS.
4Evaluation criteria & Recommendation
What’s our strategy?
The UC Mobile Strategy
Device Agnostic Technology Agnostic
MWF (CSS, HTML5, JS)
PHP Apps
Java Apps
Ruby Apps
Python Apps
Epic Apps
.NET Apps
MWF PrinciplesDevice Agnostic Works on any web-capable device.
Federated Architecture Hosted centrally, but used in a distributed manner.
Unified UI Presence One outwards presence even in a distributed environment.
Language & Environment Independent Compatible with any development language
Modern Web Standards Complies with modern web standards.
What’s the secret sauce?
1. Device detection
2. Dynamic JavaScript & CSS
3. Image compressor
It aint that much…
How UCSD Developers use it
<head>
<link href="//m.ucsd.edu/assets/css.php" media="all" rel="stylesheet"type="text/css" />
<script type="text/javascript" src="//m.ucsd.edu/assets/js.php"></script>
</head>
Create a mobile view of their app and call these assets…
How UCSD Developers use it
But where is ouriPhone app?
Powered by the UC Mobile Web Framework
Can I use it? Sure you can!
Now let’s look at some statistics...
The UCSD Mobile home page gets about 4,000 pageviews per day.
That’s ~17% of the what the campus home page gets
It’s been increasing at a rate of ~2% per month so far this year.
iPhone; 47%
Android; 31%
iPod Touch;
9%iPad; 6%
Windows; 2% Blackberry; 1%
Device Breakdown
My TritonLink; 34%
Welcome Week; 10%
Tours; 4%Courses; 14%
Book-store; 1%
Maps; 15%
Dining; 8%
Directory; 5%
Videos; 1% Podcasts; 8%
Top applications: 1 month
What about our websites?
Does it work for that too?
One Web means making, as far as is reasonable,
the same information and services available to users irrespective of the device
they are using.
- W3C Mobile Best Practice Recommendation
One Web means making, as far as is reasonable,
the same information and services available to users irrespective of the device
they are using.
- W3C Web Best Practice Recommendation
One semantic markupfor all devices
Progressive Enhancement
One Web Axiom:Content provider does
nothing
Graceful Degradation
1. Start with full feature version of content
2. Write CSS and JS so less-capable browsers can display core content
Full Desktop Site+
CSS & JS=
Responsive Site
Thank you & Enjoy the video
m.ucsd.edu
top related