Closed jamesf-hub closed 3 years ago
Hi, what do you mean by universal? As in on Windows and Linux machines too?
If cross-platform support is what you meant, the answer I have right now is "probably not unless it was widely requested."
The main reason why I think people will use Now Playing is because it's the only (to my knowledge) actively-maintained FOSS Spotify notifications service for the lacking macOS Spotify client. Windows seems to have working notifications and basic media buttons by default, and Linux seems to also have it working too.
If Spotify one day finally adds that feature into the mainline client, I will consider it again: the mini-player is a pretty nifty tool.
I believe they mean Universal app as in support for M1 and M1 Pro/ Max chips. Currently the app is only Intel compiled. Look here for more info
Ah, thanks @reece394. Indeed, I compiled the project on my 2019 machine. I think it'd be best if the app didn't need to use Rosetta 2 to run especially given its greater than average impact on battery life.
The unfortunate difficulty with this is comes with adding an autoupdater that doesn't require downloading a .dmg
file to Downloads
. When I do that, it needs to download the correct file depending on the architecture.
That's not very hard, but it'll still require some testing and reading on my end, so I'm planning it for v0.11.0.
What's even easier is building an arm64
build for v0.10.1 so I'll do that. Should be up in half an hour (I'll comment again once the lengthy sign and notarise process is over).
A Universal 2 build is expected to come in v0.11.0: once the user has downloaded and moved the .app
to their Applications/
folder, they will (hopefully) never need to visit the Releases page again.
See #13: a Universal 2 build will be added to releases from v0.11.0 from then on in along with an auto-updater.
A new arm64
version has been added to v0.10.1
.
I'm aware that users still on versions before v0.10.1 might accidentally download the .dmg
for the wrong architecture. That fact is going to speed up the v0.11.0 release, I think.
Going to close this in favour of #13 @applekillerbyjames. Feel free to reopen if I missed something.
Title.