Coming soon Makora
Macros. Clarity. Local.
Application
Makora
Macros. Clarity. Local.
This production is a private summary: description, learnings and stack are shown, the code stays private.
Draft. Written from the program notes and pending the author’s review.
- Status
- Coming soon
- Type
- Application
- Running since
- January 2025
- Role
- Architect and sole engineer
- Domains
- nutrition, personal data
- Cast
- TypeScript, Sqlite
Context and problem
Local-first nutrition PWA.
Assumption: people who track what they eat hand a detailed record of their habits to a service in exchange for a food database, and would keep tracking if the record stayed on their device.
Makora tracks macros with the clarity of a good ledger and keeps the record on the device; the food data comes from open databases, credited in the application.
Screens
How it was built
Built in 2 h · USD 55.46 of AI · 214 tests · 4 audits
Source: Trysac/13-makora docs/development-report.md (lines 10, 13, 32), dated 21 November 2026.
What the project taught
- Local-first makes privacy a property of the architecture rather than a promise in a policy.
- Open food databases come with licences that shape the product: crediting the source is a design requirement from the first screen, not a footer added later.
- A nutrition tracker lives or dies by the speed of logging a meal; every feature competes with that one interaction.
Case study in preparation
The full case study adds these sections when it is published:
- Constraints
- Architecture diagrams (C4 context and containers)
- Three key decisions
- What went wrong
- Results with dated evidence
- Demo video
- What I would do differently
Highlights
local first, privacy, open data