Glyph Interface

Glyph hardware gave Nothing a highly recognizable product identity, but there was no established interaction model for a rear-facing interface.

Unlike the main screen, it had limited resolution, no conventional touch interaction and only brief opportunities to communicate.

The challenge was not deciding what the hardware could display. It was defining what users genuinely needed when they were not looking at the screen.

Most system feedback depends on the display, sound or vibration. When the phone is face down, muted or placed at a distance, many system events become difficult to notice or understand.

We connected Glyph with core system events, translating calls, notifications, charging and device states into distinct combinations of light, rhythm and position.

The goal was not to repeat the screen, but to make essential system feedback perceivable beyond it.

Basic light feedback could tell users that something had happened, but it often could not explain whether the event still mattered or whether action was required.

If Glyph only provided momentary effects, its usefulness would remain limited after the initial novelty faded.

We expanded Glyph from event feedback into persistent, glanceable experiences that helped users understand progress, priority and remaining time.

The interface focused on answering simple questions—whether something was nearly complete, whether an important message was waiting, and whether the user needed to act.

Glyph originally worked mainly as a passive output surface. Users could receive information through light, but had limited reasons to actively enter and interact with the interface.

Without interactive content, the hardware risked being experienced only during occasional calls, notifications or demonstrations.

We introduced Glyph Toys as a lightweight interaction layer designed specifically for the rear surface.

Toys combined utilities, playful content and sensor-driven interactions, allowing users to actively explore Glyph without turning it into a conventional application screen.

If every Glyph experience depended on first-party development, the number of supported scenarios would remain limited and growth would be slow.

Third-party applications understood their own user journeys better, but lacked a consistent and controlled way to access Glyph hardware.

We opened selected Glyph capabilities through a developer kit, enabling third-party applications to integrate light-based feedback and experiences.

The SDK was designed not only as a technical interface, but as a product framework balancing openness, consistency, performance and user control.