or you team up with an artists and build a site for them. I built itdv.podtards.com for @The Doerfels.

THIS IS PURE TRUTH! 👂#listentousers 🙏 View quoted note →

What do they need?

Automatic splits! I haven't checked but I think you implemented it. Also, thisnwould be more a feature request/change but theres a lot of info avail within the rss feeds. When we upload an rss, your back end should be automatically pulling from those tags.

One thing that I think is important not to conflate is there are two distinct "users" when it comes to this music ecosystem who have drastically different needs. You have artists (content) and fans (consumers). Which one is your particular app targeting? Fans want ease of use. Easy to find the song they want or discover new music. It needs to be easy to zap (min clicks) and easy to set up (or better yet, not at all). But for the stickiness factor, sharing is vitally important. Share tracks share playlists share zap comments. Make it easy for other ppl to hear what youre hearing. Get the preview cards looking right. The app only grows if its easy for the next person to onboard. On the content side, you actually want some barrier to entry. Friction keeps a certain degree of slop out. That minimal amount of effort cuts out most the shit. Its a balance though, obviously dont make it hard on the users. The killer sauce in this ecosystem is interoperability. One change one update one new upload published in any one of the apps here should appear/publish everywhere all at once. Nostr obviously fixes a lot of this but the pipes are running via rss. The ones who can join the two will win.