About
Built by one person, for an ordinary week.
Emira is not a startup with a content team. It is one developer, one Android app, and a set of decisions that were argued out one at a time, usually after the previous version turned out to be wrong in practice.
Why this exists
Every food tracker works on a good day. You had oats, you weighed them, you found them in the database, you logged them. The trouble starts on a normal day. Someone brought pastries, dinner was in a restaurant with no menu data, and you cooked something with one hand while holding a conversation with the other.
That is where logging quietly stops, and the reason is almost never motivation. It is effort. The meals that are hardest to enter are exactly the ones that are hardest to estimate, so the gaps in a food journal are not random. They cluster in the places that matter most.
Emira started from that observation. If the awkward meals are what decide whether a log is any good, then the input flow should be built around them, not around the easy case. Hence five ways in, sensible defaults instead of a form, and corrections that take a moment rather than a re-entry.
How it has actually gone
The first version, in November 2025, was an ordinary food journal: meals, a daily total, a calendar. It was useful enough to live with, which turned out to be the important part Everything after that came from using it and noticing what broke.
Conversational logging arrived in February 2026, photos and barcodes alongside it. Then a long stretch of unglamorous work on the thing that actually decided quality: not recognising food, but getting amounts right. Semantic search, remembered preferences, web lookups for products no database had, and a planning step so the model looks things up instead of asserting them.
By mid-2026 the app had learned when you tend to eat, stopped interrogating you about every missing gram, and started explaining where its numbers came from. The full record is on how Emira got here and in the release notes, which are written in plain language for the same reason this page is.
Things Emira deliberately does not do.
A product is defined at least as much by its refusals. These four come up often enough to be worth stating.
No weight history
Emira reads your weight from Health Connect and never keeps its own record of it. There are enough apps turning a number on a scale into a daily verdict.
No invented certainty
An estimated ingredient says it is estimated. Presenting a guess with the same confidence as a scanned label is the thing that makes people stop trusting these apps.
No streak that punishes a normal week
One missed day is grey, not a failure. A system that breaks the moment life happens teaches people to stop opening the app.
No advice
Emira records and explains. It does not tell you what to eat, and the nutrition writing on this site cites sources rather than issuing instructions.
Who is behind it
Elian, developer and sole maintainer, based in Germany. One person writes the app, the backend, this site and the release notes.
That is worth saying plainly for two reasons. It explains the pace, because Emira is in private beta because it is genuinely still being built, not as a growth tactic. And it means feedback goes to the person who will act on it, which is why waitlist invitations go first to people who intend to use it properly and say where it falls over.
How this site is written
Nutrition content here is informational and carries citations. Numbers about Emira's own performance name the benchmark run they came from, and where something has not been measured, the page says so instead of estimating. The accuracy page is the clearest example, because the most interesting figure on it is the one that is still missing.