Unsolicited feedback: If this were also offered as a web-based application I'd probably use it (sitting at my desk all day I don't want to use my mobile device for music). Maybe sell rotating ads or sponsorships (on screen but not in the audio stream, please!) to make some $.
That's exactly what is coming next for it! A fully-fledged web app. It's actually built using web tech so it's an easy port. Just need to rebuild some of the native bits for web (ohh I might get to use wasm!) but once that's done it should be good to go. Planning on pushing out in the next 2 weeks.
And yeah while I don't need to run ads on it at the moment, if the right sponsor wanted to work with me I'd be exceptionally happy to do so.
> Except for the limited commercial uses for Non-Streaming SDAs (set out below) commercial uses are not permitted for SDAs.
Their guidelines are super strict about using any music or artwork in specific ways. For instance, I'm pretty certain you need to display a Spotify logo any time you play music from Spotify, which I don't see on the player. And the player has rounded corners on the artwork.
> To comply with our licensing agreements, you must always attribute content from Spotify with the logo.
> Artwork must be kept in its original form. Don’t animate or distort it in any way. This includes applying overlays and blurring.
I'm not a lawyer so I'm sorry if I'm reading these incorrectly. I tried making an app using the Spotify API at one point and had it running but it got shot down a couple times for not displaying the Spotify icon. Good on you if your app is all set. I was always worried I was going to face the Spotify legal team with mine and gave up on it.
I only mention these because I do love the radio! Great mix of genres so far!
Radiant launched with a paid subscription model (like a dollar a month) Spotify shut it down, took away our API creds and left us in the lurch. Had to set it up again, with the subscription removed. That hurt because we had a good number of paying customers at that point.
But we moved to be compliant with their guidelines after that and I carried it on as a labour of love.
Now I'm actively looking at moving away from Spotify and on to my own data set and APIs that can match what Spotify has. I've built something like it before using the Cover Art Archive for the artwork, Acoustic/MusicBrainz for the metadata and custom logic built atop so I know it's possible.
Once I've done that I can start looking for sponsors.
There is always the possibility that if the userbase really scales up, Spotify would grant me a commercial license and allow me to commoditise the platform but I don't need that to happen really.
I made a Spotify powered app ( https://mergemusic.app ) and we didn't add any payment methods to comply with their terms.
Tried for months / years to get in touch with someone at Spotify who could discuss a commercial licence agreement, so the app could have a business model. Stonewalled.
Turns out Spotify instead of working with us, made their own version - Spotify Blend, launched 2 years after our app.
The thing that bugs me the most is Spotify is a member of https://appfairness.org which states
> App store gatekeepers have carefully crafted their mobile device ecosystems to eliminate competition and maximize their own control and profits, to the detriment of developers and consumers.
However Spotify's own App Store did exactly the behaviour they are complaining about.
I suspect it might be complicated by the fact that most of their content isn't owned by them but leased(?) from record labels, artists, podcasters, etc?
But I agree it seems like they use this API as a free launch pad for ideas, which seems morally or ethically questionable. Sorry to hear they might have ripped your idea.
I've got plans to build my own "open music API" that'll make whatever service you use just an adaptor that Rad can tap into. At the moment Radiant is very embedded in Spotify's API ecosystem due to a few key features none of the other services has.
Longer term thing sadly as this is very much my side deal but it'll get there.
Probably make that new API and dataset OSS as I want other devs to build cool stuff without being at the mercy of the streaming services.
Honestly, I think the value is in the DJ personalities. I'm trying to get away from sarcasm in my daily life as it makes me unhappy overall. Most evenings, I just kinda wanna listen to someone more positive like a dead head talk about music -- no offense, I just wanna look at the positive side of life for the years I have left.
That said, I would like to see even just a recommendation engine plug into YT Music, spotify, even hell, an nzb downloader. "You liked this song and band, you know you should try this band."
If you want something like this for a shop or store etc, ping me via rad@getradiant.app, we might be able to build something cool to fit that need (I've been toying with this idea for a while so it'd be nice to have a first user for it)
It was a native iOS app originally but now it's pure web (straight Svelte SPA, no UI framework) with native plugins.
I did it because I don't have the time to maintain for 3 platforms in parallel without one falling behind and I'm not a fan of React native personally. I spent a good chunk of time testing with much older hardware as a target to make sure performance wouldn't be a noticeable distraction for users and I'm happy with how it turned out :)
If you have more info on how you set up your Svelte project, I’d be interested in hearing! I recently rewrote my personal website from react into something much simpler with Svelte and am trying to figure out the best way to serve it on phones.
Very cool.