Our player, in your build, with no dependency on our domain
Code to copy: an isolated web component, the same logic without any interface for your own rendering, an adapter that drives a player already present in your design system, and two reference implementations, iOS and Android.
You want your own player, in your colours, on your release cycle. But writing it properly takes weeks: synchronised highlighting, resume where you left off, reading comfort, keyboard accessibility, listening milestones. Those are the weeks nobody wants to spend twice.
Our player, in your build, with no dependency on our domain
You copy the files
They have no dependency and do not update themselves. You version them with your own, and change them if you want.
Your server builds a manifest
A JSON object built from our routes, with the audio address, duration, chapters and word-level timing. Your key stays with you: no file in the toolkit calls our API.
You choose your form
The web component for a complete interface, the bare logic if you write your own rendering, the adapter if you already have a player to drive.
No key in the browser
A repository control forbids any file in the toolkit from calling our API or carrying an authorisation header.
The weeks of polish included
Highlighting, chapters, resume, remembered speed, sticky bar, text size and contrast, keyboard shortcuts, screen-reader announcements.
Web, iOS and Android in agreement
The three implementations carry the same constants, and a control checks it: a mobile player that resumed differently from the web is a defect nobody reports and everybody feels.
An adapter, if you already have a player
It drives your existing markup without adding a line of style or creating an element. What you were missing was not the look, it was the logic.
Teams that want control of their rendering, native mobile apps, sites with an established design system, newsrooms that refuse any dependency on an external domain.
Ready to give your articles a voice?
Book a 30-minute demo: we set WeDispatch up with you, no complex setup.
How many days of development?
Three to five, including the server route that returns the manifest and the work of matching your colours. Mobile adds one to two days from the reference files.
What happens when you fix a defect?
Nothing on your side until you take the file again. That is the price of independence, and we write it down rather than let you discover it: changes are announced in the release notes.
Does listening measurement still work?
Yes. Progress milestones are sent on an open route, and your dashboard fills up just as it does with our player. Three fields are sent, and nothing that identifies a listener.
Can measurement be switched off?
Entirely, with one attribute. Another attribute redirects it to your own collection.