01 · iOS · TestFlight
Great Hearth
A household operating system — not a task app, not a family app.
Hearth is a household operating system designed for however your home is organized — one person, a couple, a family, or roommates. It treats a household like a small agile team: there are plans, a Later list, a weekly planning ritual, and task ownership that distributes mental load fairly between everyone involved.
The core idea came from the gap most household apps miss. Running a home isn't a to-do list problem — it's a mental load problem. Someone has to remember the dentist needs scheduling, notice we're out of paper towels, plan what the weekend actually looks like. The task apps handle tasks fine, but none of them help with the invisible work of running the family itself. And all of them nag.
Hearth's discipline is the opposite. Gentle nudge, not dictator. Capacity is a ceiling, not a budget to fill. Empty states are wins, not failures. The language throughout is calm by design.
Four surfaces do the work.
Today is the daily agenda, but stretched — yesterday and today anchor a scrolling view that runs 14 days forward, so tomorrow and next Thursday are one gesture away. Real calendar events flow alongside tasks. Open-time markers show where things could actually fit. When the day slips, running-late shortcuts do the deferral work in two taps.
Plans groups projects by Area (Household, Personal, Together, or whatever you name). Each Plan has a Now list of active work and a Later list for ideas that aren't ready yet — because ideas need a home without polluting the active view. Standalone tasks live here too, side by side with Plan work.
Weekly Meeting is the 20-minute guided ritual that makes the rest of the app honest. Look back at what shipped. Name what's already true (fixed events, life overhead, cooking time). Set a capacity budget with actual math. Pull from Later until the week fits — then stop.
Activity is the shared feed of what's happened, so nobody has to re-explain what got done.
The ownership model is the one thing most task apps get wrong. Assignee is who's executing the task; owner is who's holding the mental load for it — remembering it exists, noticing when it's stuck, deciding when to promote it. Hearth makes that distinction explicit, because "who's doing this" and "who's tracking this" are different questions.
The facts.
Role
Design and build — solo.
Year
2026
Stack
iOS · EventKit
Shipped
TestFlight — invites by email · greathearth.com
Status
In testing
If you’re making something
Tell me what it is — I’d rather hear the problem than the brief.