WeDispatch 1.2.0: your client area, redrawn
Ten redesigned screens, navigation built around your working moments rather than our technical map, a new Distribution screen, and mobile finally done properly. A tour of version 1.2.0.
A client area ages like a desk: you put a feature down, then another, each in the place that made sense that day, and a year later you are opening three drawers to find one setting. Version 1.2.0 is a big tidy-up. Ten redesigned screens, navigation rebuilt around what you are doing rather than how the product is built, and a new screen for everything that leaves the player. Nothing you could do before has gone away — it is simply easier to find.
Navigation that follows your day
The menu used to list thirteen flat entries, in an order that owed more to the product's history than to yours. There are now five groups, named after the moment you open them: Monitor (where things stand), Create (my audio, editing it), The player on your site (how it looks, how it speaks), Setup (plugging it in, distributing it) and Account.
A few screens were renamed along the way, to say what they do rather than what they are: Statistics became Listening, Player became Appearance, Voice became Voice & delivery. During the transition the old name stays visible in grey beneath the new one, until the eye adjusts. And every old address redirects: if you had bookmarked a page, it still takes you to the right place.
Three screens merged into one
Fixing a pronunciation, pulling an audio quote out of an article, finding the exact second a word is spoken: three separate pages, when all three start from the same thing — audio you have already produced. They are now one screen, Edit & reuse, with three tabs. You pick the audio once, then do what you came to do.
In the same spirit, API keys have moved into Sites & setup. A key on its own means nothing: it exists to connect a site. Quick start, the WordPress plugin, the webhook and your keys therefore now live together, under site management.
A new screen: Distribution
The podcast feed, the morning playlist, the registration wall and translated editions had something in common that the navigation never said out loud: they are the four ways your audio leaves the player to go and live somewhere else. They sat scattered at the bottom of the Appearance page, between two colour settings. They now have their own screen, Distribution.
We took the opportunity to apply one simple rule, and stick to it: a setting lives in exactly one place. Review-before-publish, for instance, is now set only under Settings & team. Wherever something moved, the old page carries a pointer to its new address — you do not move the furniture without leaving a note.
Mobile, properly this time
A redesign that only exists on a large screen is not a redesign. On a phone, the right-hand context column kept its desktop width once it dropped below the main content: you got a narrow card stuck to the left, under text spanning the full page. It now takes the full width, as it should. The side menu no longer stays stuck in its hover state after a tap, and opens full screen.
Pricing you can actually read
The per-article price tapers: around one euro at low volumes, easing towards ninety cents as volume grows. That was already true, but you had to work it out. The Plan & billing screen has been rebuilt in two columns and now shows that scale exactly as it is applied, next to your real Stripe invoices and your current commitment. One single source for prices, in the product and on the public page: no stray figure contradicting another.
And the documentation follows
Last detail, and the one that wears you down most when it is wrong: the documentation and API reference still referred to screens by their old names. All of it has been gone through, in French and English. When the docs tell you where to change something, that is the name you will see on screen.
What comes next
This version is a foundation: a coherent client area that the next features can settle into without scattering again. What follows is about substance — showing more clearly everything the product can do, and turning your listening data into answers rather than charts. As always, everything goes through staging first, and we tell you here what changed.
Give your articles a voice with WeDispatch
This blog is itself voiced by WeDispatch. Curious how it sounds on your content?
Book a demo