Why Murmr exists

I built Murmr because most dictation options I tried were cloud-focused, subscription-heavy, and overloaded with features I did not need.

This project did not start because output from existing tools was unusable. It started because I wanted a cheap, convenient way to capture speech and quickly paste a refined transcript into Claude, Codex, and everyday docs.

What I actually needed

The loop I care about is small:

• capture speech quickly
• clean the transcript
• paste it where I am already working

That is it.

Why local-first matters

Cloud-first products often introduced friction I did not want:

• recurring monthly costs for basic usage
• account and service complexity in the critical path
• unclear handling of everyday speech data

Murmr is designed around Apple-native frameworks and private iCloud sync so the core workflow can stay on-device. If your device can do the job, there is no reason to route routine speech through power-hungry datacenters.

Keep it simple

A lot of "bells and whistles" in this category feel clumsy in practice. They add UI clutter and cloud the core use case.

Murmr stays opinionated:

1. capture
2. clean
3. deliver

What comes next

Current beta work is reliability, polish, and better daily ergonomics.

No dramatic roadmap slides — just steady quality improvements based on real usage.