Arbitrum UX/UI DeepDive
andrewdamelio opened this issue · comments
Arbitrum Usage Exploration
- Look into using L2 dApps with a focus on UX/UI handling of setup, bridging and app usage.
- Determine pain points and things we can do UX wise to help them.
- Start to explorer what is required on a UI front (components, flows, guides) to help implement Arbitrum
MetaMask
Pain Points
Setup
Both Matic and Arbitrum have the same setup configuration process. A custom network needs to be added to MetaMask.
Matic has the extra step of having to acquiring a native Matic token to use on Matic L2 so if we are using ETH, or a common ERC this extra step is removed with Arbitrum.
Adding a custom network is extremely annoying, there is lots of data to write it, and copying is difficult b/c MetaMask will lose focus.
There is actually a great solution in the works for this. MetaMask has a network API coming so we will be able to provide a hook to allow users to either approve a MetaMask network switch, or to approve adding the network as a custom end point.
Bridging
- Whenever you need to bridge you usually will need to toggle between L1/L2. This was a UX pain point for me. It's hard to tell currently which Network i'm connected to, and which controls on the page are relevant.
- I think having some type of colour scheme to switch over when moving between L1/L2 so its clear which NETWORK i'm connected to.
- Alternatively, maybe having a colour scheme convey to me which L# i need to switch to inside my metamask
