Going Mobile with a Web-Based Strategy

Պահպանված է:
Մատենագիտական մանրամասներ
Հրատարակված է:EDUCAUSE Review (Online) (Mar 29, 2011)
Հիմնական հեղինակ: Rocchio, Rose
Հրապարակվել է:
EDUCAUSE
Խորագրեր:
Առցանց հասանելիություն:Citation/Abstract
Full Text
Ցուցիչներ: Ավելացրեք ցուցիչ
Չկան պիտակներ, Եղեք առաջինը, ով նշում է այս գրառումը!

MARC

LEADER 00000nab a2200000uu 4500
001 3224543176
003 UK-CbPIL
035 |a 3224543176 
045 0 |b d20110329 
100 1 |a Rocchio, Rose 
245 1 |a Going Mobile with a Web-Based Strategy 
260 |b EDUCAUSE  |c Mar 29, 2011 
513 |a Journal Article 
520 3 |a Key Takeaways * 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. 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. [...]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. 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. 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. 
653 |a Source code 
653 |a Strategy 
653 |a Smartphones 
653 |a Servers 
653 |a Applications programs 
653 |a Libraries 
653 |a Popularity 
653 |a HyperText Markup Language 
653 |a JavaScript 
653 |a Image 
653 |a Advocacy 
653 |a Colleges & universities 
653 |a Mobile content 
653 |a Computer Oriented Programs 
653 |a Governance 
653 |a Staff Meetings 
653 |a Open Source Technology 
653 |a Language Maintenance 
653 |a Architecture 
653 |a Campuses 
653 |a Environment 
653 |a Influence of Technology 
773 0 |t EDUCAUSE Review (Online)  |g (Mar 29, 2011) 
786 0 |d ProQuest  |t ABI/INFORM Global 
856 4 1 |3 Citation/Abstract  |u https://www.proquest.com/docview/3224543176/abstract/embedded/ZKJTFFSVAI7CB62C?source=fedsrch 
856 4 0 |3 Full Text  |u https://www.proquest.com/docview/3224543176/fulltext/embedded/ZKJTFFSVAI7CB62C?source=fedsrch