Our initial instinct was to seek to create a fully-functional media publishing system, with "conversational" as well as "broadcast" communication media. We proceeded to pare down the scope, in order to be able to deliver a coherent and usable product within the timeframes of the event. When deciding which elements to subtract, we converged towards the "audio-only" format, due to its lightweight and accessible nature (compared, for example, with video). After some UX research with some audio publishers (musicians, journalists, event production), we found a feasible use-case, to provide a way to offer anyone a simple audio channel for being able to broadcast audio to anyone on the planet with an internet-connected browser.

In terms of technology, we focussed heavily on the front-end UI, and the overall UX, while taking a practical approach to the back-end (using mature centralised technologies) in order to maximise progress. Decentralising this back-end can be relatively easily achieved, for publishing content (Livepeer) and also recording/distributing (Swarm).

Other evolutions can include:

• audience interaction - e.g. adding waku.org as a way to talk about the content being livestreamed
• optional addition of video, layered onto the audio
• ability for a listener to be "promoted" to be a participant, to contribute to the livestream.