One outing. Five children. Five different lessons.
Every other homeschool app assumes a fixed address, a desk, and one child on a grade-level track. We built the inverse: a curriculum engine where where you are is an input, where a single afternoon at a canyon credits a six-year-old, a three-year-old, a toddler and two infants at their own levels — and where the whole thing keeps working with zero bars for a week.
Free for beta families · founder pricing kept for life · no card, no spam
One activity. Many participants. Per-child credit.
Most software collapses those three into one row, and then “the little one can watch” becomes the only way to include a toddler. We keep them separate, so the engine is structurally incapable of handing a child a lesson that is not hers.
Roles, not ages
Each activity declares slots — measurer, recorder, counter, fetcher, teacher, subject — with the band range each one needs. The engine pulls every slot’s objective from that child’s own frontier.
Teaching counts
When the six-year-old teaches her sister to count, that is a retention demonstration of her own mastered skill. Pedagogically true, and the cheapest evidence in the system.
A supervision budget
Hands-on steps happening at once can never exceed the adults actually available, minus one if someone is holding a baby. Checked in code after generation — never left to a prompt.
The rhythm is the scheduler.
A real homeschool day has structure. What it does not need is seat time. The unit of a day is an ordered sequence of blocks with duration bands — not clock times — which is the only register that survives a travel day.
Tap the day type each morning and the template swaps: travel day turns the morning basket into an audiobook and focused work into oral-only; park day lets Out & About swallow everything; sick day keeps the routines and breaks nothing.
Coverage is measured across a rolling seven days, never a single one. A park day that is ninety percent science and citizenship is not a failure. It is Tuesday.
- Morning routine15mIcon cards all five children can tap. Teeth, hair, beds, shoes.
- Morning basket25mEveryone together: read-aloud, weather, and where are we on the map.
- Focused work3 × 12mOne-to-one rotation. Every slot pairs with an anchor task for the children not in it.
- Out & about60-180mThe main event. One outing, one activity row, a differentiated bundle per child.
- Rest / quiet90mTwins and the two-year-old nap. The six-year-old reads or listens.
- Afternoon making45mWatercolour the rock layers she measured this morning.
- Evening routine20mTidy, bath, read-aloud, and the chocks checked before tomorrow’s drive.
The constraints are the product.
A week with no signal
Lessons, maps, field guides and capture all work at zero bars. If a feature in the daily loop needs a network, we consider it a bug. Vector basemaps read straight off local disk.
Ledgers you cannot edit
Credits and observations are append-only. Mistakes are fixed with a compensating entry, never a quiet edit. This becomes a college transcript, and an unfalsifiable record is the entire point.
The app brags about being closed
Every lesson carries its device minutes and its off-device minutes, and the dashboard targets at least seventy percent off-device. There is no streak to protect and nothing to farm.
Children are not reachable
Nothing about a child leaves the household without a deliberate, per-item, revocable act by a parent. Not a policy we wrote — a boundary the database enforces.
A six-year-old and a three-year-old need different apps.
And a two-year-old needs no app at all — so we did not build him one. He gets tag-along mode inside the parent app: observation prompts a grown-up scores, producing a real record without ever handing him a device.
Find the layer of rock that looks like a stripe of rust. How many hands tall is it?
Teach Rose to count her piles of rocks out loud.
Stamps unlock when the GPS says she actually arrived.
No feeds, no infinite anything. One to three cards, read-aloud always available.
Tap once to hear the word. Tap twice to choose. The screen closes itself after ten minutes with a “let’s go outside” card.
A pre-reader surface: three targets, no text, and no way to fail.
The roadside museum matters more than the famous one.
National parks, state parks, historic sites and science centres come from open public-domain datasets, stored in full and searchable in a canyon with no signal. Everything else — the county historical society, the alpaca farm, the marker at the end of a gravel road — you add yourself, and the lesson plan we generate for it is ours to keep forever.
That is the part that makes this work offline. You do not need a third party’s description of a place in the field. You need the scavenger hunt, the questions, the printable journal page, and the five bundles — and those are ours.
We are looking for about a hundred families.
The app is not finished and we are not going to pretend otherwise. What we have is a complete design, a working database with the tenancy and record model already built, and 674 hand-authored curriculum nodes. What we need before launch is places — real ones, documented by families who actually stopped there.
Beta families help build that library and keep founder pricing for as long as they keep an account.