NEXRADIO / RADIO AUTOMATION IN THE CLOUD

Your own listener app and website: what the listener sees and what the station gains

The stream is the product; the app and the website are the shop. What belongs in a good listener app, why the playlist should be public, and how a request travels from the phone into the clock.

What is in the app

A player that starts and keeps playing, even as the listener moves through the site. Now playing, with artwork, artist and title, and what comes next. The presenter on duty and the show. Making a request, with a name if you like. Today's playlist and earlier ones, per hour. Installable on the phone as an app, without an app store, with the station's own icon and colours.

Why the playlist must be public

Listeners search for 'what was that song at half past ten'. A public playlist per day and hour answers that question and is at the same time text that search engines can read: every title and artist you play becomes a page you can be found on. At NexRadio a service writes the played songs to static pages every hour with their own sitemap, so the archive persists even though the live API only looks twelve hours back.

The request

A request from the app arrives as an event. It is checked: does the song exist in the library, was it not just played, is it not nonsense. Then it lands in the next suitable slot of the current hour, and the AI presenter reads it with the requester's name. This is one of the few permitted exceptions to the rule that the clock decides everything: a listener may add something, provided it is within the hour and has a verifiable reason.

Website and app share the source

The station's website and the app read the same data as the transmitter: now playing, schedule, playlist, presenter. There is no second database that can lag. The site is generated from one file with colours, images and texts per language, and published with one command. Multilingual with us means separate pages per language, so the English page really is English for a search engine and not a Dutch page with a language button.

What the station gains

Measurable listeners, per moment and per stream. A channel to the listener that does not depend on an app store. Requests and reactions that really influence the programme. And a website that is found on the music you play, not only on your name.

Frequently asked questions

Does the app have to be in the App Store or Google Play?

No. The app is installable from the browser with its own icon and works on iPhone and Android. A store version is possible but not necessary.

Can the app be in several languages?

Yes. Website and app have separate pages per language; the listener chooses and the choice persists while listening.

Does the listener see what comes next?

Yes, the next song and the presenter on duty. Exactly what is shown is configurable per station.

Explore your radio automation.

Discover what NexRadio can do for your station in a personal demo.

Book a demo

A personal demo. No payment details required.