Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

clarify in app if quantity for cooked vs raw is before or after the cooking #134

Open
myusrn opened this issue Nov 16, 2019 · 2 comments
Open

Comments

@myusrn
Copy link

myusrn commented Nov 16, 2019

When you click on any item for more details on serving sizes some items have an amount if cooked and amount if raw, e.g. beans, grains and cruciferous vegetables. It would be helpful to clarify if a cooked serving size is referring to before you cook it or what it grows or shrinks to after being cooked. Perhaps a cooked portion size is already well understood to mean one of these two options?

@caugner
Copy link
Contributor

caugner commented Feb 9, 2020

I have had the same issue with the The How Not to Die Cookbook – and found the cooked serving size to always refer to the size of the cooked portion, not e.g. to the dried beans before soaking and cooking.

@myusrn Could you suggest how this could be clarified specifically in the app? (Ideally accompanied by a screenshot.)

@myusrn
Copy link
Author

myusrn commented Feb 9, 2020

Maybe just an asterisk or footnote number reference beside the word, e.g. cooked* or cooked[superscript1], that then is explained at bottom of content on that screen. It sounds like saying "cooked" is well understood to mean the portion size after cooked not the amount of ingredients used to do the cooking. If that is the case then maybe more appropriate to not clutter up the UI with * or footnote number superscript beside uses of word cooked in portion sizes and instead just call this out the daily dozen app faq page.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants