Keeping a listening queue tidy: folders, shows, duplicates and notifications in WeDispatch Radio
Turning documents into audio is the easy part. Finding them a month later, never paying twice for the same text, and never showing a sensitive title on a locked screen is harder. What WeDispatch Radio actually does, rule by rule.
Any app that turns documents into audio has a problem you do not notice in week one. At first the list fits on a screen: a couple of memos, a report, an article. A month later it mixes committee PDFs, pasted notes, articles from a partner publication and long documents split into episodes. That is when people start re-uploading a text they already had, scrolling for a half-remembered title, or keeping the app open to see whether a file is ready yet.
We have already described what WeDispatch Radio is: a private listening queue for customer accounts that reads pasted text, PDFs and article addresses aloud. This post covers what comes after, the parts of the app that keep that queue usable over time, described from what is actually implemented rather than from a roadmap.
Shows, the way podcast apps do it
On a phone, Radio behaves like a podcast app. Audio is not a flat list. It is grouped into shows, the way episodes sit under a podcast's name:
- one show per source: the website a document was added from, plus one for the articles the account publishes itself;
- "My documents" for pasted text and PDFs that have neither a source site nor a folder;
- one show per series: a long document split into roughly thirty-minute episodes is a show of its own;
- "Today's briefing", as soon as an article has its spoken summary;
- one show per folder, once you create one.
The home screen offers what you would expect from a listening app: a "Resume" card for the episode you started (after more than five seconds, and not if you were nearly done), a "New episodes" shelf, and a "Play the new ones" button on each show's page. Each cover shows two initials and a colour that stays the same for the same show. On a desktop nothing changes; the list stays a list.
Folders: suggested for you, never published
When you add a document, the add sheet suggests a folder. For an article added by its address, the suggestion is the folder where you already keep the most documents from that site, with the most recently used one winning a tie. For pasted text or a PDF, nothing is suggested, because there is no source site to infer from.
A few rules are enforced in code rather than left to judgement:
- A folder name is 1 to 60 characters. Anything longer is rejected, never silently truncated, since the folder would otherwise not carry the name you typed.
- "My documents" is not a folder you can create. Typing it means "no folder", which avoids ending up with two of them.
- A document can be moved between folders from its menu.
- A personal folder name never appears on the account's public podcast artwork, nor in the sections offered on other screens of the account. A folder called "Smith litigation" stays between you and your phone.
Duplicates: flagged before you pay
This is the rule that saves credits. When you submit a text, Radio checks whether it is already in your library and ready to play. If it is, you are told before anything is produced, with two options: "Listen", which costs nothing, or "Create anyway".
Duplicates are detected by content, not by address, for two reasons. The address of a personal document is deliberately not kept. And an article that moves or gets republished changes address without changing text. So Radio compares a fingerprint of the text, computed the same way as at upload time.
Only your own documents are compared. A colleague's document on the same account is never offered, even with identical text: the database query filters it out, and the deciding module filters again behind it. "Listen" is only offered for audio that is genuinely ready, because "listening costs nothing" has to be true at the moment we say it. If you do choose to recreate, the credit estimate is shown before you start.
Notifications: one, and discreet
A long document takes several minutes to produce. Instead of keeping the app open, you can turn on notifications from Radio's settings. The choices we made:
- One notification per document, when all of it is ready, not one per episode. A six-episode report does not buzz six times.
- Failures are reported too, with a prompt to open Radio and try again.
- A personal document's title is never shown. People read locked screens over your shoulder, and a title can be sensitive. The text is neutral: "Your document is ready to listen to."
- For an article the account publishes, the notification includes its title, since it is public anyway, once per article and at the moment it actually goes live (immediately, at its scheduled time or after approval).
Notifications can be switched off from the same menu, and they stop when you sign out. On iPhone they require the app to be installed on the home screen, which is a platform rule rather than our preference. The same platform shapes background playback, covered in our post on listening with the screen locked.
What Radio does not do
A private document is never stored offline on the phone; offline downloads are limited to published articles. Radio does not fetch and copy a third-party article from its address either, except from partner publications; for anything else you paste text you have the rights to. And none of this replaces a real document management system. It is a listening queue, organised so that you can find what you meant to hear.
The voices that read these documents, and how they handle French, are described on our French text-to-speech page. The feature overview lives on the WeDispatch Radio page.
Give your articles a voice with WeDispatch
This blog is itself voiced by WeDispatch. Curious how it sounds on your content?
Book a demo