Salt alert is a mobile app concept helping parents to track sodium level in their kid's diet. High sodium diet is one of the causes of childhood obesity.
Domain to user research
Process to requirements
Concept to final design
User testing to Specification
Scholarly/Non-scholarly research summary
Stakeholder Interview Questions
Target User Group
During the initial research phase our focus was to understand the problem space of
childhood obesity. We did this by reading scholarly articles and interviewing possible mentor's/stakeholders in the project. Following this
we did extensive user research by interviewing 16 parents ( having children age 5-10 years) residing in the city of Bloomington, Indiana. Parents were chosen as target user group as scholarly articles suggest parent based intervention is the most effective in lowering possibility of childhood obesity. Easy access to parents was another factor which played a role in parents being selected as a user group. We concluded this phase by deciding parent's to be our primary user base and developed a few persona's to help us understand everyday life of parents.
B.J. Fogg's Design Process
A simple behavior to target
Systemic design concepts
During the requirements phase we came across B.J. Fogg's design process which helped us to guide this project. We decided to target a simple behavior of low sodium food amongst children after discussion with stakeholders. At this point we brainstormed system level concepts, unique concepts was one of the key criteria we kept in mind while brainstorming new concepts. Exemplar research helped us to understand existing applications across different technological medium. This research also helped us to understand possible rationale other designers had while designing the applications. Lastly we documented user scenario's and corresponding requirements. These scenario's were mainly derived from the storyboard's showcased in the next phase of the process i.e. design.
Mobile interaction storyboard
Android design pattern- Source: Google
Wireframe showing one of the workflow
Design phase started with storyboarind user's interaction with the mobile application.
A workflow was prepared after to consolidate user's expectation after story boarding and user scenario. At this point we consulted android 4.1 design patterns
to understand how existing patterns and components recommended by google could be used while designing wireframes. Usage of patterns while designing a application
can help designers to concentrate on bigger challenges faced by user's than worrying reinventing the wheel for every single design problem.
Formative user testing in progress
Task and Task completion timing- Quantitative data
Functional specification and next steps
Paper prototype was used to test the concept and various workflows with 5 parents. Formative usability testing was performed and the findings of this user testing were discussed with stakeholders to access the severity of issues. The main pain points in the workflow were the editing of child's profile and sharing of sodium level with family doctor. Functional specification were documented to help developers get a overview of the application. The pricing of this application and long term usage statistics would help us see if this application is successful in lowering sodium level in kid's diet.