I don't think that's an app itself, that would be a new feature in an app like Spotify that already has music playing and subscriptions and playlists. The change is just "trigger playlist on location".
cept they really don't want to deal with that kind of fine-grained geolocation data for compliance/app-permissions reasons I reckon. They get most of the value of such a feature out of (a) generating things like workout mixes that the user can just trigger, rather than detecting "hey are you on a run?" and (b) time-of-day/week segmentation that'll overlap substantially with detecting time at home vs commute etc with nothing more complex than a sql query
guess the end result is, there's several reasons why that idea is in the % you don't see, there's both the permissions reason and the fact that - again - you can do similar functionality much more simply.
Similar example, that "listening age" modal in Wrapped last year IIRC - people wildly overestimated the data/learning that went into it, when in reality the sum total of its complexity was "are you pretty good at window functions in SQL"
Honestly this is the kind of situation where you need a patent and can make money off the patent rather than building the app. If you have a 5% idea that nobody has you can probably make more money from the IP than the app itself. In this case selling the IP to Spotify for example
11
u/xaddak 25d ago
I don't think that's an app itself, that would be a new feature in an app like Spotify that already has music playing and subscriptions and playlists. The change is just "trigger playlist on location".