Why we built Meosu native (and skipped Electron)

Dictation is not an app you visit. It’s a layer that sits between your intent and the text fields where you work across your Mac — which means it lives in the hot path of everything you do. A hotkey that starts capture a beat late, an overlay that janks, an idle process that chews battery in the background: each one taxes every single sentence you speak.

That’s the whole argument for native, and it’s why Meosu has a hard rule: no Electron, no Chromium, no Node runtime anywhere near the hotkey, audio, or insertion path.

What native buys you, concretely

Capture starts when your finger does. Meosu listens for its shortcut with a low-level event tap and opens the microphone immediately. There’s no JavaScript event loop between your keypress and the first audio frame.

Insertion is a system conversation, not a universal promise. Meosu tries safe direct insertion in the field you chose. When the field does not allow it, Meosu copies the result to the clipboard so you can paste without dictating again. App behavior can vary.

The overlay is a real window. The dictation HUD is a non-activating native panel — it never steals focus from the field you’re dictating into. That single property is surprisingly hard to fake in a cross-platform shell.

Idle means idle. A menu bar agent written in Swift can afford to be genuinely quiet when you’re not using it. Your battery shouldn’t pay rent for an app that’s waiting for a keypress.

What it costs us

Being native is slower to build. Every view is written twice as carefully, and there’s no shared web codebase to amortize across platforms — which is why Meosu is a Mac app first, not a five-platform launch. We think the trade is right: dictation is a tool you invoke hundreds of times a day, and tools in the hot path earn their keep with reliability, not feature matrices.

The details are the product

The same philosophy shows up in smaller places: a bespoke icon set drawn to one geometric grammar, so no glyph looks borrowed. Progress metrics that calibrate against your actual typing speed instead of a flattering default. A “scratch that” that reverses exactly the words Meosu inserted — verified by range, not by guesswork.

None of this is visible in a feature table. All of it is visible at the end of a workday.