Made With Care: An Indie Voice Typing App vs Big Tech

I test a lot of products for work. Startups, enterprise SaaS, indie projects. Over the years I've developed one marker for "real" products: the maker uses it themselves every day.

That sounds banal, but it's surprisingly rare. Most SaaS startups build for an audience they don't belong to. Marketplaces are built by people who don't shop on them. AI tools are made by developers who don't use them in their own work.

Commander Flow is the opposite case. And you can feel it from the first minutes.

How it shows in the product

Minimalism. You install the app — and it just works. No ten-screen onboarding wizard, no popup recommendations, no in-product ads, no "upgrade to Pro" notifications. There's an icon in the tray and a compact menu. That's it. Anything that doesn't help you work with text is absent. That's a rare discipline in a world of AI apps that love to wave their capabilities in your face.

Default hotkey: Caps Lock. Brilliantly simple. It's the most rarely used key on the keyboard, and it's on every keyboard in the world. No two- or three-key combos to clamp down with your fingers. One finger. One key. Any keyboard — standard, laptop, ergonomic, mini. If for some reason that hotkey is inconvenient, it's reassignable to anything else in one click.

Code written close to the metal. No wrappers around wrappers around wrappers — the thing that usually turns an app into a sluggard. Instead: native system calls where possible; direct CPU and GPU usage where it speeds things up. No middlemen between your hardware and the model. You can see it with the naked eye — the app reacts instantly, doesn't wait, doesn't hang.

Perfectionist-grade optimization. You can tell each unnecessary millisecond of latency was personally unbearable to someone. And that someone removed it. I'm not a developer; I can't judge technically — but I've met developers, and I know what products look like when optimization was abandoned.

"Good products are built by people who need that product more than anyone in the world."

A direct line to the developer. It works.

The Commander Flow menu has a "Report a problem" item. Open it, and there's a window where you can write the developer anything: a bug, a feature idea, weird behavior, an improvement suggestion. For modern consumer software, that alone is unusual.

And it works. Not as the boilerplate "thanks, our team will review" reply. As a real channel to the human writing the code. I personally tested it several times — described a problem, and shortly after received an update where the problem was fixed. Free. It just landed in the next release.

No "priority support" tier, no ticket numbers, no SaaS queue. Window → developer → fix → update. That's how all industries used to work, before big companies ate them. Here, it still works.

What this means for the user

Right after install, the app just works. No wizard, no account, no "pick a plan," no "we use cookies." Install, press Caps Lock, talk — text appears in the field. Simplicity that, in 2026, registers as rare.

Speed becomes apparent after a couple of days. Not "X percent faster," but "the response arrives before you have time to expect it." When an app uses hardware directly, with no architectural padding, waiting disappears — and you stop tolerating it in other programs.

And the most unusual part — the developer answers personally. Not the press team, not a support bot. The person writing the code. This used to be the norm, and is now nearly a luxury.

What I'd improve

Small team is the bottleneck for new platforms. I'd love a native macOS client right now (which I know is in the works). I'd love a Linux build. None of that is doable in parallel with current resources. The team picks priorities and does them well — but lateral expansion speed is limited.

Documentation is sparse in places. Normal state for a small team running fast on the product. Some things you figure out by trying. The minimalist UI compensates — there isn't much that isn't obvious — but readers who like reading everything sometimes feel the gap.

Direct contact with the author doesn't scale forever. Right now, while the product is small, the developer reads everything personally. When the user base grows by an order of magnitude, that channel will have to be distributed. As of April 2026, we're in this short window — worth using it.

Why I stayed

I don't stay with Commander Flow because it's "the best on the market" (although I think it is). I stay because the product is made with care. Every update solves a concrete pain of real people, not "a checkbox in a roadmap for investors."

That, to me, is the real meaning of "made with care" — not a marketing line, but the technical fact that the code is written by a person who personally needs it. Who also presses Caps Lock every morning to dictate their emails. Who also reads "Report a problem" and answers it. Who also optimizes every millisecond, because that millisecond was bothering them.

If you're on the fence about trying it — download. Use it for a week. You'll spot the same thoughtfulness in the details that I noticed.

This is software made by a person, for people. Not because of branding. Because it feels like the thing was built not for money but for the sake of working comfortably.

In 2026 that's rare, and worth holding onto.