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, and mpv on a laptop. That is the entire compatibility matrix, solved by not writing a player.
The moment you build a player, you inherit: background audio permissions, media session controls, offline caching, sync conflicts, and a store review process. For a tool whose job is "turn two texts into one audio track", none of that is the interesting part.
2. Predictable filenames beat a library view
The output for a chapter looks like this:
lesson-03/ 01-ja-en-0001.mp3 01-ja-en-0002.mp3 01-ja-en-0003.mp3 Zero-padded, language-pair in the name, sentence index last. Cheap players sort lexicographically, so 1, 10, 11, 2 is what you get without padding. Fixing that one detail removed the most common complaint I had with my own earlier attempts.
Folder depth matters too. Some car head units only browse two levels. Artist/Album/track is safe; courses/japanese/season-1/chapter-3/lesson-4/track is not.
3. Pauses are the product
Once sentence pairs exist, generating audio is the easy part. What makes a bilingual track unlistenable is silence: too much and you lose the sentence you just heard, too little and the transition feels like a cut.
I settled on roughly 350 ms between the two languages of a pair and 900 ms between pairs. Those two numbers do more for comprehension than any voice-quality tuning I tried.
Second lesson: do not normalize loudness per clip. Normalizing each sentence independently makes the two languages pump against each other. Measure the pair, apply one gain to both.
4. Tagging is where the bugs live
ID3v2.3 vs v2.4, UTF-16 vs Latin-1 for non-ASCII titles, players that ignore track but honour the filename, players that do the reverse. I ended up writing only title, track, album, and artist, all in ID3v2.3, and letting filenames carry the real ordering. Boring, and it works on everything I've tested.
What this buys you
Because the artifact is a file, the workflow stays inspectable. You can re-cut a chapter at a different pause length six months later without re-aligning anything, or drop the folder on a USB stick and hand it to someone. There is no account state to migrate.
I wrote the boring details up separately — file naming, folder depth and bitrate for bilingual MP3s on real devices — because that guide turned out to be more useful than any feature I shipped.
The upstream half, pairing a Japanese audiobook with its English edition and getting sentence-level alignment out of two texts that never segment the same way, is here: Japanese–English audiobook listening, line by line.
Where it breaks
Alignment on arbitrary prose. Dialogue-first matching covers maybe 70% of fiction; the long tail is a manual pass. Graded readers are fine, literary novels are not, and I have not found a general solution that doesn't involve a human reading the chapter.
If you've built something in this space, I'd rather hear about your segmentation failures than your UI — that's the part I'm still losing to.

