How we used Slack as a backend
For our latest project, we used a rather unconventional content management system—Slack. Here’s what we did and why.
We recently built an enhanced live streaming experience for Red Bull Radio. (For context: we act as the service’s product team.) Their editors are now able to easily share real-time updates from events broadcast on the station, directly through Slack.
The experience launched last week, to coincide with this year’s Red Bull Culture Clash in Atlanta. Culture Clash is an action-packed event series that puts a spin on the traditional sound clash, derived from Jamaican dancehall culture. The musical competition is known for its spectacular surprise appearances and dubplate specials, recorded specifically for the night.
Like many other shows and festivals, the clash was broadcast live on Red Bull Radio. There is a lot happening at these shows, so the challenge was to create an enhanced audio experience that would be meaningful and entertaining for users listening online for multiple hours.
To keep listeners engaged, we introduced custom emoji reactions (airhorn, anyone?), a live chat, and a timeline. With the timeline, users received real-time updates throughout the event that paired with the broadcast. Rae Sremmurd jumping on…
