How we double-check the food advice in this app

This app tells you things that matter: which foods need extra care for choking, which contain major food allergens, and which carry age-specific safety warnings. You deserve to know how we try to keep more than 1,000 food pages accurate. Here is the system, in plain words.

A computer rechecks every food page before any update goes out

Before an update ever reaches your phone, a program rereads the entire food library looking for the mistakes that would matter most. A few examples of what it insists on:

Honey must never be listed as okay before 12 months. Ever.
If a page says “never serve this,” it must also say why.
Every fish on the FDA and EPA's “Choices to Avoid” list (their highest-mercury category) that appears in our library must be easy to find by the names people actually use, and each one must clearly carry that warning.
The same food listed under two names must carry the same safety guidance under both.

If any of that is wrong anywhere, the update simply does not go out until it is fixed. Not “we will get to it.” It cannot ship.

A person rereads the riskiest pages on a schedule

Computers catch mix-ups. They do not notice when the official advice changes. So every three months, one of us sits down and rereads the highest-stakes pages, the danger warnings, the allergen notes, the choking-age guidance, the fish lists, against the current guidance from the AAP, the CDC, the FDA and EPA, and NIAID. We made this schedule impossible to skip: if the review is overdue, we cannot publish any updates at all until it is done. Busy months happen to everyone. The block stays up anyway.

When we get something wrong, we say so where you can see it

Every safety and guidance correction goes in our public changelog, in plain words, including what we got wrong. Real examples: sugar apple and soursop were missing a warning their close cousins already carried, and logging oatmeal was wrongly counting as a wheat introduction. Every app gets things wrong sometimes. We publish our mistakes instead of hiding them.

What we will never do

We do not diagnose anything, ever. The app can tell you what you logged and what published guidance says. When that raises a health or safety question about your child, the interpretation belongs with your pediatrician, and our pages say so. One more honest thing: having a pediatric professional independently review our health and safety content is the bar we are working toward, and until a named clinician has reviewed a page, we will not pretend one has. Our editorial policy spells that out.

Sources

😋 🤢

Track it in YummyYucky

Log first tries and reactions, with an automatic allergen tracker when a food needs one, all in one place you can share with your pediatrician.

Start tracking for free

Last updated September 2026. Next review December 2026. How we write these: built from current published guidance from the AAP, CDC, FDA/EPA, NIAID, WHO, and other pediatric and public-health authorities, with sources cited on the page. See our editorial and medical policy for how we research, source, and update these, and how we double-check the food advice.

This is general information, not medical advice, and is not individualized for your baby. Always talk to your pediatrician about your baby's diet, introducing allergens, and any reaction. In an emergency, contact emergency services.

Some links in our guides are affiliate links: if you buy through them we may earn a small commission, at no extra cost to you. We only suggest things we'd actually use, and it never changes our guidance.