Rebuilding the desktop platform
Platform owner for the desktop app: the audio engine, the transcription socket, the release process, and the telemetry loop that decides what we build next.
The Problem
A founding-stage desktop app has to be dependable before it can be clever. That means a real audio engine, a transcription pipeline that survives bad networks, an architecture the team can keep building on, and a way to turn production signal into the right work in the right order.
What We Built
Took platform lead and rebuilt the desktop app from the building blocks up: reworked the audio engine, built a resilient transcription socket that holds through flaky connections, set the architecture, and wrote the conventions the team now builds against. Then closed the loop with an agentic workflow that pulls from Sentry, Amplitude, and other metrics, shapes it into candidate work, and feeds the backlog on a regular, reviewable cycle. User feedback runs through the same pipe: triaged into planned releases with the board and the delivery manager, so what ships is what actually moves stability and performance. Owns the whole release-management workflow too: separate tracks, fully automated with GitHub Actions and code signing, so a release ships from a single commit scoped to patches or minors, or a one-off workflow run.