The list is how
the house talks.
You remember something while you’re doing something else. Milk. The laundry. A call that needs making. If the other person isn’t there, that thought still needs somewhere to go.
I wanted a shared list my partner could add to easily, ideally by voice, without needing me there to make it work. The test is whether both of us actually use it.
That’s why getting a thought down matters so much. A mixed request shouldn’t become three little forms to fill out. Get it captured, then help it find the right place.
How long does
it actually take?
The other starting point was time. I might have half an hour before I need to leave, but spend it waiting instead of doing something that would fit.
A job can feel bigger than it is. Six minutes to fold clothes is a much smaller thing to start than “deal with the laundry.” Seeing a time beside the next step makes the decision easier: that chore fits, so I can just do it. I wanted easy access to that number, without planning a perfect day.
That gives WAM a fairly strict rule: don’t invent the time. Record completed runs, show where the number comes from, and leave a blank when the answer isn’t known.
Explore the time example ↗The washer doesn’t
need watching.
Starting the laundry is one job. Remembering to move it later is another. It’s easy to move on to something else and forget what’s still waiting.
The useful screen puts those things in perspective: what needs hands-on work, what a machine is doing by itself, and the open stretch in between. A timer should help bring you back when it’s ready.
Calls and awkward one-offs need their own space, too. Longer term, I want the useful details beside them: the contact, the opening hours, the thing you need before you can begin. That preparation is still a direction for the product.
Why it started
on glasses.
The appeal is having the next useful thing in view without taking out a phone. Glance at the step, see what’s waiting, and get back to it.
I also want to be present with the people around me, rather than busy running a device. The system should make that easier. The glasses are one display for WAM; the household and its data don’t live inside the lenses.
A phone needs to stand on its own. Glasses are optional.
The rules come
from using it.
I set the product direction and make the interaction and system decisions. Claude and Codex help implement them. Testing it in the household and on the hardware is what tells us whether those decisions were any good.
Repeatable jobs should have clear rules. Models can help where interpretation is useful. The result should take less effort to use, and be clear enough to trust when something goes wrong.
WAM Home now has working lists, tasks, routines, step clocks, learned times, capture history and Undo in development. Getting it ready for other households means checking the whole experience, not just adding another feature.