Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bridge UX Benchmark #18

Open
Icreatedthisaccountjustforonereason opened this issue Nov 3, 2024 · 0 comments
Open

Bridge UX Benchmark #18

Icreatedthisaccountjustforonereason opened this issue Nov 3, 2024 · 0 comments

Comments

@Icreatedthisaccountjustforonereason
Copy link

Icreatedthisaccountjustforonereason commented Nov 3, 2024

The current Zenon bridge has an abysmal UX and throws off newcomers. I won't support this claim with data as it should be pretty iobvious if you compare it to a best practice below:

  1. Download OKX app
  2. Navigate to "wallet" tab
  3. Bridge any asset from eth to sol or any other chain

If your process takes longer or more steps than it takes to bridge assets from one chain to another on okx web3 wallet, your bridge's UX is sub par and likely a significant contributing factor for drop off rates and / or lack of adoption.

Do not attribute bad UX to security needs, others show that UX and security are not tradeoffs.

Given that you and other devs were paid a lot of znn / qsr for this, one would think you'd have a vested interest in continuously improving your code to meet the market benchmark and optimize for adoption (i.e. UX).

Also, apparently this is the only way to reach you - consider accepting telegram as an additional feedback channel if you are serious about gathering user feedback to improve your code. Non technical users cba to raise a github issue (me included but here I am) but it's their feedback you should want most.

Ps. I'd rather we didn't need a bridge in the first place for obvious reasons.

Yours sincerely,
Shazz

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant