Selected by Let's Make It Fund × BambuLabSelected by the Let's Make It Fund — Bringing Brew Supply to life with BambuLabAeroDial: keep every AeroPress dial-in decision visible
AeroDial is a browser-based AeroPress dial-in workspace for logging what changed, recording what landed in the cup, and choosing the next comparison without losing the session history. It keeps judgment manual and the evidence visible: the app organizes your brews, but it does not predict taste or prescribe a winning recipe.
Competition practice and limited-coffee sessions where several fast iterations must remain comparable and defensible.
Brewers looking for an automatic recipe recommendation, cloud collaboration, or laboratory extraction analysis.
| Brew | Time | Inputs | Outputs | Marks | Actions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Dose (g) | Grind | Brew water temp (C) | Brew water (g) | Immersion time (s) | Pressed yield (g) | Final beverage (g) | Bypass (g) | Extraction -10 to +10 | Strength -10 to +10 | Overall score 1 to 9 | Better than last brew? | Descriptors | Custom descriptors | ||||
Next brew | Ready to log | g | C40 24 clicks | °C | g | s | g | g | 0 | Floral, Fruity, Berry, Dried Fruit, Citrus Fruit, Sour / Fermented, Sour, Fermented, Green / Vegetative, Chemical, Musty / Earthy, Woody, Roasted, Cereal, Burnt, Tobacco, Nutty / Cocoa, Nutty, Cocoa, Spice, Sweet, Vanilla / Vanillin, Brown Sugar, Other | white peach, earl grey | After commit | |||||
Dial-in snapshot
Taste map
See where each brew landed across extraction and strength
What changed across brews
Compare how your brews moved over time
Why AeroDial exists
AeroDial gives competition brewers a structured way to log what changed, compare the cup against the previous brew, and keep finite coffee sessions readable while the dial-in moves quickly. It is designed for sessions where the main problem is not finding another idea, but preserving enough context to trust the next decision. That makes it especially useful once the brewer already has a plausible recipe direction and now needs cleaner comparisons.
- Keep one draft row ready at the top while preserving a reverse-ordered brew history below it.
- Track manual quality, extraction, strength, and descriptors without collapsing the session into one vague memory.
- Use it as a dial-in notebook for AeroPress practice rather than as a recommendation engine.
- Compare each brew against the last one so direction of change stays visible instead of disappearing into isolated notes.
- Preserve finite-coffee sessions well enough that a front-runner can still be defended after several quick iterations.
- Keep late-session judgment anchored to written context instead of trying to reconstruct the session from memory alone.
Evidence-bounded report with variable-specific denominators, interactive findings, methods, limitations, and normalized public data.
Open WAC 2025 23-recipe research reportA practical training structure for competition brews, logging, workflow, and serving.
Read AeroPress championship prep frameworkA practical explanation of hidden variability in AeroPress brewing and how to reduce it.
Read Why AeroPress brews stop matchingAeroBox turns grams-out and press speed into measurable recipe variables.
View AeroBox precision press standChoose the comparison before adding columns. Core mode covers the fast recipe and cup fields needed for many sessions; Detailed mode is useful when preparation, water, agitation, filtering, equipment, or service changes must remain visible. Hidden columns stay part of the saved record even when they are not shown in the grid.
The pinned row is the next brew, not another historical result. Duplicate a useful logged brew into it, change only what the next test requires, and commit it after brewing. Reverse-ordered history keeps the newest result nearby while preserving the earlier path that led to the current front-runner.
Extraction, strength, quality, descriptors, and competition markers are manual observations. The charts summarize the values you enter and help reveal direction across a session; they do not infer missing measurements, correct tasting bias, or establish that two differently scaled variables have the same scientific meaning.
AeroDial stores named sessions in this browser and supports JSON import and export. Export important work before moving devices or clearing storage. The app has no account, backend synchronization, multi-user editing, automatic recommendation layer, or hidden cloud copy of the coffee notes you enter.
When a session is finished, keep the exported record beside the coffee and recipe notes it describes. Context outside the grid still matters when the same recipe is revisited later.
Start with a plausible recipe and log the first cup honestly. Duplicate a useful brew into the pinned draft row, change the smallest number of inputs that can answer the next question, and keep input notes separate from what was perceived after tasting.
Use Core mode when speed matters and Detailed mode when preparation, agitation, filtering, water, or service choices need a fuller record. Marking a front-runner is a manual judgment, not a score calculated by the app.
Read trends as a history of the values you entered. Normalized lines make unlike units visible in one frame, but they do not turn temperature, time, and sensory ratings into one comparable scientific scale.
AeroDial does not predict extraction, cup quality, or the next winning recipe. Missing TDS or extraction measurements remain missing, and sensory ratings are personal observations rather than laboratory outputs.
Sessions live in this browser unless exported. There is no login, backend sync, or collaborative editing in the current version, so important competition work should be exported before storage is cleared or the device changes.
Dense logging can become its own distraction. Use only the columns that affect the current decision, hide the rest, and stop adding detail when the record no longer improves the next comparison.
Brew Supply apps organize decisions that would otherwise be scattered across memory, paper notes, and disconnected calculator results. They are most useful when the record changes what you do next: repeat a promising setup, isolate one variable, notice that inventory is running out, or reject a comparison that changed too many things at once. More fields are not automatically more rigor; the useful record is the smallest one that still explains the next decision.
The browser remains the operating boundary. Review inputs before committing irreversible workflow actions, export work that matters outside the current device, and keep sensory conclusions separate from what the software can calculate. Neither a polished chart nor a saved session turns subjective notes into laboratory evidence. The brewer remains responsible for tasting, safety, competition compliance, and deciding whether the added structure is worth the time.