| Literature DB >> 31682575 |
Katherine Marie Appleton1, Jeff Bray2, Sarah Price2, Gernot Liebchen3, Nan Jiang3, Ioannis Mavridis4, Laure Saulais5, Agnès Giboreau5, Federico J A Perez-Cueto6, Rebecca Coolen7, Manfred Ronge7, Heather Hartwell2.
Abstract
BACKGROUND: Increasing pressure from governments, public health bodies, and consumers is driving a need for increased food-based information provision in eating-out situations. Meals eaten outside the home are known to be less healthy than meals eaten at home, and consumers can complain of poor information on the health impact and allergen content of meals eaten out.Entities:
Keywords: diet; digitalhealth; eating; eating behavior; food; mhealth; mobile app; smartphone
Year: 2019 PMID: 31682575 PMCID: PMC6914280 DOI: 10.2196/12966
Source DB: PubMed Journal: JMIR Form Res ISSN: 2561-326X
MoSCoW (Must have, Should have, Could have, Won’t have) requirements for the app.
| MoSCoW | Requirementsa |
| Must have |
Provide detailed and accurate dish information as supplied by the manufacturer, including ingredients and allergens; Include nutrient information (calories, sugar, fat, saturated fat, and salt); Include information allowing dietary classifications; Include price per dish, allowing assessments of “value for money”; Provide the information in an easily accessible format; Enable quick information access, eg, via a QR (quick response) code; Allow users to store personal preferences about dietary needs and requirements, for example, religion, vegetarian, and vegan; Tailor menu presentation based on user profile; Warn users for certain dishes based on user preferences, for example, allergens and religious dietary needs |
| Should have |
Adopt a traffic light type coding system for the nutritional information; Provide additional detailed information if required; Provide a calorie calculator allowing assessment of a whole meal composed of several dishes; Allow users to set a desired calorie limit per dish; Allow presentation of all dishes to retain free choice for the consumer while retaining a tailored presentation based on the user profile |
| Could have |
Provide information about ingredient provenance and organic nature; Provide information about animal welfare, environmental impact, and fair trade nature of all ingredients; Allow users to set favorite food region; Allow users to set favorite dish or specific food items; Enable recommendations based on user preferences; Store previous purchase history; Enable recommendations based on previous consumption; Provide warnings of over or excess consumption; Provide personalized food messages for each user; Allow sharing via social media; Allow users to take photos of dishes/meals chosen; Allow users to search for dishes; Allow users to access menus in advance; Include functionality to preorder meals; Include functionality to feedback dish choices to a canteen; Include functionality to feedback comments/suggestions to a canteen; |
| Won’t have |
Provide generic dish information; Limit consumer choice; Provide information on allergen traces; Provide advertisements; Support push notifications, for example, for special offers; Include functionality to allow users to pay via the app; Include functionality to feedback sales to a canteen |
aDefinitions: a) Dish: can be made up of several food items, for example, lasagna with side salad; b) Food item: something a consumer can buy, which has nutritional facts and can fit a food classification; c) Nutritional fact: a fact about the nutritional values of a food item (eg, salt level or sugar level); d) Food classification: information about food items in relation to dietary classifications such as vegetarian, vegan, kosher, or halal.
Details of the prototype app per user interface screen.
| Screen | Display | User actions | |
|
| |||
|
| Screen 1 | Welcome and option for tutorial | User swipes to progress |
|
| Screen 2 | Personalization screen | User has option to personalize the app (personalized functionality) or skip this (basic functionality) |
|
| Screen 3 | Display of local canteens with available information based on Global Positioning System locator | User selects desired canteen and clicks option to see menu |
|
| Screen 4 | Menu for the day is displayed pictorially, consisting of dish name, picture, price, and diet classification | Users can view all dishes available. Users can view full information per dish by clicking on any dish |
|
| Screen 5 | Information (description, energy, portion size, ingredients; allergens; and nutritional content (gram per 100 g) of fat, saturated fat, carbohydrate, sugars, fiber, protein, salt, using the traffic light system) is displayed for the dish | User can view all information. User can also toggle a heart symbol to send feedback to the caterer that they like the dish. Activation with the QR (quick response) code (per dish) results in immediate arrival at Screen 5 |
|
| |||
|
| Screen 2 | Personal preferences are available based on the following: Canteen selection (local canteens available); Diet type: vegetarian, vegan, pescatarian, halal, kosher; Allergens: celery, cereals, crustaceans, eggs, fish, lupin, milk, molluscs, mustard, nuts, peanuts, sesame, soybeans, sulfur; Dish calories | User selects preferences for canteen, diet type and allergens by moving a bar from “selected” to “not selected.” These are saved automatically on the consumer’s mobile phone and remain stored or can be updated at any time. The default selection is “not selected.” Users can also set a desired maximum amount of calories per dish using a sliding scale and is provided with WHO (World Health Organization) recommendations for men and women |
|
| Screen 4 | When personal preferences have been selected, the menu is provided such that preferred dishes are provided at the top, and less preferred dishes are provided at the bottom of the list. Dishes that do not fit the user profile based on diet type and allergens are provided grayed over | Users can view all dishes available. Users can view all information per dish by swiping across the dish |
Figure 1Screenshot of the FoodSMART app: screen 1.
Figure 3Screenshots of the FoodSMART app: screen 5.
Mean and standard deviation of responses to all individual questions in the SUS questionnaire plus the additional question, for all consumers (N=233).
| Question | Value, mean (SD)a |
| I think that I would like to use this system frequently | 2.4 (1.1) |
| I found the system (was not) unnecessarily complex | 2.8 (1.0) |
| I thought the system was easy to use | 2.8 (0.9) |
| I think that I would (not) need the support of a technical person to be able to use this system | 3.0 (1.1) |
| I found the various functions in this system were well integrated | 2.7 (0.8) |
| I thought there was (not) too much inconsistency in this system | 2.7 (0.9) |
| I would imagine that most people would learn to use this system very quickly | 2.9 (1.0) |
| I found the system (not) very cumbersome to use | 2.7 (1.0) |
| I felt very confident using the system | 2.6 (1.0) |
| I did (not) need to learn a lot of things before I could get going with this system | 2.7 (1.1) |
| I believe the FoodSmart App will be useful to customers in a canteen setting to help them to get informed about the dishes offered | 3.1 (0.9) |
a0=strongly disagree and 4=strongly agree.
Mean, SD, minimum, and maximum total System Usability Scale scores by gender, age, and event location for all consumers (N=233).
| Demographic characteristica | SUSb score, mean (SD) | Minimum-maximum | |
|
| |||
|
| Male (n=81) | 69.8 (14.6) | 32.5-100.0 |
|
| Female (n=143) | 67.9 (15.8) | 27.5-100.0 |
|
| |||
|
| 20-29 (n=115) | 67.0 (13.6) | 27.5-97.5 |
| 30-39 (n=39) | 73.9 (14.2) | 35.0-97.5 | |
| 40-49 (n=35) | 64.4 (19.7) | 32.5-95.0 | |
| 50+ (n=32) | 71.9 (16.4) | 45.0-100.0 | |
|
| |||
|
| United Kingdom (n=65) | 76.3 (13.7) | 42.5-100.0 |
| France (n=50) | 67.8 (14.4) | 32.5-95.0 | |
| Denmark (n=15) | 73.0 (16.8) | 45.0-97.5 | |
| Malaysia (n=30) | 62.8 (9.6) | 35.0-75.0 | |
| China (n=42) | 58.6 (15.6) | 27.5-87.5 | |
aNumbers by gender, age, and event location do not equal 233 owing to incomplete demographic information in returned questionnaires from some respondents.
bSystem Usability Scale.