Transcript of "Going mobile with a web based strategy (educause quarterly) | educause"
Going Mobile with a Web-Based Strategy (EDUCAUSE Quarte... http://www.educause.edu/EDUCAUSE+Quarterly/EDUCAUS... Location: Home » Resources » EDUCAUSE Quarterly (EQ) » EQ Archives » EQ Volume 34 (2011) » Volume 34, Number 1, 2011 » Going Mobile with a Web-Based Strategy Going Mobile with a Web-Based Strategy By Rosemary A. Rocchio If your campus needs to go mobile immediately, how should you assess, choose, and adopt the best mobile strategic approach for your campus community? UCLA went through this process and subsequently chose a mobile web strategy around an in-house–created Mobile Web Framework to deliver a device-agnostic environment with graceful degradation and a unified mobile presence. The UCLA MWF accommodates a variety of technology platforms and campus system architectures and has standardized around the modern web standards HTML5 and CSS3. Future plans include release of the MWF source code in a shared environment to create a broad academic community for development and collaboration. The CIO wants to know your mobile strategy — as of yesterday. So you need to go mobile now… but how? This article will walk you through UCLAs assessment of the mobile strategic approaches available in the fall of 2009 and the universitys subsequent decision to focus on the creation of a mobile web strategy around a new homegrown Mobile Web Framework, UCLA MWF. This journey will detail the benefits of UCLAs selected strategy: Delivery of a device-agnostic environment with graceful degradation Providing users with a unified mobile presence Accommodating any variety of technology platforms and campus system architectures Standardization around the modern web standards HTML5 and CSS3 Further, I will provide a glimpse of where UCLA intends to take the development of the UCLA MWF, along with an update on current adoption on campus, across the University of California System, and beyond. Formation of a Mobile Strategy Conceptualizing a mobile strategy typically begins with consideration of a native (device-specific platform) strategy. After all, Apple mobile devices are incredibly popular, and the company has sold 10 billion apps for their mobile platform. Other benefits of native applications include the interactivity, immersive user experience, geo awareness, and high-definition graphics. The significant problem with going native, however, is the proliferation of mobile devices. Consider the rising popularity of Android devices, executive preference for Blackberry smartphones, and the potential popularity of Windows phones now that Nokia plans to offer the Windows OS. Nokia is still the second most popular phone brand worldwide, and the Windows Mobile OS may just give it the "refresh" boost it seeks. Looking at the worldwide smartphone market share as of January 2011, with Android having surpassed both Nokia and Apple, it becomes obvious that the proverbial mobile horses have already left the barn. Therefore, requirements of a native strategy dictate either the ability to standardize on a single mobile platform or the resources to code for the top three to four native devices. An alternative to a native mobile strategy is to use a mobile web framework. A framework is a set of modules that are coded and maintained in one place, but invoked from a broad spectrum of web pages designed for a mobile device. Frameworks are accessible via a defined application programming interface (API) and have the ability to control certain aspects of code programmed with it. In the case of a mobile web framework, the framework detects the type of device accessing the code, and then delivers a set of code that can best be displayed on the particular device. In the fall of 2009, UCLA weighed the pros and cons of a native strategy versus a mobile web framework strategy and decided to focus on the latter for a variety of reasons: The first and most positive reason to go with a mobile web framework strategy is that by doing so, UCLA would maintain a device-agnostic mobile environment, which results in the broadest distribution possible to any mobile device. Security is a positive aspect of a mobile web approach because all mobile web applications are browser based, and users have some awareness of encryption ("https"). Another important positive of mobile web applications is that many applications can be collected in a mobile web portal — a critical factor for UCLA given the broadly distributed campus data owners and services. The most important factor of a mobile strategy, however, is that a mobile web framework — shared libraries of CSS (cascading style sheets) code that handle the device presentation layer — significantly reduces the maintenance of distributing mobile content. The Decision to Build a Mobile Web Framework Having decided on a mobile web strategy, UCLA considered using the framework created by the MIT Mobile Web Open Source Project code. While it had many positives, and their general framework value proposition was a strong one, the MIT Mobile Web Open Source Project had a number of significant drawbacks for a university like UCLA: It consists primarily of server-side technology (all the data has to coexist on the same server). It is platform specific, meaning that because it was written for PHP, it will not work with other code languages (Java, .NET, and so forth). It is not modular enough, which means that integration points are deep in the source. After a certain amount of evaluation of these issues and consideration of UCLAs distributed IT organizations and their respective investments in a broad variety of technology platforms, OIT began building the UCLA MWF with a flexible architecture based on several principles. Principles of the UCLA MWF1 of 5 4/21/11 12:41 PM
Going Mobile with a Web-Based Strategy (EDUCAUSE Quarte... http://www.educause.edu/EDUCAUSE+Quarterly/EDUCAUS... collection. Beyond UCLA UCLA has been expanding its collaboration on the UCLA MWF within the University of California System since announcing it via a presentation at a UC-wide conference in July 2010. The name of the framework may become the "UC Mobile Web Framework" in the near term as a result. UC Berkeley has adopted the use of the UC/UCLA MWF, for example. Bill Allison, chair of the UC Berkeley Campus IT Architecture Committee, explains Berkeleys mobile strategy: Bill Allison Additionally, UC Riverside developed a mobile web pilot using the UC/UCLA MWF that they launched in the winter quarter of 2011, testing their application suite with approximately 200 students. Finally, UC San Diego completed a full mobile web framework evaluation of eight different frameworks, selecting two in which to build pilots. They found UCLAs MWF best met their needs for a campus-wide solution. Mojgan Amini, User Experience and Technologies at UCSD, explains why the campus chose UCLAs MWF: Mojgan Amini Licensing Plans UCLA intends to release the UCLA Mobile Web Framework code as a "source available" project where anyone is welcome to use the core trunk code and, after passing a code review process, contribute new code as they build new features. The source code is managed in a shared environment and already has developers from three UCs contributing time and effort to the project. The future goal of the UCLA MWF is to create a broad academic community of development and collaboration around the UCLA MWF. Get Involved with UCLA MWF4 of 5 4/21/11 12:41 PM