Heard Nutrition
BetaA simpler way to log meals you can actually review.
Heard lets you type or speak a meal, review the matched items, and get a nutrition breakdown grounded in USDA data. It is built for people who want faster logging without hiding uncertainty behind confident-sounding guesses.
A meal logger built around trust, not black-box answers.
Heard takes a natural-language meal description, breaks it into parts, matches those items against USDA FoodData Central data, and scales the nutrition to the serving you actually ate. The point is not just speed. It is that the result stays reviewable. You can see what matched, what counts toward totals, what still needs input, and where the app is being cautious.
That makes Heard different from a generic AI calorie guess. The goal is not to sound certain. The goal is to give you a result you can check before you trust it.
One meal description goes through a clear review flow.
- Type or speak a meal the way you would naturally describe it.
- The app parses that input into foods, quantities, and useful details.
- Each food is matched against USDA data and scaled to your serving.
- Review the rows, edit what needs help, and check what is included in totals.
- Save the meal or report anything that looked off.
Clearer input usually leads to better matches.
Strong inputs
- Lunch was 170 g 0% Greek yogurt, 15 g honey, and 30 g blueberries.
- Just ate 2 large eggs, 2 slices whole wheat toast, and 1 tbsp olive oil.
- 150 g extra lean ground beef, 200 g potatoes, and 75 g broccoli.
Harder to match
- Lunch was a bowl of Greek yogurt with some honey and blueberries.
- Just had a couple of eggs, a couple pieces of toast, and a spoonful of olive oil.
- Had a bowl of ground beef, potatoes, and broccoli.
Grams are still the strongest input when you have them. If you do not, household measures like cups, slices, and tablespoons can still work well for common foods. Brand and preparation details help most when they materially change the food.
Usable today, still honest about where it is weak.
Heard currently relies on USDA data only. That gives the app a strong public nutrition source, but it also means coverage is uneven in some areas. Some branded foods, niche products, and very specific preparations still need better support.
- Some foods will need manual edits, especially vague or branded items.
- USDA-only coverage means some results are stronger than others today.
- Rows with unclear quantities may be flagged instead of being over-guessed.
- Only calories, fat, protein, and carbohydrates are displayed for the beta.
- The beta is mainly about finding weak spots, improving match quality, and learning what users need most.
So the beta is not just early access. It is the phase where we learn where the current system is strong, where coverage needs work, and which improvements matter most in real use.
Meal logging is the start, not the whole story.
The longer-term goal is to make Heard a better everyday nutrition product, not just a faster input box. That includes broader food coverage, stronger matching, better saved-meal and repeat-use workflows, community & research features, and a product people can keep coming back to without feeling like logging is work.
The bigger picture matters, but it only matters if the product earns trust first. Faster should not mean looser. Convenient should not mean opaque. That is the standard we want to to keep as we grow.
If something feels off, that is useful signal.
If a match is wrong, a serving looks strange, or the product flow feels confusing, let us know. That kind of real-world feedback will help turn this from a promising beta into a stronger nutrition tool.