What exists today

Max is a prototype, not finished consumer hardware. We're building the useful parts first and letting real use decide what the final device needs to become.

The first test

Can someone open the Max app, tap one enormous FIND MAX button and hear or see the walker from another room?

That's the first thing we're building properly. The app, backend and device behaviour are being tested in software first, then on a Raspberry Pi with a real speaker and light, then in Dad's actual walker.

The better test

Can someone call “Max, where are ya?” and hear “Over here” from the walker without having to think about the technology underneath it?

Voice only matters if it is reliable enough to make Max simpler. The big phone button and push-to-talk stay as dependable fallbacks.

What we're building first

• One enormous Find Max control.
• A clear locator sound and visible light.
• Home Wi-Fi connectivity.
• A simple phone/PWA interface.
• Natural voice interaction after the button-driven path is reliable.
• Remote status and support for authorised family.

These are build priorities, not a claim that every item is already complete.

What we're not pretending to know yet

Final enclosure, final battery system, final microphone hardware, final cellular hardware, final pricing and final availability all depend on what we learn from the real prototype.

The concept images and video show the experience we're building. They are not photographs of finished shipping hardware.

Why build it this way?

Because the walker is the point. We can design a beautiful enclosure now and discover later that the speaker points the wrong way, the microphone gets buried under shopping, the battery is annoying to charge, or nobody uses half the features. It's cheaper and more useful to find that out with the real walker first.

Build it. Put it on the walker. See what gets used. Keep the useful bits.

We'll email when there's something worth showing.