Successfully reported this slideshow.
Your SlideShare is downloading. ×

Going Mobile - JBoye - 2011

Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Loading in …3
×

Check these out next

1 of 41 Ad
Advertisement

More Related Content

Slideshows for you (20)

Advertisement

Similar to Going Mobile - JBoye - 2011 (20)

Going Mobile - JBoye - 2011

  1. 1. Going Mobile!How UVU Launched Their Mobile Initiative<br />Nathan Gerber <br />Director, Web Development Services<br />Utah Valley University<br />
  2. 2. Introductions<br />Nathan Gerber @nathangerber<br />16 years Web IA experience<br />Director, Web Development Services<br />Noel-Levitz Associate Consultant, Web Strategy Services Team<br />Utah Valley University<br />Largest state university in Utah (almost…one more student)<br />32,000+ students<br />28,000+ public pages<br />
  3. 3. What We Will Be Covering<br />Why we did it Research shows…<br />What we did We decided to…<br />How we did it “Baby steps, Bob, baby steps”<br />Tools we used CMS, sniffer, GA, lots of devices <br />Next steps Where do we go from here…<br />
  4. 4. You Are Here<br />Can you find my son in this picture?<br />
  5. 5. ?<br />So, what’s the big deal with mobile<br />
  6. 6. Morgan Stanley – Mobile Users by 2015<br />
  7. 7. Smartphones Outsell PCs<br />
  8. 8. Mobile Phone Use, 2009 – 2011<br />80% of adults (18-29yrs) own mobile phones in 2010… no change from 2009<br />2009 2010 2011<br />Take a photo… 66 to 76 to 93%<br />Send & receive text messages… 65 to 72 to 95%<br />Send & receive email… 25 to 34 to 52%<br />Access the Internet… 25 to 38 to 65%<br />From Bob Johnson Consulting, LLC<br />
  9. 9. E-Expectations: Noel-Levitz<br />24% may drop college after poor web experience<br />23% searched college websites via smartphones<br />Most desired web content:<br />Information on academics… 54%<br /> List of academic programs… 28%<br />Cost related information… 30%<br />Do you have my program? How Much will it cost? Will I fit in?<br />
  10. 10. Google Analytics for UVUFor President’s Report<br /> 1551% <br />IN <br />8 MONTHS <br />(from 10,534 to 173,953 visits)<br />*Still only 2.5% of overall traffic<br />
  11. 11. Build A New Mobile Site?<br />“Mobilize, don’t miniaturize”… anon.<br />“… the mobile context is so different from the desktop one it deserves direct consideration vs. just mangling down a full-size site.” <br /> - Drew Stevenson, University of Minnesota, 2010<br />Bob Johnson Consulting, LLC<br />
  12. 12. This Is How We Felt<br />Web team resources<br />Mobile web project<br />
  13. 13. What We Did…You May Consider<br />
  14. 14. The Big Guy Has To Agree<br />Their response:<br /> “Ok, but don’t spend too many resources and don’t ask for any more. After all, it is only 2% of our overall traffic.”<br />We approached it as an information item, not for approval<br />(Learning to deal with HIPPOS)<br />
  15. 15. Initial Decisions<br />“The user IS mobile, not just holding one.”<br /><ul><li>Justin Gatewood, Victor Valley Community College</li></ul>“Mobilize, don’t miniaturize”<br />Anonymous<br />“It is not about making our site work on a mobile device, it is about what our users need when they’re mobile”<br /><ul><li>Mobile Web Team, Utah Valley University</li></li></ul><li>Now For The Tech Stuff<br />(…well, sort of)<br />
  16. 16. Native App or Mobile Web?<br />
  17. 17. Native Apps<br />Pros<br />Controlled user experience<br />Use hardware features<br />Off-line usage<br />Uses app code on device<br />Cons<br />Develop for each platform<br />Different experience based on device<br />Cost/time to develop/deploy<br />Testing not as easy<br />Upgrades/version requires new download<br />
  18. 18. Mobile Web<br />Pros<br />Cost/time to develop is less<br />Upgrades quicker<br />Accessible to all/no installation<br />More discoverable<br />Cons<br />Customer satisfaction<br />User experience/performance depends on design<br />More difficult to access native device capabilities<br />No offline mode<br />
  19. 19. App or Site – Future?<br />That is so last year!<br />Is there an app for that?<br />What about a framework?<br />
  20. 20. Mobile Web – Other Questions<br />http://www.dmolsen.com/mobile-in-higher-ed/<br />
  21. 21. Second Decision<br />What devices do we build for and support?<br />iPhone, Android, iPad, iPod <br />Why? Because our users have them (and so do our Administrators)<br />
  22. 22. Mobile Device Usage – World <br />
  23. 23. Mobile Device Usage – US <br />
  24. 24. Third Decision<br />How big do we make our first attempt?<br />Start with info for students<br />Choose top content<br />Don’t try to publishing everything*<br />Be willing to make mistakes*<br />Be flexible*<br />Design and redesign*<br />Add apps where needed<br />*from TAMUmobile – HighEd Web 2010<br />Baby steps, Bob, baby steps<br />
  25. 25. What Is The Top Content?<br />http://www.dmolsen.com/mobile-in-higher-ed/<br />
  26. 26. UVUmobile<br />
  27. 27. UVUmobile<br />
  28. 28. UVUmobile Features<br />Width changes with device orientation<br />Page weight is light <br />Sniffs for mobile devices<br />Content coming from OmniUpdate (CMS)<br />Other system feeds presented by OU<br />Content is driven by user need (Content is King!)<br />
  29. 29.
  30. 30. Types Of Content – One CMS <br />
  31. 31. Fourth Decision<br />What comes after the first rollout?<br />User driven – feedback system<br />Focus on key audiences – Current/Future Students<br />Functions and features <br />What do our users need to do when they are mobile?<br />
  32. 32. University Website<br />Mobile Web<br />Source: http://xkcd.com<br />
  33. 33. Three Phases of UVUmobile(at least)<br />Start with browser site<br />Static content, links to other apps <br />Expand features<br />User Services<br />Add apps where needed<br />Current and future students<br />The great merge<br />Public site and mobile site come closer together<br /> User needs<br />
  34. 34. Tools Used<br />OmniUpdate<br />Browser sniffer<br />Analytics<br />HTML 5<br />Lots of devices<br />Some Emulators <br />Other High Ed <br />mobile sites<br />http://mobiforge.com/emulators/page/mobile-emulators <br />
  35. 35. Next Steps for UVUmobile<br />Creating a launch panel for other UVU apps<br />Create app functionality where needed<br />Integration of OmniUpdate and other systems data sets<br />Continual migration of public site and mobile to together<br />In concepts, principle, driving factors<br />
  36. 36. Other HigherEd Mobile Sites<br />http://www.dmolsen.com/mobile-in-higher-ed/?page_id=43<br />http://www.edustyle.net/gallery_mobile.php<br />When evaluating, look at:<br />Design<br />Usability<br />Content<br />Services<br />Focus<br />Keep mobile user in mind<br />
  37. 37. Summary<br />Mobile is changing the way we view/consume content and services<br />Research, decide, modify as you go<br />Choose what works for your institution<br />Keep Admin informed<br />CMS is a key tool – XML <br />Get on board! Higher Ed is already behind<br />
  38. 38. “It is not about making our site work on a mobile device, it is about what our users need when they’re mobile”<br />- Mobile Web Team, Utah Valley University<br />
  39. 39. Questions?<br />Nathan Gerber<br />Nathan.Gerber@uvu.edu<br />@nathangerber<br />
  40. 40. THANK YOU<br />

Editor's Notes

  • Picture of some tools

×