We kept running into the same problem.
We’d be building something - an educational tool, a storytelling feature, whatever - and we’d need voice recording. Simple enough, right?
No. Not simple.
The MediaRecorder rabbit hole
First you deal with the MediaRecorder API. It works, mostly, but the browser inconsistencies are fun. Then you need a UI. Play, pause, stop, a waveform maybe? That’s a few days.
Then encoding. Storage. Playback on different devices. Error handling for when permissions get weird.
By the time you’re done, you’ve spent a couple weeks on something that wasn’t even the main feature.
We did this three times before we got annoyed enough to fix it.
What we built
44 is a set of web components. You drop a <fortyfour-recorder> tag in your HTML, and you get a recorder. Drop in <fortyfour-player>, you get a player.
One line of code. We handle the MediaRecorder stuff, the UI, the encoding, the storage, all of it.
<fortyfour-recorder></fortyfour-recorder>
That’s it. That’s the integration.
Who it’s for
If you’re building something that needs voice - a language learning app, oral history project, audio journaling, whatever - and you don’t want to spend two weeks on recording infrastructure, that’s what this is for.
We built it because we needed it. Figured other people might too.
Questions? [email protected]