fixedlanding
Today / what matters
The top landing stack for now, next, and tonight. This should always exist and should be the first thing the prototype gets right.
Non-negotiable
dashboard
Today is the dashboard.
This is the main home surface: what matters now, what the body is doing, what support needs surfacing, and what should stay visible no matter how the rest of the prototype evolves.
Dashboard / Today
Top-level home surface. This is now the real Today page as well: conceiving surfaces, daily context, and the things that must remain visible no matter how customisable the rest becomes.
Today stack
Fixed, non-negotiable
Conceive cards
Always visible
Quick capture
Fixed utility block
Custom modules
User-editable later
Fixed dashboard blocks
fixednon-negotiable
Conceive cards
Persistent assistive prompts. These stay visible even if the rest of the home screen becomes customisable.
Always visible
global layer
Global AI input
Ask anything or capture with voice/photo from the persistent top strip. This is a cross-app assistant layer, not a page-specific widget.
VoicePhotoPersistent
Customisable dashboard blocks
customisable later
Pinned modules
Calendar, cycle, meals, shopping, and budget can become the first user-configurable blocks once the fixed dashboard core is settled.
CalendarCycleMeals
customisable later
Household pulse
Shared status and family capacity should be optional on the dashboard, not mandatory from day one.
Optional block
later concept
Dashboard editing
Users should eventually be able to rearrange selected modules while the fixed core remains locked.
Later rule set
Morning routine
This should be the launch support page for getting out the door or into the day with less friction. It needs to bridge personal readiness, school logistics, and what the body is doing without becoming a giant checklist of shame.
Launch
Get moving
Body check
Energy / symptoms
School prep
Kid + handoff
Fallback
Low-capacity path
Core morning flow
real-use nextinteractive
Start-of-day flow
The minimal sequence for launching the day: meds, food, body check, and what absolutely needs to happen first.
Take meds
Before getting lost in the rest of the morning.
Water + breakfast
Enough to get the body online.
Check school / bag
Make sure the one critical item is covered.
LaunchMorning
body-aware
Body check
Morning energy, sleep hangover, brain fog, and symptom context should inform what the morning expects from you.
EnergySymptoms
future source
School / out-the-door prep
Lunchbox, school items, permission slips, pickup context, and anything Ollie-related that affects the morning.
SchoolOllie
Support + fallback
supportive
Low-capacity morning mode
On harder days, reduce the morning to essentials instead of pushing the full ideal routine.
Fallback
interactive next
Launch checklist
The next interactive step here would be a tappable morning sequence that can collapse once complete.
Interactive next
links to Today
Morning → Dashboard link
Once the morning launch is done, the user should naturally roll into the main Dashboard / Today surface.
Linked to Today
Chores
This should be the home for household jobs, chore timers, personal bests, and eventually the child-facing chore flow. It needs to work for both adult admin and Ollie-visible motivation later.
Today
Today's jobs
Timers
Focused completion
Rewards
Points / progress later
Kid-facing
Future Ollie layer
Core chores flow
real-use nextinteractive
Today’s chores
A clear list of today’s jobs, kept separate from the broader task system so chores do not disappear into everything else.
Put bins out
Before dinner pickup timing kicks in.
Empty dishwasher
Reset the kitchen for tonight.
Reset lounge room
Ten-minute tidy only.
TodayHousehold
behaviour layer
Timers + personal best
Future home for chore timers and “beat your best” motivation without making the experience childish for adults.
TimerPB
future source
Rewards / earnings
Later this can hold paid chores, stars, or reward logic once the base chore flow is stable.
Rewards later
Structure + scope
hook-up ready
Adult chores
The adult chore layer needs to stay clean and useful even before the child-facing layer is connected.
Adult mode
future source
Ollie chores
Future connection point for child-facing chores, stars, and visual reward loops.
Future Ollie link
interactive next
Check-off + timer start
Next interactive step here would be starting a timer or marking a chore complete from the same card.
Interactive next
Tasks
This page should make doing things easier, not increase guilt or backlog anxiety. It needs a clear top layer, easy capture, and gentle defer options for low-capacity days.
Top 3
Main execution layer
Quick add
Fast capture
Not today
Gentle defer
Later queue
Backlog without pressure
Core task flow
non-negotiableinteractive
Top 3 for today
A short list that helps you start. This should feel like “what matters now”, not “everything you haven’t done yet.”
Call the school
Confirm the timing change before lunch.
Send one email
Reply to the beta/support thread without opening everything else.
Order groceries
Do the essentials only.
Top 3Today
fast capture
Quick add
Fast text capture that sits inside the page flow and is easy to reach on desktop and mobile.
Text capture
supportive
Not today
Low-friction defer state for tasks that are real but not realistic today.
DeferSnooze
Task context
links to Today
Today view sync
The top task layer here should align with what appears on the Dashboard / Today surface.
Shared with home
supportive
Low-capacity mode
Offer a reduced task view when things feel too heavy, instead of surfacing the full list.
Reduced mode
later
Later queue
Keep the backlog visible enough to trust, but far enough away not to flood the main task view.
Backlog
Future task behaviours
interactive next
Checklist interactions
Tick off, reorder, or move tasks into “not today” directly from the page.
Interactive next
later
Task suggestions
Eventually the product can help choose what to do next — but only after the basic task layer feels trustworthy.
AI later
later
Linked modules
Tasks should eventually connect to meals, calendar, home admin, and school logistics without turning into a giant project manager.
Cross-module
Cycle tracking
This is the first real-use prototype page. It needs to support quick daily check-ins, meaningful symptom capture, and calm pattern visibility without feeling clinical or overwhelming.
Today
Fast daily check-in
Symptoms
Track what matters
Sleep + energy
Capacity signals
Patterns
Useful trend views
Daily check-in
todayfast entry
Today’s symptoms
Quick symptom check-in with the current must-haves present: dry skin, acne, brain fog, mood, fatigue, irritability, and any existing symptom set already being tracked.
Dry skinAcneBrain fog
today
Sleep + energy
Disrupted sleep, short sleep, well-rested, and current energy state. These should read as helpful context, not judgment.
Disrupted sleepEnergy
today
Wellbeing actions
Space for what helped today: meds, movement, protein, recovery actions, or other supportive habits that are worth correlating later.
What helped
Cycle context
context
Phase / day
Show current cycle day / phase clearly so daily symptoms are never separated from their context.
Phase-aware
context
HRT / meds notes
Simple visibility into gel/HRT or medication context so later patterns are explainable.
Medication context
context
Notes
Short free-text note for unusual days, GP-useful observations, or anything the fixed checkboxes miss.
Optional note
Patterns + review
prototype next
Pattern cards
Weekly / monthly summaries like “brain fog strongest here” or “sleep disruption tends to cluster here.”
Readable trends
prototype next
Correlation view
Connect symptoms with sleep, energy, meds, and wellbeing actions without making the UI feel like a spreadsheet.
Correlations
future export
GP summary
Eventually this should feed a clean medical summary rather than requiring manual reconstruction before appointments.
GP useful
Recovery
Worst-day support and low-capacity return paths.
working in hub
Bad-brain-day mode
Should feel integrated with Today, not hidden as a side utility.
prototype
Comeback paths
When the user falls off, the product should offer an easy re-entry point.
Family calendar
This should be the shared family spine: pickups, appointments, handovers, school events, and the day-to-day logistics that need one clear source of truth.
Today
What matters today
This week
Shared family spine
Pickups + handovers
Critical logistics
School / Ollie
Kid context
Core family timeline
non-negotiableinteractive
Today’s schedule
Only the events that matter today, with time, location, and what needs to happen next.
3:05pm
School pickup
Ollie pickup. Tight timing with therapy after.
4:30pm
Speech therapy
Bring notebook and snack. Travel buffer needed.
6:00pm
Dinner fallback
MMC option if handover runs late.
Pickup details
Primary pickup is Dani. Leave by 2:40pm to avoid a rushed therapy transition.
WhoDani
WhereSchool gate
NextDrive to therapy
Therapy details
Speech therapy starts at 4:30pm. Build in a snack / regulation buffer after pickup.
WhoOllie + Dani
WhereClinic
NextHead home
Dinner fallback
If the afternoon runs late, switch to the low-capacity dinner plan rather than improvising.
PlanMMC / easy dinner
WhyProtect evening capacity
LinkedMeals + shopping
TodayNow / next
working in hub
This week
A readable weekly spine so the family schedule feels coherent instead of scattered.
Week view
critical logistics
Pickups + handovers
Pickup timing, who’s doing it, handoff notes, and any timing pressure should be obvious at a glance.
PickupsHandover
Family context
prototype
School / Ollie context
School events, activities, permission slips, and child-specific schedule items should sit close to the calendar, not elsewhere.
SchoolOllie
later
Co-parent visibility
Scoped visibility later, but the calendar structure should allow for it from the beginning.
Later
later
Household pulse
Optional family-state context once the base schedule layer is stable and useful.
Optional
Future family behaviours
interactive next
Tap-through events
Clicking an event should eventually open a compact detail view with notes, who’s involved, and next action.
Interactive next
later
Conflict warnings
Surface overlapping commitments or impossible timing before they become chaos.
Conflict detection
later
Calendar → tasks link
Family events should eventually create or inform tasks without making the calendar noisy.
Cross-module
Ollie
Prototype-only kid-facing and parent-managed experience. This needs to hold the child-visible side of the product without turning into a separate app with no connection to the family system.
Today
Child-facing today view
Chores
Jobs + rewards
School
Homework / slips
Shared with Dani
Parent-managed layer
Prototype-only core
prototype only
Chores + rewards
One of the key reasons to keep the kids experience in prototype scope even while beta narrows.
ChoresRewards
future source
Homework / permission slips
Likely belongs near the family area, not detached from calendar/school context.
School
live direction
Shared with Dani
The prototype must work for both of you, not just as a solo-parent admin view.
Shared view
Co-parent
Kept visible in IA but not a first-pass prototype build. The structure should exist now so later access/scoping does not require a navigation rethink.
Schedule visibility
Scoped later
Shared costs
Future source
Permission slips
Family linkage
Communication
Not in first pass
later
Scoped access
Should emerge only after the core prototype surfaces are settled.
future source
Shared logistics
Future home for co-parent-specific visibility and schedule handoffs.
future source
Shared costs
Likely ties into Household → Budget later.
Shopping
This needs to be a fast, low-friction household list surface. It should clearly separate what already exists, what will be connected later, and what is only a prototype placeholder for now.
Quick add
Fast grocery capture
Current list
Core shopping surface
Meal-linked items
Cross-module feed
Store/grouping
Practical shopping flow
Existing source
existing sourceinteractive
Shopping list
This block should map to the existing shopping/list data source rather than inventing a new model.
Milk
Staple / weekly
Fruit
Lunchbox top-up
Dishwasher tablets
Running low
GroceriesCurrent source
existing source
Fast add
Quick grocery capture should attach to the same underlying list source, not a separate temporary system.
Quick capture
existing source
Common items
Frequently bought items or recurring staples should come from the same live list logic once wired.
Staples
Future source
future source
Meals → shopping link
Ingredients and meal plan choices should eventually feed directly into shopping without duplication.
Meals link
future source
Store / aisle grouping
Useful future enhancement once the core list is stable and trustworthy.
Grouping
future source
Household suggestions
Later the product can suggest missing items or low-stock essentials, but only after the base list works cleanly.
Suggestions later
Prototype placeholder only
placeholder only
Temporary capture tray
This is just a stand-in while we work out whether all quick capture should live here or from the broader launcher model.
Prototype only
placeholder only
Visual shopping states
Extra display-only states for testing layout before real data is connected.
Layout test
interactive next
Check-off flow
Next interactive step could be tapping items off while shopping, once we decide the exact live-source mapping.
Interactive next
Meals
This should hold weekly meal planning, low-capacity defaults, favourites, and the clean bridge into shopping. It needs to be clearly hook-up ready so we don’t invent a second meal model.
Week plan
Main meal surface
Low-capacity
MMC + easy dinners
Ingredients
Shopping bridge
Favourites
Fast repeat meals
Existing source
existing sourceinteractive
Weekly plan
This should map to the existing meal-planning source rather than becoming a disconnected planning layer.
Wed
MMC
Low-capacity fallback dinner
Thu
Tacos
Family-friendly, repeatable
Fri
Freezer meal
Backup for overload nights
MMC details
This is the low-capacity dinner default. Minimal prep, predictable, protects evening energy.
TypeLow-capacity
NeedsBasic pantry + fridge
PushSend ingredients to Shopping
Tacos details
Repeatable dinner with straightforward ingredients and easy leftovers.
TypeFavourite
NeedsTaco kit + veg
PushSend ingredients to Shopping
Freezer meal details
Emergency buffer option for hard evenings.
TypeBackup
NeedsFreezer stock
PushCheck freezer inventory
Week viewCurrent source
existing source
Ingredients
Ingredients need to stay tightly tied to the real meal source so the shopping bridge remains trustworthy.
Ingredients
existing source
Favourite meals
Repeatable go-to meals should come from the same live meal data rather than a separate shortcut list.
Favourites
Future source
future source
Low-capacity defaults
MMC and easy dinners should become first-class meal types, not buried fallback notes.
MMCEasy dinners
future source
Meal → shopping automation
Choosing meals should automatically push ingredients into Shopping once the source mapping is connected.
Shopping bridge
future source
Ollie fit / picky filter
Future source for child fit, preferences, and repeatable safe meals.
Ollie fit
Prototype placeholder only
placeholder only
Visual weekly layout
Prototype-only display state for testing layout before live meal data is connected.
Layout test
interactive next
Tap-to-choose dinner
Next interactive step here could be choosing a dinner card and surfacing linked ingredient behaviour.
Interactive next
placeholder only
Planning notes
Temporary planning commentary while we decide what belongs in the real source and what stays as UI support text.
Prototype only
Notes / capture
This is the temporary holding layer while the permanent capture model is refined. It should stay small and honest, because the real capture system now lives in the global AI layer.
Temporary notes
Short holds
Captured items
Need sorting later
Global AI link
Main input lives above
Future home
Not decided yet
prototype only
Quick notes
Short holding items that don’t yet belong anywhere else.
Temporary
global layer link
AI capture handoff
The long-term capture/input model should come from the global AI bar, not this page.
Global AI
later
Sorting rules
Later, captured items could be triaged into Tasks, Shopping, Meals, or Home.
Future sort
Budget
This should hold the household money snapshot, upcoming bills, grocery room, and spending visibility without turning into a finance app. It needs to be hook-up ready to the real budget source.
This pay cycle
Main snapshot
Upcoming bills
Near-term pressure
Groceries room
Shopping link
Critical admin
Money context
Existing source
existing sourceinteractive
Household snapshot
This should map to the existing budget/finance source rather than becoming a separate budget shell.
$480
This pay cycle
Available after core bills
$190
Upcoming bills
Due before next cycle
$120
Grocery room
Available for shopping this week
This pay cycle
The current cycle snapshot should stay simple and readable, not overloaded with categories.
StatusIn range
PressureModerate
NextWatch bills + groceries
Upcoming bills
These are the short-horizon obligations that constrain the rest of the cycle.
Due soonUtilities + internet
RiskNeeds visibility
NextProtect bill room
Grocery room
This is the amount the shopping flow should be able to reference directly.
LinkShopping list
StatusOkay for one main shop
NextWatch extras
This pay cycleCurrent source
existing source
Upcoming bills
Short-horizon bill visibility should come from the same money source so the page stays trustworthy.
Bills
existing source
Grocery room
Budget should clearly communicate what room exists for shopping decisions this cycle.
Shopping link
Future source
future source
Per-shop budget logging
Future source for connecting each shop back into the household budget view.
Shop log
future source
Shared costs / co-parent costs
Future expansion once the core household budget layer is stable.
Shared costs
future source
Alerts + pressure signals
Future warning layer for overspend, bill collisions, or low grocery room.
Alerts
Prototype placeholder only
placeholder only
Visual budget cards
Prototype-only display state for testing hierarchy before live figures are connected.
Layout test
interactive next
Tap-through money tiles
Next interactive step could be tapping a bill or budget tile to reveal more context.
Interactive next
placeholder only
Planning notes
Temporary commentary while the real budget source boundaries are being finalised.
Prototype only
Home
This should hold practical household admin: maintenance, records, appliance info, home tasks, and other operational home data that should not be scattered across notes and tasks.
Maintenance
Repairs + jobs
Records
Home documents
Appliances
Reference info
Car / pets
Secondary ops
Future source
future source
Maintenance log
Track home repairs, overdue jobs, and maintenance history in one place.
Repairs
future source
Home records
Lease, appliance details, utility info, and practical home records should live here instead of random notes.
Records
future source
Car / pets
These likely belong here under the operational home umbrella rather than being split elsewhere.
CarPets
Prototype placeholder only
placeholder only
Home dashboard cards
Display-only layout testing while real home/admin sources are still being decided.
Layout test
interactive next
Tap-through records
Next interactive step could be opening maintenance or appliance records from compact cards.
Interactive next