@Ixxtabb notifications are totally different things. Yes, there are interactive notifications but it's far from what the music control framework is or specifically Spotify control. On most watches, you will have customized interactive notifications (for example, from Spotify I get limited control options within notifications, from the Metronome app I get +5/-5 beats option etc.) but at the core, these are different things. This is a kind of workaround to use notifications to control apps (it's more like a "quick reply" type of action to the app) but it won't grant full on-demand control as it's not made for that purpose. Pixel Watch on the other hand has WearOS which is supported by a number of music service providers and allows storing its own music. My wife with her Galaxy Watch 5 (also WearOS) has a choice of many music apps and can store her own music on the watch (and there is a number of music player apps for WearOS, too) and Spotify support is full (with offline playback). I don't think killing music on Sense 2/Versa 4 will help sell Pixel Watch as WearOS already offers better music capabilities than any Fitbit ever did. If somebody wants a watch with Amazon Music, Spotify, YT Music, Deezer, Pandora and whatnot, then would simply pick a watch that offers it. I am very curious about what volume of users will jump onto Pixel Watch from Fitbit devices just for that feature. The bad taste left after removing features from Sense 2/Versa 4 will rather make customers move somewhere else where the same features are being offered. Logic tells me that Sense 2 should retain all the features of Sense and add slightly more and then Pixel Watch should build even stronger options (like offline Spotify, and better in-watch apps). So some users would ask: "do I need long battery life or I'm going to benefit more from more advanced features?". And for some users that would be a no-brainer if they wouldn't mind putting the watch on a charger often. Although, it might be Pixel Watch's battery life is too short even for such a user (make it 2-3 days like GW5 and it's sold). Maybe Google has no confidence in the new product so instead of acquiring new users try to migrate old users (who are already bound to the platform). This is all just speculating and I may be totally wrong (well, I was wrong some time ago thinking Google could improve Fitbit, I may be wrong now, too).
Business decisions made by Google/Fitbit are currently far beyond my comprehension. They seem illogical to me (and probably the majority of the users) but they may make sense for Google internally. Big companies plan months/years ahead. We asked to bring music back to Sense 2, but they are already further than that. They already know whether the music will be back on Sense 2 and know whether there's even going to be next Sense 3 and what features it's going to have (including any music support). This is how big companies work. If internally, there are no plans to bring music into current and future Fitbit products then they already know that and no feature suggestion or posting in the community forum may change it. The only thing that works is whether the product makes money or not and this is where customers have all the power.
Community Moderators ensure that conversations are friendly, factual, and on-topic. We're here to answer questions, escalate bugs, and make sure your voice is heard by the larger Fitbit team. Learn more
Fitbit Product Experts Alumni are retired members of the Fitbit Product Expert Program. Learn more
Best Answer
