Table 3.
Criteria for selecting and reasons for not selecting nutrition and diet apps (N=2382).
| Criteria and barriers | Value, n (%) | |
| Criteria for selecting a nutrition and diet app | ||
|
|
Easy to use/convenient | 1570 (65.9) |
|
|
Costless/free of charge | 1413 (59.3) |
|
|
Automatic calorie estimation is supported | 1231 (51.7) |
|
|
Automatic nutrient estimation is supported | 1117 (46.9) |
|
|
Automatic food recording is supported | 1115 (46.8) |
|
|
Validated and certified | 1036 (43.5) |
|
|
Self-explanatory (no need for training) | 953 (40) |
|
|
History records are supported | 755 (31.7) |
|
|
Recipe and menu import functions are supported | 729 (30.6) |
|
|
Provides an option for adding nutritionally related events (eg, reflux) | 443 (18.6) |
|
|
A link for data transmission (eg, other apps) is supported | 217 (9.1) |
|
|
No opinion | 195 (8.2) |
|
|
Other | 95 (4) |
| Barriers to selecting a nutrition and diet app | ||
|
|
Major foods are missing | 977 (41.0) |
|
|
Incorrect calorie and nutrient estimation | 798 (33.5) |
|
|
Local foods are not supported | 655 (27.5) |
|
|
Unconvincing portion size estimation | 648 (27.2) |
|
|
Not personalized | 503 (25.1) |
|
|
Not validated and not certified | 567 (23.8) |
|
|
No opinion | 522 (21.9) |
|
|
Only manual entry of food type is allowed | 464 (19.5) |
|
|
Incorrect automatic food item recognition | 448 (18.8) |
|
|
Recipes are not considered for nutrient estimations | 376 (15.8) |
|
|
Only manual entry of portion size is allowed | 345 (14.5) |
|
|
User is required to be tech savvy | 310 (13.0) |
|
|
History records are not supported | 295 (12.4) |
|
|
Sharing of history records is not supported | 88 (3.7) |
|
|
Other | 83 (3.5) |