Subnostr

There may already be a term for this that I'm unaware of, but I'm naming it anyway.

Long-term user bias.

Many long-term users adjust to poor UX/UI over time and begin to think no issues exist. This becomes an issue for software that is relatively new and growing because new users are smacked with a massive amount of poor UX/UI all at once (it's been growing over time). The long-term biased users don't see the issues because they've lived with them for so long and had the chance to adjust over time.

That's what I'm seeing with Nostr clients.

"My client works perfectly."

"It's easy. Just do this and that in that and add this relay for that and make sure these relays are that model."

"You're just addicted to Twitter, bro."

"Some people are lost and go back to their angry apps."

It may just be that UI/UX sucks ass here and most of us are too biased to see it.

#Nostr

anonymous 9mo ago

This isn't always the right perspective. The argument isn't always about "I don't want to learn new UI even if it's better". It's about, "I know what I'm doing or even I don't, and I don't want my UI to force me into patterns I don't want or use cases I don't care for or to tell me that what I want makes no sense. Sometimes you want to deviate for a reason.

Needing to learn and understand doesn't necessarily mean bad. And on top of that users may be left with a better understanding.

Reply to this note

Please Login to reply.

Discussion

Matt 9mo ago

I'm not buying it.

Matt 9mo ago

Users shouldn't need to understand the deeply technical aspects of a protocol to have it work well. The whole point of a client is to abstract those things out to some degree so people can easily interface with the protocol. I'm not saying there can't be clients aimed at technical users. But I haven't used one yet that just works well without me having to fuck around. They irritate the shit out of me and I used to be a developer and have a CS degree. I'm not buying that as a feature.