Sense more. Share nothing.

SenseBridge is a free, open-source iPhone app that translates a blind or low-vision person's surroundings into clear spoken information — processed entirely on the device, so the camera and your surroundings never leave your phone.

SenseBridge is in open development and not yet available to download. You can follow the build on GitHub today.

If you are hearing this page rather than seeing it: the artwork here shows a signal traveling from a phone's camera, across a stylized bridge, and arriving as a spoken sentence — the same journey this page describes.

Follow progress on GitHub

Built like its name

SenseBridge exists to connect two things: a camera's raw signal, and the plain sentence a person is trying to hear. Everything between them — perception, reasoning, rendering — is the span of that bridge, assembled entirely on your phone.

No cloud crossing. No account gate. Just the shortest path from sensing to understanding.

The whole system is the phone in your pocket

No extra hardware, no cloud. SenseBridge is being built to run entirely on the iPhone's own sensors and silicon — here is how each part carries the signal.

Diagram: an iPhone drawn as a wireframe pulls apart into three layers. The camera and LiDAR scanner at the back capture the scene. The Neural Engine in the middle runs perception and reasoning models on-device. The speaker and Taptic Engine at the front turn understanding into speech and gentle haptics.

01 · SENSING

Camera + LiDAR

Light and depth enter here. The camera and LiDAR scanner sample the scene's shape so the app has something truthful to describe. In the architecture this is the SensingSource seam — the only door the world comes in through.

02 · REASONING

Neural Engine

On-device models turn pixels and depth into hedged, plain-language description. Perception always runs on the phone's own silicon; reasoning does too by default, with an opt-in setting to use your own cloud or self-hosted AI instead — off until you turn it on.

03 · RENDERING

Speaker + Taptic Engine

What the phone understands comes back as speech and gentle haptics — the RenderTarget seam. Always phrased as awareness, never as a promise of safety.

What it does today

Five capabilities, all running entirely on the phone.

  • Reads printed text and documents aloud.
  • Identifies common objects and surfaces.
  • Describes a scene in a natural sentence.
  • Gives cautious obstacle awareness using LiDAR — never navigation.
  • Announces important sound events nearby.

Private by architecture, not by policy

There is no backend, no account system, and no telemetry by default. Perception and reasoning run on-device; nothing about your surroundings leaves your phone without your explicit, revocable consent.

A privacy policy can change. An architecture with no server cannot.

Built the way it asks to be judged

This site is built screen-reader-first, to the same standard the app promises: semantic structure, every control labeled, full keyboard support, WCAG 2.2 AA. If you use VoiceOver or NVDA, this page should already feel like home.

Prefer to listen? This page can read itself aloud.

A future direction — not a product

Where the bridge could go next

SenseBridge is being built for the phone first. But the same on-device pipeline — sense, reason, render — could one day ride on lighter hardware, closer to the senses it serves.

Wearables like camera glasses could let the same hedged, private descriptions arrive hands-free. Nothing about that future is promised; the protocol seams are simply being designed so it stays possible.

Illustration: a pair of glasses drawn as a translucent wireframe rotates slowly. Every few seconds, a small point of blue light travels the frame — down one temple, around its lens, across the bridge, around the other lens, and down the far temple — warming to amber as it arrives.

Developed in the open

Everything substantive you just read is verifiable: the code, the architecture decisions, and the distance still to go are all public. If SenseBridge earned your interest, the way to act on it today is to watch the build happen.

Watch the build on GitHub