Living List
What the household needs. The current shared collection of things to buy.
Incubation chamber / Specimen 001
GroceryMaster
The household organism
The family shopping system that grew from chaos, notes and forgotten groceries into one living list.
Observation file / 001
It began as a grocery list.
Then another person needed the same list.
Then the list needed memory.
Then the pantry joined. Then previous purchases joined.
Then thousands of groceries needed names, icons and structure.
Eventually the list was no longer a list.
It had become a system.
The original problem was shared memory.
01 Origin
It started with forgetting things.
Milk. Bread. Something for dinner. The item somebody was definitely going to remember.
Household shopping is built from hundreds of tiny acts of memory, usually distributed among several people and several badly timed messages.
GroceryMaster began with one simple experiment: what if the list lived in one place for everyone? That was enough to start the mutation.
Household evidence 001-A
- Milk
- Bread
- Something for dinner
- The thing we forgot
One list. Multiple people. One changing state.
02 Experiment
What happens when the list remembers?
A shared list creates new questions. Who changed it? Has someone already bought it? Do we already have one? Didn’t we buy this last week?
Can the person in the supermarket see what changed at home? The experiment expanded. The list became shared state. Shared state became household memory.
Cloud-backed synchronisation. Shared household state. Real-world delays have existed.
How much of the repetitive mental work involved in household shopping can software quietly remember for the family?
Household workspace / iPadThe user should never have to understand the architecture to add milk.
Original app capture03 System
More than a checklist.
The list is the most visible surface. Behind it is a connected model of what the household needs, owns and buys again.
One household. One grocery state.
The user should never have to understand the architecture to add milk.
Shopping Mode
The list in motion. A focused context for physically shopping while household updates can propagate.
Pantry
What the household already has. Practical memory for imperfect shelves and real life.
Buy Again
What it keeps coming back for. Previous purchases reduce the work of starting again.
Groups
The people sharing the system. Household ownership instead of disconnected personal lists.
Catalogue
The vocabulary behind the interaction. Structured grocery items, aliases, categories and visual assets.
The catalogue wall
≈ 4,600grocery item definitions / associated assets
Names. Aliases. Categories. Visual memory.
English / Spanish / Simplified Chinese
Catalogue items and associated assets—not retail-integrated supermarket SKUs. Multilingual catalogue work does not imply universal localisation.Behind the metaphor
The actual specimen.
Original product captures. The interface stays intact.
P-02 / Diagnostic specimenCorrect eventually can feel wrong now.
P-04 / Diagnostic specimenThousands of items. Still no olives.
P-01 / Diagnostic specimenA shared list becomes shared state.
P-07 / Diagnostic specimenIdentity has to survive real life.
04 Problems
Real households are terrible databases.
Two people edit the same list. Someone loses signal. A device is reinstalled. A subscription is restored. A change arrives several seconds later than expected.
Those moments became the useful part of the experiment. Every failure exposed another assumption.
Assumptions
under review
under review
A shared list becomes shared state.
Two people can change the same household. Updates have to propagate without making the interface difficult to trust.
Correct eventually can feel wrong now.
A delay of several seconds becomes conspicuous when two people are actively shopping. Correctness and perceived responsiveness are different requirements.
Freshness has a cost.
Constantly asking whether anything has changed wastes work. Active shopping and an idle screen do not need the same behaviour.
Thousands of items. Still no olives.
Catalogue scale brought aliases, duplicates, missing essentials, icons and translations. Scale did not automatically produce completeness.
The App Store holds part of the truth.
Transactions, renewal, restoration and trial states challenged ordinary assumptions about what an account owns.
TestFlight is its own environment.
Sandbox behaviour, distribution restrictions and App Store state made release conditions part of the system.
Identity has to survive real life.
Reinstalls, new devices and expired sessions pushed authentication beyond the simple question of whether login works.
An intelligent catalogue can slow you down.
More choices can undermine the interaction the entire system is meant to protect: find an item, add it, leave.
Lab noteProblems are specimen data.
Pantry / iPadComplexity belongs to the machine. Groceries belong to the household.
Original app capture05 Solutions
Make the complexity disappear.
GroceryMaster grew considerably underneath. The interaction was not supposed to.
The person standing in the kitchen should still be able to think: we need milk. Tap. Done.
Everything required to make that state shared, persistent and useful belongs behind the glass.
Household interaction
We need milk.
Tap. Done.
Complexity belongs to the machine. Groceries belong to the household.The Living List
Model the list as shared household state so an item can have a life beyond a single tick.
Contextual Shopping Mode
Concentrate more active household synchronisation where it matters: while someone is physically shopping.
Pantry + Buy Again
Remember both what the household has now and what it has bought before.
Shared Groups
Make the household the owner of the grocery state, rather than isolating it on one person’s device.
Catalogue intelligence
Give everyday groceries a structured vocabulary of item definitions, visual assets, aliases and translated keys.
Less work while idle
Reserve frequent presence and freshness checks for the contexts where they provide practical value.
Renewable identity sessions
Let account access survive ordinary device and session changes more reliably.
StoreKit hardening
Investigate entitlements through Sandbox, TestFlight, restore and reinstall scenarios. Payment logic is distributed systems logic.
Backed by automated functional and UI testing. Release behaviour is investigated through real device, Sandbox and TestFlight conditions.
06 Evolution
A list. An organism. A system.
Seven meaningful mutations. Each changed what GroceryMaster could be.
- I
The List
One device. One memory.
Observe mutation
Move the household’s scattered memory into software.
A grocery list - II
First Sync
The list learns to exist in more than one place.
Observe mutation
Household state replaces local state. The first connection appears.
A shared list - III
The Household
People become part of the system.
Observe mutation
The grocery system belongs to the household rather than one device.
Groups and shared ownership - IV
Shopping Mode
The specimen leaves the kitchen.
Observe mutation
Planning and buying become distinct contexts. The Grocery Ninja appears.
A specialised shopping state - V
The Pantry Remembers
Past and present begin to connect.
Observe mutation
What do we have? What do we usually buy? The environment begins to remember.
Pantry + Buy Again - VI
Catalogue Intelligence
Thousands of grocery concepts acquire structure.
Observe mutation
The catalogue becomes a system in its own right.
A structured grocery catalogue - VII
Mission Ready
The experiment becomes a shipped product.
Observe mutation
The chamber opens. A native iPhone and iPad product enters real household life.
GroceryMaster 2.x
Current chamber state / 2.x
Shipped. Still evolving.
Living List, Shopping Mode, Pantry, Buy Again, Groups and catalogue intelligence now belong to one native iPhone and iPad system, with authenticated accounts, subscription entitlements and App Store distribution.