[Reports] Reports improvements
planned
C
Cherry Del Castillo
Feedback:
- food tags and food insights should be included
- member would like the daily reports to be more interesting
- make reports concise
- daily reports need to be easier to digest with fewer words (easier to Gronk)
- evaluate the daily/weekly reports and numbers presented - too much data that most members won't understand. Simplify the most meaningful metrics
C
Cosima Travis
planned
C
Cosima Travis
in progress
C
Cosima Travis
Merged in a post:
meal name / description should be included in report
C
Cristina Escalante
Current behavior:
* Currently the meal name / description is the only required field when logging. The ingredients are NOT required and sometimes autogenerated incorrectly.
* The ingredients are the only items to appear in the monthly and weekly reports, and are cut off on the monthly report
Expected behavior(s):
* if a the ingredients field is required for the reporting feature to function, reporting should either use the description field instead, or be more strict about entering ingredients
* wrap text on the reports pdf, so meals with more than 3 ingredients can be shown
C
Cosima Travis
Merged in a post:
Display reports numbers using the same mental model as with diabetes-related numbers (low is good, high is bad)
C
Cheryl Bryant
As a user, I want to see report numbers displayed in the same way in which I think of diabetes numbers so I can easily understand whether my numbers are "good" or "bad." For example, in the diabetes world, lower glucose numbers are typically considered good, whereas high glucose numbers are thought of as bad. Same with Glycemic Index and Glycemic Load values of foods. In the Levels app, I have to do mental gymnastics to intuit/comprehend the reverse---that higher numbers are good and lower numbers are bad. It's confusing and disrupts my flow when managing pre-diabetes.
C
Cosima Travis
planned
Your feedback matters! We're planning this new feature based on your suggestions.