What does #devstr think are best practices for nostr app discovery?

cc nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z nostr:npub16c0nh3dnadzqpm76uctf5hqhe2lny344zsmpm6feee9p5rdxaa9q586nvr nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 nostr:npub1g53mukxnjkcmr94fhryzkqutdz2ukq4ks0gvy5af25rgmwsl4ngq43drvk

Reply to this note

Please Login to reply.

Discussion

#YESTR

How about discoverability *in app* (amethyst, iris, primal web etc)

As simple as searching for kind 32267 (software applications)

Thinking we should have a "supported NIP" tag in there

What does this mean and how does it look like to the non-dev non-technical nostr app user?

Probably alongside other recommendations.

Next to notes you can have recommended notes, profiles, apps and other stuff

Does NIP-89 still work? This is a bad way to go because it assumes that discovery is made when you can't read that event or find something better. Looking at the client tag seems like the only option

Depends on what you mean by “app discovery”; what’s the context?

Imagine I am a non-dev non-technical beginner nostr app user who is enjoying a single app.

I am familiar with and used to the one app to one network pattern (x, tiktok, linkedin etc).

I may or may not have heard that there are other nostr apps that can do some of the same things, some things better, and some things worse than my main nostr app. (Many apps one network is a foreign, and uncertain concept for me.)

I would like to see in my main app in the people I interact with who is using which app with useful context, so that I can go on a nostr app discovery and experimentation journey.

I am interested to find apps that complement what my main app does.

In app, how do I know where to start with this discovery and exploration process?

I wouldn't asks devs but maybe #marketingstr?

#induecourse