Openwhyd Roadmap

This document outlines the development plan from a high level and will be updated as progress is made towards Openwhyd version 2.0.

Everything contained in this document is in draft form and subject to change at any time and provided for information purposes only. The information is provided “as is” with no representations or warranties, express or implied.

A bit of context

Openwhyd is a free and independent platform that enables users to create playlists of songs from several music streaming sources (e.g. Youtube, Soundcloud, Bandcamp, Deezer…), to share them, and to discover hidden gems hand-picked by our community of music lovers.

The development of this platform started in 2012 by the Parisian start-up company Whyd. During summer of 2016, Whyd offered the platform to its community of users, in order to focus on the development of their new product. With their blessing, Adrien Joly took the responsibility of turning Whyd’s ex-product into an open-source project, re-baptised “Openwhyd.”

Today, Openwhyd is maintained by volunteers on Github, coordinated by Adrien Joly, and hosting bills are covered by donations from our users.

Read more about the story of Openwhyd.

Openwhyd v2.0

Opportunities for improvement

Some users and contributors expressed their frustration on a few recurring topics.


Many of those issues are caused by technical debt and vintage development practices from its start-up years (2012–2014).

Proposed vision for Openwhyd 2.0

For users, it’s important that Openwhyd becomes more attractive, easy and fun to use. From various mobile devices: iPhones, Android phones, and tablets. Music discovery should be made easier thanks to editorial content (e.g. blogs, interviews…), the possibility to join genre-centred groups, and/or personalised discovery features. (e.g. based on machine learning.) Also, why not think of a new brand identity!

Our partners (e.g. festivals, music venues, clubs and magazines that embed Openwhyd playlists onto their own website to publish their programme) would benefit from a better design and customisation options for our embedded player. We also imagine that some of our partners could contribute to sustaining Openwhyd financially, e.g. by providing a more seamless integration into their websites.

Proposed technical directions for Openwhyd 2.0

As suggested by Serdar: before starting to add new features and/or clients (e.g. Android app), we need to consolidate the foundations of the current version. (e.g. bug fixing, documentation, automated tests)

Here’s list of proposed directions to modernise Openwhyd’s technical architecture, and to ease contributions from developers who want to join our effort:

Proposed architecture and projects for Openwhyd 2.0

Here’s an overview of the resulting architecture:

openwhyd v2.0 architecture diagram

And here’s a diagram showing a wider range of projects to be worked on towards Openwhyd version 2.0:

openwhyd v2.0 projects

You’ll find information on how to contribute / support this effort, in the corresponding section of README.

Feel free to file issues on this repository if you have questions, concerns, or suggestions.

Openwhyd v1.0 (done)

Openwhyd used to be called “whyd” (hosted at, and was the main product of the start-up company that developed it between 2012 and 2015. Read more about the story of Openwhyd and the release of Openwhyd 1.0 (open-source).

For its transformation into an open-source project, Openwhyd’s technical infrastructure had to be reworked. Become more mature, robust and accessible to contributors.

To reach version 1.0, contributors have given dozens of hours of their spare time to:

Here’s the resulting architecture:

openwhyd v1.0 architecture diagram

Read more on the version release.