Mobile Applications and Devices STEMTech 2011 CIO Summit October 2, 2011

Some Mobile Statistics 5 billion people will be directly touched by mobile devices and networks by Source: Yankee Group Research, 2011 Earths Population Today: almost 7 billion people

Mobile Device Statistics Mobile Computing is the Largest Computing Shift Ever Source: Yankee Group Research, 2011

Mobile Device Statistics

Smart Phone Market Statistics

Smart Phone Statistics

Mobile Web Review Pros Cost and ease of development Compatibility with the most devices Control of the development and delivery process Best match with current web developer skill sets, allowing for high levels of reuse in terms of training and code base. Cons Mobile Web applications cannot use the local device hardware, such as local storage, cameras, accelerometers, and other hardware specific features. Mobile Web is not as Cool Applications are not typically as easy to use, or as polished as device specific applications. Cannot be run in an offline capacity Often perform more slowly due to reliance on the network connection of the device

Mobile Web Uses Suggested Uses: Informational tools Service tools Commerce tools Non-Recommended Uses: Games Simulations Offline Uses Anything that needs to execute code locally or access the hardware directly Strategic Considerations: Mobile Web Applications are the easiest way to enter the mobile ecosystem and leverage currently existing technologies, skill sets and reuse existing application development efforts This methodology would allow the easiest path to deploy numerous services and tools to the largest number of end users in the shortest period of time

Device Specific App Review Pros Direct monetization of the application through an app store Built in national level marketing such as Android or iPhone recognition or Halo effect Device Specific applications typically have the best user interfaces and usability Access to the local features of the devices such as storage, camera, and other device specific hardware Cons Cost of development is higher than Mobile Web Buggy software is harder to fix as it relies on the user to download updates There can be multiple versions of device OSs in production further increasing the number of delivery platforms that need to be supported Reliance on externally controlled app stores for delivery to devices. App Store may include a one-time or annual fee and may have approval process before apps may be published Applications can get lost in the Application stores with many thousands of other offerings

Device Specific App Uses Suggested Uses: Games Simulations Anything that relies on using the device specific hardware, such as the camera or GPS based services Anything that must run offline Media driven commerce (music, video, e-readers …etc) Non-Recommended Uses: General Information Simple Services Traditional e-Commerce (Non media) Strategic Considerations: The device specific applications do have more features and potentially better interfaces, but the value of the additional cost should be considered. Mobile ecosystems (Android, iOS, Blackberry) should be evaluated to find the right fit for your business goals. Market Penetration, Monetization, Users Needs, Market Appeal …etc. Tools like Appcelerator might ease the burden of developing for multiple platforms.

Sinclairs Mobile Offerings For Students: People Directory(4) College News & Events(5) General Campus Info(6) Sinclair FAQs Schedule Planner(2) Program Viewer(3) SCC Whiteboard Current Schedule*(1) Current Booklist* My Advising Plan* Magic Helpdesk* For Employees: Bookstore/Student Assistance App* * Requires Authentication (#) Student Indicated Importance on Survey

Mobile Development 5 Options: 1.Native Application Development 2.Mobile Application Platform Middleware 3.Mobile Pre-built Applications & Systems 4.Outsourced Mobile Application Development 5.Mobile Web

Native Application Development Pros: Complete control over application Designed exactly to requirements Cons: Expensive Multiple devices and OSs to support Slower to market Infrequent releases Overwhelming maintenance

Mobile Application Platform Middleware Pros: Rapid application development Develop once (devices supported via middleware) Cons: Some developer learning curve Costs Backend system integrations may be difficult Examples: Pyxis, Appcelerator

Mobile Pre-built Applications and Systems Pros: Less expensive Applications and integrations already built Multiple devices supported via middleware Cons: Less flexibility Customizations may be more difficult Examples: Blackboard Mobile, SunGard Mobile Connection

Outsourced Mobile Application Development Pros: Build to exact specifications Little to no in-house development needed Cons: Expensive Vendor dependency for changes, improvements Little control post-release Examples: MobileZapp

Mobile Web

Pros: Device independent (uses browser) Develop once Can use some native device functions HTML 5 Cons: Longer initial development time More limited native device integrations (but improving) Examples: Sinclair Mobile

Mobile Development Process Valencia Step 1 Extensive review of all options (5) and tools/vendors – Including demos and some pilot testing

Options, Tools and Vendor Review

Mobile Development Process Valencia Step 2 (ongoing) Review of research re: content/use Review of other college/university apps Student, Faculty & Staff input

Mobile Development Process Valencia Step 3 Initial Tool Decision (and internal pilot) SunGard Mobile Connection Software Cost (free) Technology (uses same technology that Banner next release will be using) Built in integration with Banner ERP system Pre-built Applications User support community

Mobile Development Process Valencia Step 4 (Fall 2011) Review/feedback with MAG (Mobile Advisory Group) Now considering mobile web option in parallel Step 5 (Fall 2011/Spring 2012) Initial silent rollout – Android, Iphone/Ipod/Ipad Step 6 (Fall 2011/Spring 2012) Feedback and review Step 7 (Spring/Summer 2012) Marketing Announcement and Final Rollout (including Blackberry)

Valencias Mobile Application (so far)

Questions? Contact Information: Ken Moore Senior Vice President & CIO Sinclair Community College Bill White Chief Information Officer Valencia College

Resources Sæterås, John. "Mobile Web vs. Native Apps. Revisited." mobiletech 9 April 2010: n. pag. Web. 12 Jul Covert, Adrian. "What Makes The Five Smartphone Platforms Different." Gizmodo 18 March 2009: n. pag. Web. 12 Jul King, Michael. "Magic Quadrant for Mobile Consumer Application Platforms." Gartner G (2009): n. pag. Web. 2 Jul Jones, Nick. "What the CIO Needs to Know About Mobile-App Stores and Ecosystems." Gartner G (2009): n. pag. Web. 2 Jul Jones, Nick. "Cross-Platform Mobile Application Development Tools: Interest and Capability Expected to Grow." Gartner G (2010): n. pag. Web. 2 Jul Basso, Monica. "Social Trends Are Influencing the Adoption of Mobile and Web Technology." Gartner G (2009): n. pag. Web. 2 Jul Redman, Philip. "Hype Cycle for Wireless Devices, Software and Services, 2009." Gartner G (2009): n. pag. Web. 2 Jul Clark, William. "Critical Capabilities for Mobile Enterprise Application Platforms." Gartner G (2009): n. pag. Web. 2 Jul King, Michael. "Mobile Applications for Your Customers: Remain Calm and Know the Risks." Gartner G (2009): n. pag. Web. 2 Jul Jones, Nick. "The Case for and Against Device-Specific Mobile Applications." Gartner G (2008): n. pag. Web. 2 Jul Shen, Sandy. "Hype Cycle for Consumer Mobile Applications, 2009." Gartner G (2009): n. pag. Web. 2 Jul Jones, Nick. "Ten Mobile Technologies to Watch in 2010 and 2011." Gartner G (2010): n. pag. Web. 2 Jul MacManus, Richard. "Mobile App or Browser-Based Site? Report Says The Browser Will Win on Mobile." Read Write Web 2 Feb 2010: n. pag. Web. 1 Jul Cameron, Chris. "Will Mobile Web Apps Eventually Replace Native Apps?." Read Write Web 5 Jul 2010: n. pag. Web. 2 Jul Nakao, Kevin. "Why You May Not Need a Mobile App." Mashable Jun 2010: n. pag. Web. 2 Jul