Augen (German for “eyes”) is a project concept I’ve been circling for a while: a visual question tool designed around one moment. A visually impaired person points their phone at something and needs to know, right now, what it is or what it says.
Every existing assistant gets in the way of that moment. You open an app, wait for it to load, maybe create an account, start a chat conversation, describe what you want, wait for a verbose answer. Each step is small friction. Stacked together, they make the tool useless exactly when it’s needed.
The idea
Augen is one screen. Camera, question, answer.
- Take a photo, or point the camera live.
- Ask by voice or text: “what does this say”, “is this the right medicine”, “what color is this”.
- Get a short answer. Immediately.
No chat history. No conversation context to manage. No account. Using it a hundred times a day should feel like glancing, not like texting.
For longer interactions there would be AugenChat, a companion for conversations that need context, reviewing a document, comparing labels, learning a room layout. But Augen proper stays deliberately dumb and fast. The fast tool must never inherit the slow tool’s weight.
Why now
This isn’t hypothetical demand. Visually impaired people already strap camera glasses to their heads and ask questions out loud. The Ray-Ban Meta glasses turned out to be an accidental accessibility device, and the community noticed before Meta did. The market is validating itself.
What doesn’t exist yet is an ecosystem that puts accessibility first instead of bolting it on:
- Open, so users aren’t locked into one vendor’s glasses and one vendor’s models.
- Local where possible, because medical information on a photo shouldn’t require an upload.
- Accessibility by default, not as an add-on. The settings exist for everyone, the interface assumes them, and “temporary” disability, a broken arm, a bright sun, a noisy street, stops being an edge case.
Status
This is a concept I’m shaping into a build. The core loop is small enough to prototype quickly: capture, one vision model, one question, one answer. The interesting work is in cutting every unnecessary millisecond and every unnecessary tap.
More as it takes form. If you work in accessibility or use these tools daily, I’d genuinely like to hear what breaks in your current workflow.
Written with AI assistance. I plan to rewrite it by hand.