1 COMMONWEALTH OF PENNSYLVANIA DEPARTMENT OF PUBLIC WELFARE INFORMATION TECHNOLOGY STANDARD Name Of Standard: Mobile Website Development Domain: Application Number: Category: STD-EASS010 Date Issued: Date Revised: 08/19/13 Issued By Direction Of: Shirley Monroe, Acting Dir of Div of Tech Engineering Abstract: The purpose of this standard is to define the guidelines to be used to drive future mobile website development. These guidelines should be applied based on the needs of the customer and have been defined to make the best use of DPW s existing development technology, processes, and tools. To better serve the citizenry and workforce, the Department of Public Welfare (DPW) has embarked on a strategic initiative to define and operationalize their mobile website architecture. The Department s goal is to provide an opportunity for DPW to build a standard architecture and develop a set of guidelines that define the foundation for mobile based solutions to support potential citizen facing mobile websites. The following areas are to be addressed: Design and UX/UI (user experience/user interface) Architecture o Critical to understanding how to create user friendly, interactive and attractive mobile websites. Application Development Architecture o The core technology for the creation of mobile websites. Mobile Device Architecture o The mobile device architecture for deploying mobile websites. Security Architecture o Critical controls and data security considerations. Testing, Performance, and Usage Metrics o Important testing and performance management considerations during and after application development.
2 General: The goal of the process is to create a set of guidelines relevant in the development and deployment of mobile websites. The purpose of this document is to state standards in terms that can be applied as technology changes and they will require review as technology and requirements change. The key objectives are to create development guidelines to enable and support the creation of citizen-facing DPW mobile websites. The resulting guidelines herein are intended to describe the items that are not part of the established standards defined in the ALM Baseline (which should be followed where appropriate). The guidelines focus on the mobile-specific topics and include mobile web environments, architectures, security, and standards. Standard: DESIGN AND UX/UI ARCHITECTURE This section of the guidelines describes the activities, tools and processes required to create highly usable, interactive and attractive mobile websites. This section provides standards for the following: Mockups, Wireframes, and Prototyping Tools - Tools to facilitate the creation of visualizations of a mobile website s screens Creative Design Branding, color scheme, and iconography guidelines Accessibility Creating mobile websites that are accessible for users with disabilities Mockups, Wireframes, and Prototyping Tools Creative Design Accessibility Guideline Rationale Tools Design tools appropriate for the project should be selected. Adobe Creative Suite is an approved tool, but other tools may be used if approved by stakeholders. Mobile websites should follow best practices for mobile web design such as being touch friendly and highly visible on small screens. The standard DPW style guide for websites should be used where applicable when creating styles for mobile websites. The current accessibility standards issued by the state should be applied as much as possible to mobile websites. Adobe Creative Suite licenses are already owned by DPW. Although other tools may be helpful they will require the purchase of new licenses. Screen size and input methods on mobile devices differ greatly from desktop websites and a different design should be created to increase usability on mobile devices. The appearance of mobile websites should be consistent with DPW s desktop websites and branding. Accessibility standards for websites have been created by the Office of Administration and mobile websites are not exempt. The wire framing tool Balsamiq, the prototyping tool Axure, and the graphics design tools provided by in Adobe s Creative Suite. Best practices for mobile web design are defined by the W3C in the Mobile Web Best Practices 1.0 document (available on their website). The following documents contain style and branding information for desktop websites that may also apply to mobile websites: Commonwealth of Pennsylvania Style Guide ITB-APP005 STD-APP005A For Commonwealth of PA s Accessibility Policy see ITB- ACC001. For the W3C s mobile web accessibility guidelines see the website of the W3C Web Accessibility Initiative.
3 ARCHITECTURE OVERVIEW The following section provides a high level view of the components that comprise the mobile web architecture. Figure 1 demonstrates the relationship between the current web architecture and the architecture to support mobile websites. At high level the DPW Mobile Web Archjtiecture can be described in the context of the chosen subject matter areas including Design UX/UI, Application Architecture, Device Support, Security and Testing, Performance and Usage Metrics. Figure 1
7 MOBILE DEVICE ARCHITECTURE This section describes the systems and devices required for end to end solutions. Devices selected for support are based on the current trends in the market. As shown in Figure 3 below, a survey conducted in December 2011 indicates a majority of the smartphone market is divided between ios and Android devices. The tablet market is dominated by ios/the ipad. Android tablets hold less than 10 percent of the market share. Figure 3: OS Share of Device Traffic The Android tablet market share is rapidly changing. As shown in the Figure 4, the new Amazon Kindle Fire is rapidly taking over market share. The data in Figures 5 and 6 suggests testing on the 9.7-inch Apple ipad, the 7-inch Kindle Fire, and the 10.1-inch Samsung Galaxy Tab 2. Testing on these tablets would cover a range of screen sizes, the ios operating system, the new Android 4 (Ice Cream Sandwich) operating system, and the heavily modified version of Android 2.3 (Gingerbread) used by the Kindle Fire.
8 Figure 4: Android Tablet Market Share Figure 5 shows a breakdown of mobile traffic that visited DPW s websites during April Since the browsers on different versions of Android have different levels of HTML5 support, this graph divides the visits from Android devices according to operating system market share data provided by Google for the time period shown. Because of the low number of devices using versions other than ios 5, this breakdown was not necessary for ios. Figure 7 reinforces the need for testing on an iphone, ipad, and a device running version 2.3 of the Android operating system. The Samsung Galaxy SII is a popular phone that runs Android 2.3 making it a good candidate for testing. This phone is also scheduled to receive an update to Android 4.0 (the latest version) in the near future. Figure 5: Mobile Traffic to DPW Sites, April 2012
9 This section provides guidelines for the following: Device Support Which devices should be supported by mobile websites Device Support Guideline Rationale Tools Mobile websites should be fully functional on a set of the top devices found to be accessing DPWs mobile websites. DPW recognizes that mobile device landscape changes rapidly and market leading devices and operating systems can be obsolete in less than a year. The top device categories accessing DPW s public websites are a moving target that closely conforms to the devices citizens are actually using, making it a suitable guide for determining device support. The following devices are market leaders across several categories and encapsulate a range of operating systems and screens sizes. Apple iphone (ios) Apple ipad (ios) Samsung Galaxy S (Android) Samsung Galaxy Tab (Android) Amazon Kindle Fire (Android) Testing on these devices will provide coverage for the most common devices on the market at the time of this document s creation. These devices need to be re-evaluated periodically to keep pace with current market trends. SECURITY ARCHITECTURE The security control guidelines have been defined to make the best use of DPW s existing security technology, processes and tools in the ALM Baseline. A copy of the Mobile Application Security Standards can be found here: A copy of the Mobile Device Standard can be found here TESTING, PERFORMANCE, AND USAGE METRICS This section describes the tools and methods used to test mobile websites during and after development; validate the performance of mobile applications; and the metrics and tools be used to assist in the process. Where the stated guidelines do not address a specific area, it is either described in the ALM Baseline. This section provides guidelines for the following: Performance Guidelines to minimize the amount of data transferred to mobile devices and maintain the minimum acceptable levels of performance for mobile websites Usage Metrics Specifies the tool used for metrics gathering and mobile websites usage analytics Load Testing Tools used for load testing mobile websites Functional Testing Guidelines and options for testing the functionality of mobile websites Device Testing Testing mobile websites on devices
11 Appendix A: HTML5 FEATURE CHECKLIST This checklist is to be used to evaluate HTML5 features used by an application. It is referenced in the HTML5 section of the Application Development Architecture guidelines. Feature Description Used Application Cache Offline package installation. Web storage Persistent and session storage. Web SQL storage Persistent SQLite storage. Geolocation Geolocation & tracking using GPS, cells or Wi-Fi. Multimedia Video & Audio Players Server-Sent Events Allow data to be pushed from server Web Sockets Bidirectional protocol over HTTP Web Workers Threading and background process communications Canvas API 2D Drawing API SVG Scalable Vector Graphics Motion Sensors Accelerometer, Gyroscope, Magnetometer WebGL 3D Canvas for the web Network Information Connection Type: 2G, 3G, 4G, WiFi API File API Opening local files through input type CORS Cross origin Resource Sharing, for cross domain AJAX requests HTML Media Capture Taking pictures, record video and audio from an input file type Notifications API Background alert notifications IndexedDB Agnostic database system (replacement for Web SQL) getusermedia Camera access for <video> element FullScreen API Allow the application to get a full screen mode Page Visibility API Determine current visibility state Animation Timing API Performance timers for HTML5 animations
12 Exemptions from this Standard: There will be no exemptions to this standard. Refresh Schedule: All standards and referenced documentation identified in this standard will be subject to review and possible revision annually or upon request by the DPW Information Technology Standards Team. Standard Revision Log: Change Date Version Change Description Author and Organization DPW Mobile Website Dev Standards v1.doc Page 12 of 12
UX & Cross-Platform Mobile Application Development Frameworks Esteban Angulo Javier Alonso Xavier Ferre 01/01/2014 Laboratorio de Ingeniería del Software Escuela Técnica Superior de Ingenieros Informáticos
MASARYK UNIVERSITY FACULTY OF INFORMATICS Best Practices in Scalable Web Development MASTER THESIS Martin Novák May, 2014 Brno, Czech Republic Declaration Hereby I declare that this paper is my original
Mobile Application Primer 1. Introduction!... 4 1.1 Acknowledgments!... 5 1.2 How this document is structured!... 5 1.3 Summary of approach!... 5 2. The mobile landscape!... 7 2.1 Some global trends!...
Building A Better Network Monitoring System A report submitted in fulfillment of the requirements for the degree of Bachelor of Computing and Mathematical Sciences with Honours at The University of Waikato
Product Overview for Windows Small Business Server 2011 December 2010 Abstract Microsoft offers Windows Small Business Servers as a business solution for small businesses by providing a simplified setup,
Convergence of Social, Mobile and Cloud: 7 Steps to Ensure Success June, 2013 Contents Executive Overview...4 Business Innovation & Transformation...5 Roadmap for Social, Mobile and Cloud Solutions...7
CS411 Software Architecture Design Final Project Group 10 Customer Relationship Management System Ali Ozcan Fuat Basik M. Yusuf Ertekin M. Emre Nevayeshirazi 20700687 20701411 20702750 20701946 Customer
Kony Write Once, Run Everywhere Mobile Technology WHITE PAPER July 2012 Meeting the BYOD challenge with next-generation application and device management Overview... 3 The Challenge... 4 MAM Functions...
Kony Mobile Application Management (MAM) Kony s Secure Mobile Application Management Feature Brief Contents What is Mobile Application Management? 3 Kony Mobile Application Management Solution Overview
PROJECT FINAL REPORT Grant Agreement number: 212117 Project acronym: FUTUREFARM Project title: FUTUREFARM-Integration of Farm Management Information Systems to support real-time management decisions and
HP Performance Engineering Best Practices Series for Performance Engineers and Managers Performance Monitoring Best Practices Document Release Date: 201 Software Release Date: 2014 Legal Notices Warranty
HP Performance Engineering Best Practices Series for Performance Engineers and Managers Performance Monitoring Best Practices Document Release Date: May 2009 Software Release Date: May 2009 Legal Notices
UNITED STATES SECURITIES AND EXCHANGE COMMISSION Washington, D.C. 20549 FORM 10-K (Mark One) ANNUAL REPORT PURSUANT TO SECTION 13 OR 15(d) OF THE SECURITIES EXCHANGE ACT OF 1934 For the fiscal year ended
Configuration, Change, and Release Management Policies and Procedures Guide Table of Contents Section 1 Introducing Configuration, Change, and Release Management...5 1.1 Overview of Configuration, Change,
Continuous Compliance for Energy and Nuclear Facility Cyber Security Regulations Leveraging Configuration and Vulnerability Analysis for Critical Assets and Infrastructure May 2015 (Revision 2) Table of
General Principles of Software Validation; Final Guidance for Industry and FDA Staff Document issued on: January 11, 2002 This document supersedes the draft document, "General Principles of Software Validation,
Google Apps as an Alternative to Microsoft Office in a Multinational Company The GAPS Project Thesis presented in order to obtain the Bachelor s degree HES by: Luc BOURQUIN Supervisor: Thierry CEILLIER,
Challenges for Web Analytics Applications on Mobile Platforms WILLIAM ZHANG Master of Science Thesis Stockholm, Sweden 2013 Challenges for Web Analytics Applications on Mobile Platforms WILLIAM ZHANG DD221X,
Outsourcing Workbook Page 1 Copyright 2008 Notice of rights All rights reserved. No part of this book may be reproduced or transmitted in any form by any means, electronic, mechanical, photocopying, recording,
The Critical Security Controls for Effective Cyber Defense Version 5.0 1 Introduction... 3 CSC 1: Inventory of Authorized and Unauthorized Devices... 8 CSC 2: Inventory of Authorized and Unauthorized Software...
Securing Microsoft s Cloud Infrastructure This paper introduces the reader to the Online Services Security and Compliance team, a part of the Global Foundation Services division who manages security for
UPTEC IT 13 013 Examensarbete 30 hp Augusti 2013 Data Driven Development for Mobile Applications Oskar Wirén Abstract Data Driven Development for Mobile Applications Oskar Wirén Teknisk- naturvetenskaplig
Reducing Total Cost of Ownership: Delivering Cost Effective Enterprise Business Intelligence A White Paper by MicroStrategy Reducing Total Cost of Ownership: Delivering Cost Effective Enterprise Business
Addressing NIST and DOD Requirements for Mobile Device Management Whitepaper 2013 ForeScout Technologies, Inc. All rights reserved. Call Toll-Free: 1.866.377.8771 www.forescout.com Contents 1. OVERVIEW
G DATA TechPaper #0273 Mobile Device Management G DATA Application Development TechPaper_#0273_2015_04_21 Contents 1. 2. 3. 4. Introduction... 3 Mobile devices in the enterprise... 3 2.1. Benefits... 4