The biggest problem I see right now is the first use experience. The first 15 minutes you use a product determines whether you continue using it or likely drop it forever.

When you just start #Nostr & you wanna see anything, all Relays have to be queried first, etc. At first, everything is empty.

Happens as well, when you delete the cache of the #Nostr app you use.

People are so used to instant access, it's probably a pretty big blocker to wait for Relays to finish loading the feed, especially in Global, basically like viewing an image in Internet Explorer during 2003.

Reply to this note

Please Login to reply.

Discussion

Could you help mange expectations by a pop up message that says "please hold while we're connecting relays and syncing data.... after that you can connect a wallet, make a post with #??? whatever... and start making friends....".

Something to pass the time and educate the user as to what's going on.

I don't get this comment. Connecting to the relay, setting up a subscription, and receiving data takes ~1s. Sounds like a client problem.

Nope, not a client problem. It depends on how you connect to the services, through which network & how many relays allow your requests to go through etc.

If it works well for you, you maybe don't have a lot of different connections & the servers are more available to you. I don't know.

Or I mean, you could define this as a "client problem", but if you do that, then nothing will ever get fixed, because every client configuration will be a "client problem" as in "not my problem" and the actual issue will persist.

Not every "client problem" is not "not your problem".

Sorry, notifications are still shit ;)

You're right for sure. I'm on a comfy European fibre connection righ now, so everything is butter-smooth. But even on a shitty 3G connection, it should be possible to request / download a few KB in 1-2 seconds (even with a ping of 500ms).

So unless you government is restricting access, either your client doesn't have enough, or good enough servers, or there's another issue in the client - caching or whatever.