Thread
UX is king.
Privacy and decentralization are not features. They are architectural decisions that should just be there. Excusing bad UX by selling privacy will get you nowhere.
Users today don’t care about privacy or decentralization. We win by giving them the best UX which also happens to be private and decentralized.
Replies (2)
I obviously agree about the importance of a good UX. But it cannot replace knowing and picking the right values (=features) in the first place.
A great UX should alleviate the pain that necessarily a new protocol introduce, and we should treat users with respect creating a dialogue around these values, don't just try to attract them with easy and appealing solutions. We win explaining what matters, why it matters, and offering good software that makes that obvious and enjoyable.
what if because of the decentralized architecture you can't build a UX as good as the centralized one? (according to some UX criteria)
what do you pick at this point?
