Manual Fallback

Short answer

What it is

A fast manual logging path when voice is not practical.

Why it matters

It keeps the product reliable across real contexts instead of idealized ones.

When to use it

Quiet public places, privacy-sensitive moments, or when you want silent control.

Why it fits the promise

The goal is still to capture the habit before the moment passes.

Why voice-first needs fallback

A voice-first product fails if it assumes speech is always socially comfortable, private, or convenient. Real-life habit tracking happens in classrooms, offices, transit, bedrooms, and shared family spaces. Some of those moments need silence.

Manual fallback turns voice-first from a narrow demo into a real daily workflow.

What it solves

Manual fallback solves the gap between product philosophy and context. It lets the same low-friction capture promise hold even when the input method changes.

What it does not mean

It does not mean voice was a mistake. It means Spoke is designed around real-world capture, not ideology about one input method.

Where it connects

Manual fallback works best alongside voice logging, review-before-save, and recovery-friendly progress flows. Together they create a calmer capture system.