I am approaching the problem from a very different perspective; instead of building a superapp I’m betting on making the protocol incredibly interoperable; the superapp route was always going to be possible but I think it ultimately undermines the whole point of nostr.
What I want is a flourishing ecosystem of apps that tightly integrate with each other without ever having to know of each other; there’s a reason I wrote NIP-31 (display unhandled events), NIP-89 (handle unknown events), NIP-90 (DVMs), NIP-60 (interoperable wallets)
I didn’t continue the work on Honeypot at the expense of Olas; I am finishing that work BECAUSE Olas, and Highlighter REQUIRE it.
Maybe I’m completely wrong but I think an extremely composable ecosystem is the only way that this can possibly ever work in the long run; much like outbox (or something like it) is required for nostr to work in the long run.
I fully agree. Having one application complement and help build the overall puzzle can be very powerful once all of the tools are available.
Thread collapsed
I agree with this take. I think we scare people talking about nostr because they get overwhelmed by all the info (not everyone is a freaky who likes rabbit holes).. but it’s easier to bring them by one “app” that fits their need. Once they get into the ecosystem we can introduce more and more clients/ use cases.
Thread collapsed
Totally agree! Interoperability is such a important thing. You've seen my Nostr for Business deck and one huge inspiration to start working on it was the fact that all SAAS business apps like Slack, Notion,... are trying to be this huge superapp. The problem is that the experience is getting worse as they are adding more and more features.
Having small dedicated apps that are exceling in the small niche and are seamlessly interoperable with other apps is the way to go.
Thread collapsed
This is the future I want
10,000x micro apps
Thread collapsed