Interoperability is required for nostr victory.

What I struggle with is the experience of 10 different kinds requiring 10 AppStore app downloads and installs.

I’m not making the case for nostr-wechat (I think).

Without being an engineer or a designer, it seems that one/few apps + tens of PWAs is the only sustainable solution to NIP-89 and interoperability.

How wrong is this nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft

Reply to this note

Please Login to reply.

Discussion

Why do you struggle with this? What's the problem you see with this?

There will only be more kinds and more people embedding these kinds in other kinds. Applications will cluster around certain use cases, and thus kinds, and for 80% of the content users can stay in the app. But of all apps will have the occasional kind they don't support.

Yes, agree on more and more kinds.

This is the pretext to my thought and question: what is the resistance/how likely is someone to install an app based on a recommendation from another app?

I see a risk of user drop off here.

Installation of an app seems a big ask.

Thus my question if PWAs might interoperate more easily in a many kind world.

This is where Nostr is sooooo beautiful to me.

If your social graph doesn't think it's worth it to install an app for this, then mostly PWA's will be shown as suggestions.

If however, the number one app suggested is, let's say, and Android Reading app and I see that my Reading group friends all use this. I'm going to be veeeery incentivised to check it out.

Love this view. Social incentives built in as a motivator.

Maybe it’s a non-problem, or perhaps an apportunity, as you suggest. Thanks for sharing 💪