Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

A Mobile Web Framework for the UC System

976 views

Published on

Describes UC San Diego's decision making process to use the Mobile Web framework. Outlines how all University of California schools are also leveraging the framework and contributing to it's development.

Published in: Technology, Education
  • Be the first to comment

  • Be the first to like this

A Mobile Web Framework for the UC System

  1. 1. Mobile ComputingA mobile web framework for theUniversity of California System
  2. 2. 13 years in the Web field 3.5 years working in higher ed.Brett Pollak 2 years experience in mobile@campusweboffice
  3. 3. Audience participation bit.ly/rm6Vsi
  4. 4. Where is the web today? bit.ly/rm6Vsi
  5. 5. Where is the web tomorrow? bit.ly/rm6Vsi
  6. 6. Where is the web in 6 months? bit.ly/rm6Vsi
  7. 7. Mobile devices outnumber the US population
  8. 8. Mobile data traffic rose 111% from this year to last
  9. 9. Smartphones Today… 33% of the U.S. Population use SmartphonesBy October, 2012…Asymco, July 2011 Over 50% of the U.S. population will use Smartphones
  10. 10. 14% of prospective studentsaccessed admissions sitesfrom their mobile device
  11. 11. 65% of 18-29 year olds haveaccessed the mobile internet
  12. 12. The next generation is growing up with it
  13. 13. How do we do keep up?
  14. 14. The Higher Ed landscape
  15. 15. Parents FacultyStudents StaffVisitors Alumni
  16. 16. Students with the latest gadgets
  17. 17. Staff and faculty with older devices
  18. 18. Where is ouriPhone app?
  19. 19. Decentralized IT groups that own the data
  20. 20. 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
  21. 21. Our investigation begins in thespring of 2010…The mobile web was our target solutionMost higher ed packages like MIT and Kurogu needed to be hosted centrallyFront end frameworks like Sencha were very JS heavy and were more thanwhat we were looking for.JQuery mobile looked promising but was in alphaUCLA MWF was in the works and provided a light footprint
  22. 22. UCSD’s Framework Selection1 Involved Campus IT Groups • Libraries Student Affairs
  23. 23. UCSD’s Framework Selection2 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
  24. 24. UCSD’s Framework Selection •3 Reviewed Mobile Frameworks
  25. 25. UCSD’s Framework Selection4 Evaluation criteria & Recommendation • ease of use and learning curve • framework features, • documentation, • cross-platform support, • maturity, • extensibility, and • potential integration with our campus CMS.
  26. 26. What’s our strategy?
  27. 27. The UC Mobile StrategyDevice Agnostic Technology Agnostic PHP Apps .NET Apps Java Apps MWF (CSS, HTML5, JS) Epic Ruby Apps Apps Python Apps
  28. 28. MWF PrinciplesDevice AgnosticWorks on any web-capable device.Federated ArchitectureHosted centrally, but used in a distributed manner.Unified UI PresenceOne outwards presence even in a distributed environment.Language & Environment IndependentCompatible with any development languageModern Web StandardsComplies with modern web standards.
  29. 29. What’s the secret sauce?It aint that much… 1. Device detection 2. Dynamic JavaScript & CSS 3. Image compressor
  30. 30. How UCSD Developers use itCreate a mobile view of their app and callthese assets…<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>
  31. 31. How UCSD Developers use it
  32. 32. But where is ouriPhone app?
  33. 33. Powered by the UC Mobile Web Framework
  34. 34. Can I use it? Sure you can!
  35. 35. Now let’s look at some statistics...
  36. 36. 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.
  37. 37. Windows, 2% Blackberry, 1% iPad, 6% iPod Touch, 9% iPhone, 47%Android, 31% Device Breakdown
  38. 38. Videos, 1% Podcasts, 8% Shuttles, 0% Directory, 5% My Dining, 8% TritonLink, 34% Maps, 15% Welcome Week, 10% Courses, 14%Bookstore, 1% Tours, 4% Top applications: 1 month
  39. 39. What about our websites?Does it work for that too?
  40. 40. One Web means making, asfar as is reasonable, the same information and servicesavailable to users irrespective of the device they are using.- W3C Mobile Best Practice Recommendation
  41. 41. One Web means making, asfar as is reasonable, the same information and servicesavailable to users irrespective of the device they are using.- W3C Web Best Practice Recommendation
  42. 42. One semantic markup for all devices
  43. 43. Progressive Enhancement
  44. 44. One Web Axiom:Content provider does nothing
  45. 45. GracefulDegradation
  46. 46. 1. Start with full feature version of content
  47. 47. 2. Write CSS and JS so less- capable browsers can display core content
  48. 48. Full Desktop Site + CSS & JS = Responsive Site
  49. 49. Poll Resultsbit.ly/rm6Vsi
  50. 50. Thank you &Enjoy the video m.ucsd.edu

×