Nostr Web Client

Remixed nostr:npub1stemstrls4f5plqeqkeq43gtjhtycuqd9w25v5r5z5ygaq2n2sjsd6mul5 by trying to prototype their competitor.

Demo: https://cdn.satellite.earth/b144258f6c0795a4c65d1b56105f858dfad34888bb9b821fe9946926adcfe618.mov

Features:

👉 Player: probably n the roadmap already. Avoids me having to scroll back in the feed to pause songs 😉

👉 DVM algorithms: On the current Stemstr I can't filter my feed. Using profile list would be a start, but looking ahead even those filters will just be free DVM's.

👉 More than just Upload: nostr:npub1rlfaaaal29097arpaqflh7x98r8yyc075utazmar3g7kyzfr6wzszhyg5u shows the trend towards bots helping us create demo's from recorded audio or text prompts. This lowers the barrier for any user to become a creator on this app.

👉 More than just Download: On the current Stemstr "remix" actually means "download" and it's hard to keep track of the remix flow. If a download icon means "download", it lets you label the track, it automatically adds it to your local downloads feed and it proposes a payment for the producer (of which Stemstr can take a cut), I think the flow would be clearer. If on top of that, when you upload a track the app asks you whether this a Remix or an Original, it'd be even better. Also the filename should be displayed, so you're not surprised by what is downloading on desktop f.e.

👉 The download action is a very high signal one. I propose you use it. Status in the feed + letting users browse other users downloads on their profile page. Makes cool demo discovery a lot easier.

👉 Launch tracks: A way for finished collabs to be "officially" published on the Wavlake of the world.

👉 Cover Art: you were already on this and the marginal cost of adding/creating images is only going down. The UI should accomdate that, even for demos.

👉 Greyscale UI: less chaotic, room for images to breathe

👉 Show the Stack: A way to visually show that this track had predecessors

nostr:npub1yauhh489aefdkzsewe5vj2u68elzxlsln7nn5yxr34e3c22vljdqkn7h9m hope you get something out of this, Stemstr has a ton of potential. Figma here: nostr:npub1e2wk36e9vg8uw40phrrkkhc4tax8a9ken3fjcyy63vmdyz9aee2sk9el27" target="_blank" rel="noopener noreferrer" class="note-link">https://w3.do/3PAFF5Dp/tsl32Md2nostr:npub1e2wk36e9vg8uw40phrrkkhc4tax8a9ken3fjcyy63vmdyz9aee2sk9el27 #nostrdesign #stemstr #music

Rock 2y ago

nostr:npub149p5act9a5qm9p47elp8w8h3wpwn2d7s2xecw2ygnrxqp4wgsklq9g722q you’ve give me so much great food for thought here and if you ever find yourself wanting to properly contribute to the design in a more fundamental way or to help Stemstr work with the community to bring these experiences to life, I’d love to work with you to do so!

Some notes below :

Player is such a needed addition! It’s on the roadmap and something we’ve been designing, but it’s awesome to see a fresh approach!

Filtering the feed is a great idea. Would love to understand more about how DVMs can enable this. Discovery and feed management is a big problem to solve right now.

Love the nostr:npub1rlfaaaal29097arpaqflh7x98r8yyc075utazmar3g7kyzfr6wzszhyg5u integration! Bringing prompting into the experience is key to helping to create music more easily and to lower the barrier for who can be a creator.

I love the drawer that pops up on “download” action. It’s clean and organizes the journey in a very thoughtful manner.

Launched tracks is a very real need and this is a great way of handling this.

Cover art - yes, please. nostr:npub1stemstrls4f5plqeqkeq43gtjhtycuqd9w25v5r5z5ygaq2n2sjsd6mul5 needs to begin to express itself beyond the ears.

The stack is a great metaphor of the history of remixes a track has experienced.

Reply to this note

Please Login to reply.

Discussion

Niel Liesmons 2y ago

Haha damn, didn't expect you to like so many of these ideas! Great to hear that 🤗. I'm open to whatever can fit in the Opensats nostrdesign umbrella. And I prioritise exciting "Other Stuff" apps, which Stemstr definitely is imo.

The idea of DVM filtering would be to:

- for example, filter by Profile Lists (Following, My Bros, Everyone...) but to code it as DVM providing that service

- this doesn't change anything for the user regarding this feature. But it opens up the opportunity for literally anyone else to code up a different way of filtering the feed that then suddenly is available in your app without you doing anything.