​How to Make Music Seamless?

Imagine if there was only one API that powered the world of music.

App creators, web developers, and device makers have a lot of API's to install - one for each music streaming company (like Spotify), making for a lot of work; plus, user's rights are not transportable.   The 'Master API' can solve this; a single API is all that a developer would need!
​ 
Imagine an app creator.  He wants music in his app, so he installs the Spotify API. If a user is a paying customer of Spotify, then they have more rights and a better experience. ​ ​But the next user might be paying Apple music, and after that someone is a paid customer of Google music; and so on.  It's too many API's for the app creator to install; so he only installs the Spotify API.  The end result is that customers suffer; and music is not seamless.
​ 

---

Introducing 'The Master API': One API to Rule Them All

​Consider the 'Master API'.   This one API would be the only API the app creator needs to install; it would know how to talk to Spotify, Apple music, Google music, Tidal, and so on.   This saves a huge amount of work for the App creator, and every paying customer of a major music streaming service would have a more complete experience.  It would also simplify maintenance for the app creator, which helps a lot.

The Master API would then be used in apps, in websites, and in devices - allowing all of them to talk to every major music streaming service, in a standard way.  This is what would make music seamless!
​ 

URM = User Rights Management

This is based on our concept called URM, which stands for "User Rights Management".  Right now we have DRM (which stands for Digital Rights Management), a system that protects the copyrights and trademarks related to a digital work.   But what about the rights of users?   As a user moves through the ecosystem of apps, websites, and devices - his right should move along with him.  Those rights including whether he is a paying customer and at what level.   Respecting and streamlining users rights is the basis of how we can make music seamless in our world.
​ 

Data and Demographics

If one company were to create the Master API, they would enjoy other considerable benefits, including the collection of a huge amount of user data.  Right now Spotify for example knows only what their own users like, and Apple music knows only what their own users like, and so on - but the owner of the Master API would know potentially the likes and dislikes of everyone.  That opens up huge potential incomes sources to monetize those demographics - including more focused and effective ticket sales, and the creation of a new advertising network.

The Music Streaming Master API is just one of our concepts.  Upcoming blog articles will discuss:

• The Music industry, and the need for sharing customer demographics
• A big M&A opportunity right now in this market
• Our URL MusicStreaming.com is the ideal way to promote your brand on social media
• UI (User Interface) review of various music streaming services
• Why Higher Quality music is important, and who is helping (and how is not)

We have been discussing the Master API ideas privately with a few folks and then decided to just share these ideas by posting the concepts publically on our website, to foster discussion and spur innovation.

The world needs the Master API.    Who will create it?