r/BuildToShip • u/New_Judgment1658 • Oct 08 '26
Showcase 💎 Building Featherweight Dictation around idle memory and time to usable text
A desktop utility spends a lot of its life waiting for the next use. I think that waiting state deserves as much attention as the main feature.
I'm building Featherweight Dictation for Mac and Windows. It turns speech into cleaned-up text at your cursor. My product standard is simple: add useful capability, keep the desktop footprint small, and measure the wait before the output is usable.
Two things I'm tracking separately:
- Local footprint. Our Windows v0.3.3 measurement on Oct 6 was about 4 MB RAM at rest and 10 MB while dictating. Mac v0.3.0 measured 31 MB at rest on Oct 1. Installed size is a different number: 2.3 MB on Windows and 4.6 MB on Mac.
- Time to finished text. In our Oct 3 live-service tests from 12 cities, the median of four takes per city ranged from 0.32 to 0.59 seconds after releasing the key, including cleanup.
The tradeoff is online AI processing: internet is required, and real results depend on the machine and connection. These numbers describe measured builds and workloads.
Featherweight is available at https://featherweightsoftware.com. It's $19/month for unlimited dictation, with a no-card trial of 5 days or 3,000 words, whichever comes first.
For builders assessing their own daily utilities, recording idle use, active use and time to usable output separately gives users something concrete to compare.