Streamezzo S.A. - All rights reserved
Copyright 2001-2010
Checklist: Application design review
What is the review checklist?
Based on the experience gained through the development of mobile applications and updated according to the development of future applications, this checklist 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 review checklist?
Use it at final stage of the application development, prior to production, in order to:
- review and optimize the application,
- detect and eliminate any bottleneck.
How should I use the review checklist?
Print and fill this checklist according to your requirements.
Why should I use the review 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.
Review of application deployment and infrastructure
| ACTION | OK | OBSERVATIONS |
| Server preproduction & production environments are available. |
||
| Server environment is configured for production (see settings here). | ||
| Server environment has been benchmarked and sized accordingly prior to production deployment. |
||
| Server environment is redundant prior to production (see figure here). | ||
| Provisioning solution for delivering the application to devices is available. |
||
| Provisioning server prior to production has been benchmarked and sized accordingly prior to production deployment. |
Review of application architecture and design
| ACTION | OK | OBSERVATIONS |
| Ergonomics are adapted for the mobile end-user. | ||
| Content dispatching, i.e. local (on device) vs distant (server-side), is relevant. |
||
| Smart mobile data update / single requests to server only is applied (append - see tutorial here). |
||
| Transferred data amount has been measured and optimized for each server request. | ||
| Access latencies between successive pages have been measured and optimized. | ||
| Errors management is available and complete (see tutorial here). |
||
| Caching implementation is relevant (see tutorial here). |
||
| Media assets are optimized (see tutorial here). |
||
| On-device memory occupation is acceptable. | ||
| Response time when accessing data sources / connecting to 3rd party back-ends is acceptable (databases, web services...). | ||
| Application packaging is properly configured (see guidelines for each platform here). |
