Clutch Developer
NO
Book a call

Alexander: an audio app where the writing comes first

Client work with L+R. Original audio from award-winning writers and performers — which puts the entire engineering burden on playback that never loses your place.

Alexander publishes original audio features — roughly an hour each, on culture, science, crime, love and death — narrated by actors and chosen by editors rather than by an algorithm. New pieces land every couple of weeks. You can read the text or listen to it, and move between the two. There are no ads. The store listing credits award-winning writers and performers, and the app has been featured in the Financial Times, Forbes and The Washington Post.

Client work. Clutch Developer does mobile engineering on this app as part of the team at L+R in New York. The app belongs to Alexander Technology and Media.

App Store

What the app does

  • A curated library — series, single features and games, browsable by writer, narrator or theme.
  • Text and audio together, so you can switch format without losing your place.
  • Offline listening, downloaded ahead of a commute or a flight.
  • A personal list of saved and downloaded titles.
  • "Original audiobooks & games by award-winning writers and performers" — the library grid
  • "Narrated by your favourite actors" — browsing narrators, writers and series
  • "Listen to stories you can't find anywhere else" — the player mid-feature
  • "Growing collection" — My List with downloaded titles
Skjermbilder fra App Store-siden.

The hard part

Audio playback looks like a solved problem right up until you look at how people actually listen. An hour-long feature is not consumed in one sitting. It is consumed on a commute, in a kitchen, at the gym, over four days, on a phone that is also taking calls, connecting to car stereos and Bluetooth headphones, and being killed by the OS in the background.

Every one of those is a place to lose someone's position. Background playback has to survive the app being suspended. Position has to be written often enough that a hard kill costs seconds, not the whole session. Lock-screen and car controls have to show the right title and respond correctly to a steering-wheel button. Route changes — headphones out, car off — need the platform-correct response, which is usually pause, not carry on out loud.

Offline adds a second state machine on top. A download can be partial, stale, or interrupted, and the library has to be honest about which. And keeping text and audio in step means the position is not one number — it is a position in two representations of the same work that have to agree when you switch.

None of this is glamorous, and all of it is what people mean when they say an audio app feels good.

What that demands

  • A real background audio session, configured for the platform rather than bolted on.
  • Frequent, cheap position persistence — assume the process dies without warning.
  • Correct lock-screen, CarPlay and remote-control metadata and commands.
  • Download management with honest states: queued, partial, complete, stale.
  • Text and audio positions that stay reconciled across a format switch.

If your product is long-form audio, this is where the budget goes. Not the player screen — the twelve ways a listening session gets interrupted.