Streamezzo S.A. - All rights reserved
Copyright 2001-2010
Checklist: Application design definition
What is the definition checklist?
This checklist is based on the experience gained through the development of mobile applications and will evolve according to the development of future applications, it provides the most up-to-date patterns and practices.
Use this checklist as a tool to help you define the architecture and design of your applications, in order to reach good user experience.
When should I use the definition checklist?
Use it at early stage of the application development in order to avoid common pitfalls.
How should I use the definition checklist?
Print and fill this checklist according to your requirements and the development progress.
Why should I use the definition checklist?
The visual appearance plays an important role in:
- making the user stay with the application,
- supporting the use,
- keeping the user from getting bored.
As a result, this checklist gives you guidelines to develop applications that include:
- good design so as to increase the reliability of the application and the users’ willingness to start using it,
- good features and functionalities so as to keep up the positive experience.
Definition of deployment and infrastructure
| ACTION | OK | OBSERVATIONS |
| The list of devices the application is supposed to support is identified (see supported devices here). |
||
| All devices are available. | ||
| Mobile network is available (SIM cards, network QoS...). | ||
| Server development environment is available. |
||
| Server preproduction & production environments are defined (see example figure here). |
||
| Server preproduction & production environments will be available in due time. |
||
| Server environment benchmarking after application development and prior to production is planned. |
||
| Application certification is planned, when applicable (see tutorials for each mobile platform here). | ||
| Provisioning solution for delivering the application to devices is defined. |
||
| Provisioning server benchmarking after application development and prior to production is planned. |
Definition of architecture and design
| ACTION | OK | OBSERVATIONS |
| Storyboard (with all relevant information) is specified. |
||
| Available user interactions (keypad, touchscreen...) have been considered. |
||
| Adapted ergonomics for the mobile end-user have been used. | ||
| Application requirements have been completed as detailed specifications (additional behaviours, controls... - see extract here). |
||
| Available components that can be used have been identified (see list here). | ||
| Which content is supposed to be local (on device) vs distant (server-side) is identified. |
||
| Use of smart mobile data update has been defined (append - see tutorial here). |
||
| Errors management is specified (see tutorial here). |
||
| Use of caching facilities is defined (see tutorial here). |
||
| Media assets have been optimized (bitmaps, video, audio - see tutorial here). |
||
| Data sources / connection to 3rd party back-ends (databases, web services...) have been identified. |
||
| Application review after application development and prior to production is planned (see checklist here). |
