Coffee Brewing Journal App in 2026: Market Size, Revenue Precedents, Cost to Build
Last updated: 1 May 2026Category: Food & specialty beverageData source: MyAppTemplates analysis of 2026 public SOW benchmarks and shipped-app case studies
Executive Summary
What it is. A mobile journal for home-brewing hobbyists to log recipes, dial in grinders, track bean inventory, and rate cups across V60, AeroPress, espresso, and immersion. The core loop is brew → log variables (dose, ratio, grind, time, temperature) → rate → recall last best. Optional layers: bean library, café checkins, social shares, and a roasted-on-this-date timeline.
Who pays. Specialty coffee enthusiasts who already spend $200–$1,000+ on grinders and brewers. Annual willingness-to-pay for tooling sits around $20–$40 — well within IAP and lifetime-unlock territory. The buyer is not the casual drip drinker; it's the person watching James Hoffmann videos, weighing beans on a 0.1g scale, and lurking r/espresso.
Why now. Specialty home-brewing kept its 2020–2023 lockdown gains. Smart scales (Acaia, Timemore Black Mirror), Bluetooth thermometers, and prosumer espresso (Decent, Lelit Bianca) are mainstream, and there's no dominant journaling app — Filtru and Dripped are the visible incumbents and both are solo-built. The category is small enough to scare off VC-funded teams and large enough to support a one-person business at $20k–$60k MRR.
Scope Variants
Coffee brewing journal: Lean MVP → Production at 100k users
One idea, five scope tiers. Agency benchmarks vs DIY with the boilerplate plus Claude Code.
Every DIY build starts with the same flat boilerplate fee:$199 one-time — column below shows marginal Claude Code API spend on top
Production at 100k UsersMulti-platform, edge cache, BLE accessories
Web companion, Bluetooth scale integration, hardened CDN images, moderation, search
$90k–$150k
$310
99.4%
2–3 weeks
1. Real-app precedents
Two named indie apps anchor the category. Revenue figures below are estimated from public App Store rank and Sensor Tower / AppFigures benchmarks, 2026; treat them as wide bands, not audited financials.
Ship the brew loop and nothing else. Everything below maps to one or two days of Claude Code work against the boilerplate's auth, billing adapter, and Drizzle schema.
Week One Scope
The minimum lovable journal
Brew formBean, dose, water, ratio (auto-calc), grind setting, total time, taste rating 1–10, free-text notes.
Brew methodsV60, AeroPress, French press, espresso. Each with sensible defaults.
Bean libraryRoaster, origin, roast date, process. Linkable from any brew log.
Last bestOne tap to recall your highest-rated recipe for the current bean. This is the retention hook.
PaywallFree: 25 brews. Paid: unlimited + charts. $19.99 lifetime IAP using the boilerplate's RevenueCat adapter.
3. Differentiation angles that still work
Filtru and Dripped both lean iOS, English-first, espresso-friendly. The gaps below are real and shippable in a week each.
Angle
Android parity from day one
The openingThe two leading journals are iOS-first. Android coffee hobbyists are vocal and underserved.
Why the boilerplate fitsReact Native + Expo means iOS and Android from one codebase. Zero extra build work — the cost is the same.
Angle
Smart-scale CSV import
The openingAcaia and Timemore export brew CSVs. No journal app cleanly imports them.
BuildA Workers route that parses the CSV and writes brews against the Drizzle schema. One day with the @backend-dev subagent.
Angle
Café check-ins, not a social network
The openingHobbyists travel. Logging "this V60 at Onyx in Arlington" is meaningful; building a TikTok feed around it is not.
BuildLight location tag on a brew log + a personal map view. Skip the follow graph until you have 5k paying users.
How to take this from idea to App Store in two weeks
Assumes one builder, the $199 boilerplate, and Claude Code with the bundled subagents.
1
Day 1 — Schema
Define brews, beans, ratings, and recipes in db/schema.ts. Use /db-migrate to push to D1. The auth tables are already there.
2
Days 2–4 — Brew loop
Use /new-feature brews and /new-feature beans. The @mobile-dev subagent scaffolds the form screens; @backend-dev wires the routes.
3
Days 5–6 — Paywall
Configure RevenueCat product IDs and flip the Paywall screen to gate brew count. The billing adapter is already wired.
4
Days 7–9 — Polish
Charts (recharts/Victory), last-best logic, empty states, onboarding copy. This is where most apps die — give it real time.
5
Days 10–14 — Ship
TestFlight, Android internal track, screenshots, a one-page landing site, and a launch post in r/pourover. CI/CD is already running.
Frequently Asked Questions
Is this idea saturated?
No. Two visible incumbents, both solo-built, both iOS-first, and both with consistent App Store reviews asking for features they haven't shipped. Saturated would be five well-funded teams; this is a category with room for a third honest player.
Is IAP really the right monetisation?
Yes. The buyer treats their brewing setup as a tool, not a service, and a $19.99 lifetime unlock matches that mental model. Subscription works at the higher tier (cloud sync, social, web export) but lifetime IAP should be the default first SKU.
What's the realistic revenue ceiling for a solo builder?
Based on Filtru's estimated $20k–$60k MRR band, a well-executed second player should reasonably target $5k–$20k MRR within 18 months. This is a niche, not a unicorn — plan accordingly.
Do I need Bluetooth scale integration to launch?
No. Ship the manual brew form first. BLE integration is a v2 feature that justifies a price bump or a higher subscription tier — not a launch requirement.
Can I really build this for $95 in AI spend?
That's the marginal Claude Code spend for the Solo Launch tier on top of the $199 boilerplate, assuming you guide the agents and don't loop on the same screen for hours. Add 20–30% buffer if this is your first agentic project.
Why not just build it as a web app?
Because the brew happens at the kitchen counter with wet hands, a 90-second timer, and a bean bag. Native mobile with reliable timers and offline-first storage wins. The boilerplate ships RN + Expo for exactly this reason.
What's the honest reason most coffee journal apps fail?
They over-build the social layer before nailing the brew loop. The retention driver is "recall my last best V60 with this bean" — not a follow graph. Ship the loop, charge for it, then layer.
A small, defensible category with a clear two-week path to shipping.
Specialty coffee hobbyists pay for tools. Two solo-built incumbents prove the willingness, and both have visible gaps — Android, smart-scale import, web export. The brew loop fits inside the boilerplate's existing auth, paywall, and schema patterns. There's no infrastructure week to lose and no marketplace complexity to solve. Ship the journal, charge for it, and layer.