chellbook
chellbook takes any recipe a person pastes in and returns a version they can safely eat, then follows that answer out of the kitchen and into the supermarket aisle.
a safety product that happens to be about food.
the core loop
1. paste a recipe, by link or plain text.
2. the app converts it, asking a question only where guessing would be unsafe.
3. it returns a breakdown: what is fine, what had gluten and was swapped, what still needs a label read.
4. unresolved label checks ride the shopping list to the store.
5. cooking a result and rating the texture feeds a new version of the recipe.
four safety states, never a fifth
verified. supported by the recipe and by the ingredient's own published information. not a promise of absolute safety.
check the label. depends on the package. needs a certified gluten-free mark or a shared-equipment statement.
blocking. a known gluten source. this step cannot go ahead as written.
unknown. information is missing. one question closes the gap.
still undesigned
the trusted brands editor is referenced from profile and settings, but its editing UI is not designed.
cross-contamination in a shared kitchen is out of scope, and it is the single most requested thing from celiac users.
mid-cook discovery has no screen: what happens when a cook is already halfway through and finds the problem then.
recipe imagery is emoji placeholders, which is a placeholder and not a decision.
whether saved recipes open with no network is unspecified.
there is no designed behavior for an evidence line whose read date has gone stale.
the prototypes
you can open the product design showcase, opens in a new tab, which is the spec, or the wireframe exploration, opens in a new tab, which is the same product before the device chrome and the final palette.
next up is mfny concentrates, or go back to product designs.