←back to thread

311 points joshdickson | 5 comments | | HN request time: 0s | source

Hi HN!

Today I’m excited to launch OpenNutrition: a free, ODbL-licenced nutrition database of everyday generic, branded, and restaurant foods, a search engine that can browse the web to import new foods, and a companion app that bundles the database and search as a free macro tracking app.

Consistently logging the foods you eat has been shown to support long-term health outcomes (1)(2), but doing so easily depends on having a large, accurate, and up-to-date nutrition database. Free, public databases are often out-of-date, hard to navigate, and missing critical coverage (like branded restaurant foods). User-generated databases can be unreliable or closed-source. Commercial databases come with ongoing, often per-seat licensing costs, and usage restrictions that limit innovation.

As an amateur powerlifter and long-term weight loss maintainer, helping others pursue their health goals is something I care about deeply. After exiting my previous startup last year, I wanted to investigate the possibility of using LLMs to create the database and infrastructure required to make a great food logging app that was cost engineered for free and accessible distribution, as I believe that the availability of these tools is a public good. That led to creating the dataset I’m releasing today; nutritional data is public record, and its organization and dissemination should be, too.

What’s in the database?

- 5,287 common everyday foods, 3,836 prepared and generic restaurant foods, and 4,182 distinct menu items from ~50 popular US restaurant chains; foods have standardized naming, consistent numeric serving sizes, estimated micronutrient profiles, descriptions, and citations/groundings to USDA, AUSNUT, FRIDA, CNF, etc, when possible.

- 313,442 of the most popular US branded grocery products with standardized naming, parsed serving sizes, and additive/allergen data, grounded in branded USDA data; the most popular 1% have estimated micronutrient data, with the goal of full coverage.

Even the largest commercial databases can be frustrating to work with when searching for foods or customizations without existing coverage. To solve this, I created a real-time version of the same approach used to build the core database that can browse the web to learn about new foods or food customizations if needed (e.g., a highly customized Starbucks order). There is a limited demo on the web, and in-app you can log foods with text search, via barcode scan, or by image, all of which can search the web to import foods for you if needed. Foods discovered via these searches are fed back into the database, and I plan to publish updated versions as coverage expands.

- Search & Explore: https://www.opennutrition.app/search

- Methodology/About: https://www.opennutrition.app/about

- Get the iOS App: https://apps.apple.com/us/app/opennutrition-macro-tracker/id...

- Download the dataset: https://www.opennutrition.app/download

OpenNutrition’s iOS app offers free essential logging and a limited number of agentic searches, plus expenditure tracking and ongoing diet recommendations like best-in-class paid apps. A paid tier ($49/year) unlocks additional searches and features (data backup, prioritized micronutrient coverage for logged foods), and helps fund further development and broader library coverage.

I’d love to hear your feedback, questions, and suggestions—whether it’s about the database itself, a really great/bad search result, or the app.

1. Burke et al., 2011, https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3268700/

2. Patel et al., 2019, https://mhealth.jmir.org/2019/2/e12209/

1. neilv ◴[] No.43574008[source]
Small objections to the licensing terms, and the name...

I've recently been considering making my own open source nutrition app, (since every single one I've looked at seems to either violate my privacy&security, or is designed/works very poorly), but the available "open" nutrition info databases for bootstrapping have seemed poor.

So I looked at the license of this database, and the idea of making it "open" is good and maybe appropriate. But the attribution requirements to promote this other, commercial, product are a little annoying. And could also be a little confusing in app store listings.

> Attribution Requirements: If you display or use any data from this dataset, you must provide clear attribution to "OpenNutrition" with a link to https://www.opennutrition.app in:

> * Every interface where data is displayed

> * Application store listings

> * Your website

> * Legal/about sections

Additionally, I've soured on single companies that call themselves "open". "Open" has a few-decades history in computers, as everyone realized the dangers and costs of proprietary lock-ins, and so created concepts such as "open systems" and "open standards". Appropriating the "open" term for a single company, for something more proprietary than open (like the very proprietary OpenAI that's mentioned many times in https://www.opennutrition.app/about ), rubs a bit the wrong way.

replies(1): >>43574349 #
2. joshdickson ◴[] No.43574349[source]
The licensing terms are identical to similar projects including OpenFoodFacts (which also has an app) and OpenStreetMap, see:

https://wiki.openfoodfacts.org/ODBL_License

You may disagree with each of those projects as well, but, I am following long-standing licensing in this space. I also have used some OFF data for product naming, and as a result, their terms state I have to maintain their license.

Creating these databases involves a tremendous amount of time and effort, and it would not make sense for me to make this data available to commercial entities to use without attribution. The alternative is not a MIT-licensed dataset, it is no dataset.

replies(1): >>43574633 #
3. neilv ◴[] No.43574633[source]
The two you cite, OpenFoodFacts and OpenStreetMap are non-profit/not-for-profit, known for their databases, not for competing commercial apps.

I appreciate the difficulty of building a good database. Can you say why you created a new one, rather than starting with OpenFoodFacts? (Was it quality issues? Too hard to update? You wanted additional info? You didn't want their licensing terms? You wanted the advertising boost?)

replies(1): >>43574771 #
4. joshdickson ◴[] No.43574771{3}[source]
I've explained why OFF is not an adequate source in and of itself for a food logging app elsewhere in the thread. If it were usable in and of itself, I wouldn't have had anything to build on the database front and would have just used it as-is.

https://news.ycombinator.com/item?id=43570775

replies(1): >>43578452 #
5. neilv ◴[] No.43578452{4}[source]
Thanks, that part makes sense.