TABLE 4.
Checklist for application-development projects targeting nutrition improvement in community settings
| Checklist item | |
| Development | Work in development teams including researchers, practitioners, target users, and application developers |
| Utilize branding from a credible/familiar source within the application (for example, academic branding) | |
| Conduct predevelopment qualitative needs assessment of the target user population | |
| Use a behavior change theory as a broad base for application design | |
| Include target users through all key stages of application development/design | |
| Allocate resources to and conduct predeployment field testing with the target user group | |
| Features | Incorporate interactive features, an attractive interface, and nonrepetitive images and colors |
| Include a feature from each feature domain identified in this review | |
| Tailor features broadly to those most suited to the target user group | |
| Enable individual-user customization of application features | |
| Allow for changes in individual-user customization over time | |
| Nutrition content | Tailor information and environmental supports to subpopulations |
| Consider including >1 of the content areas identified in this review | |
| Consider including >1 of the feedback strategies identified in this review | |
| Include both positive and negative reinforcement of eating behaviors | |
| Use graphical presentations, such as colors, traffic light, and star representations | |
| Evaluation and reporting | Allocate resources to, conduct, and report on application usability and consumer satisfaction evaluation |
| Utilize existing tools, such as those identified in this review, in usability and satisfaction evaluation | |
| Clearly define and evaluate health outcomes to be influenced by the application | |
| Design studies to identify the contribution of the application to outcomes in multicomponent-program trials | |
| Describe the application and its development in detail in publications, including pictures of the interface and application flow | |
| Utilize the technical terminology of the area (that used in this review) when writing reports |