You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Download OKX app
Navigate to "wallet" tab
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
The text was updated successfully, but these errors were encountered:
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:
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
The text was updated successfully, but these errors were encountered: