I ship audio as plain MP3 files, not an app
I ship the output of my language tool as plain MP3 files, not as an app. Every other tool in this space wants to own playback — queue, streak, sync, recap — and I went the other way on purpose. Here is the reasoning, and the parts that actually cost me time. 1. The player already exists A file plays on the phone in your pocket, the car stereo, a 12-year-old MP3 player, a cheap Bluetooth speaker,…
This report explains why the creator of a language learning tool ships their output as plain MP3 files instead of developing a full app. There are several key reasons:
1. The player functionality already exists on most devices, so creating a separate audio player adds complexity without adding real value. This includes background audio permissions, media session controls, offline caching, sync conflicts, and app store review processes.
2. Predictable filenames are more useful than a library view. The creator uses zero-padded filenames that include the language pair and sentence index, which sorts properly on most players. This avoids the common issue of files sorting out of order in many apps.
3. Short pauses between sentences, roughly 350ms for the two languages and 900ms between sentences, greatly improves comprehension when listening in both languages. Not normalizing the loudness of each clip independently also helps maintain a consistent audio level.
4. Using simple ID3 tags (title, track, album, artist) in ID3v2.3 format eliminates many compatibility issues with different audio players. The filenames themselves carry the actual ordering information, making the system work across devices.
The creator emphasizes that once the audio files are created, the workflow remains fully inspectable and editable. They can re-cut chapters at different pause lengths later or even give the folder to someone else without any issues. The main focus is on providing a reliable, file-based format for language learning rather than building a complex app with many features.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.