What you need to know
- A teardown of the most recent APK shows groundwork for users to bring their own content to YouTube Music.
- Google Play Music has a 50,000 song limit currently.
- This discovery is just a hint of the feature coming in the future, no indication of when.
We've known for quite some time, nearly two years, that Google plans to bring nearly all of the features of Google Play Music to YouTube Music. Well, it seems that one of the most treasured features — user-uploaded content — may slowly be starting its way to the music service.
In a teardown YouTube Music APK version 3.47, 9to5Google found "introducer" strings that may be the starting layer for a specified partition in your account. Once the feature is live, it seems that you'll have a streaming tab for usage that we are already used to.
Then, there will be an added table that will be a "library" that will become the cloud-based holding area for your personally uploaded content. Hopefully, this will include content migrated over from Google Play Music. Though there is an existing "library" tab at the bottom, it may be retooled to include personal content. Also discovered is a new artists section along with a "subscriptions" page.
These features were promised long ago by Google when we first learned it was planning to make YouTube Music its primary music streaming app, so I guess this is better late than never.
About time. My main use for GPM is through my own songs. Without this I have no reason to switch.
Until Google fixes the playlist limit of 5000 tracks (which is the same limit as YouTube), YTM will be broken for me. Even the Liked Songs automatic playlist is limited to 5000 tracks. It will be nice once they let people upload their own content but Google needs to fix the playlist limit issue, that has been one thing that keeps me from using Spotify (their 10000 song limit is laughable).
Get the best of Android Central in in your inbox, every day!
Thank you for signing up to Android Central. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.