HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
MarshallOfSound
Google-Play-Music-Desktop-Player-UNOFFICIAL-
JavaScript2016–2022
MarshallOfSound / Google-Play-Music-Desktop-Player-UNOFFICIAL-

Google-Play-Music-Desktop-Player-UNOFFICIAL-

A beautiful cross platform Desktop Player for Google Play Music

Creative & MediaMobile & Desktop
Explore on GitHubRead Hacker News discussions
5Distinct people
6Mentions
0Explicit recommenders
8.2KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A beautiful cross platform Desktop Player for Google Play Music

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year6 dated mentions

Observed mentions: 2016-03-06 05:23:57 UTC to 2022-04-14 19:54:10 UTC.

0122016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2022

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC110
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC101
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC101
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC202
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101

What Hacker News says

6 sources
freedomben·Apr 14, 2022
IANAL but I've worked with some of them and I'd guess that isn't sufficient. My advice to avoid any negative attention from YT/Google (but again IANAL) would be to do two things: 1. Move the "this is an unofficial" disclaimer at the top and bold and/or italic it so it's totally unmissable. I would use the same approach as MarshallOfSound: https://github.com/MarshallOfSound/Google-Play-Music-Desktop... 2. Praise Youtube/Google for having such a great API that empowers and enables their users to get the most out of their subscription. Make sure to point out the (true) benefits that YT gets from having a library like this that is available but they don't have to maintain and promise nothing to.
In Youtube.js – full-featured wrapper around YouTube's private API
danShumway·Jan 29, 2020
> It is pretty much impossible to build a music UX that optimizes for all three of these user types This is a good argument for not tying music subscriptions to a specific client -- ie, allowing 3rd-party clients that are optimized for my specific user-type to freely hook into and stream from my Google Play Music subscription via an official API. The Google Play Music client is not optimized for users like me. I'm sure it was a lot of work to build, but I am not the target demographic of any of the interface decisions that have been made, and I curse the designers every time I open the app. So it's weird that, say, Shuttle, a music client that is optimized for me as a user, can't hook into my account or even download my purchased music. I don't mean to call out Google Music in specific, because while it doesn't have good public APIs, they
Read the rest
're at least consistent enough that alternative clients are being made on desktop.[0] But I do see this as a trend across a lot of SaaS services -- Netflix, Twitter, Facebook, Apple Music. People complain that the services aren't optimized for them, and designers will roll their eyes and say, "you can't optimize for everyone". And that's true. But who's fault is it that you have to optimize for everyone? Who's fault is it that you have to try and figure out how to balance a bunch of wildly diverse and often contradictory needs? There used to be really good alternative Twitter clients, and if Twitter wants to complain now that building one client for everyone is hard, I just can't muster the energy to feel sorry for them. Apple's whole shtick is trying to get everyone to use the same official apps, to have the same consistent, good experience. I'm not sympathetic to a company that deliberately puts themselves into that position and then complains, "optimizing for everyone at the same time is hard." [0]: https://github.com/MarshallOfSound/Google-Play-Music-Desktop...
In iOS 13's Music App Sucks
AdmiralAsshat·Aug 20, 2018
My first impressions of Flatpak have been positive, with a few caveats. As an end-user, I want my apps to be getting regular, automatic updates, which means it's vital to get them from some kind of official repo. I sympathize with the one-man developer who just wrote some cool little Electron app that he designed to be cross-platform and promptly gets bombarded by requests from his 10% Linux userbase that wants the app to be packaged for Debian/Ubuntu/Fedora/SuSE/Arch repos. I get it, I've been that annoying guy[0]. So to that end, packaging once as a Flatpak and working everywhere has been great. A handful of those pesky apps I used to have to regularly check for new RPM releases are now on flathub and I can update them automatically. With that said, flatpak support is still spotty. DNF doesn't support flatpak yet, so I had to install GN
Read the rest
OME Software on my Cinnamon DE just to be able to easily support and update them. There's also the issue of the greatly inflated installation sizes. I'm hopeful that support will get better soon now that it's finally at 1.0. [0]https://github.com/MarshallOfSound/Google-Play-Music-Desktop...
In Flatpak 1.0 Released, Ready for Prime Time

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.