Testing the Dub Browser
This week, I refined various designs related to tabs, pending requests, as well as connected and disconnected wallets. Working closely with Cam, we developed hand-off ready designs that incorporate finalized states and dimensions.
Moreover, we began introducing the Dub Browser to new users. Utilizing a blend of the Dub Browser and Figma prototypes, we conducted tests and collected valuable feedback on our designs.
Discoveries
The most gratifying aspect of the experience was witnessing people’s positive reactions to our features. The universally appealing features included:
- A consistently visible wallet: Users often experience a significant pain point with Brave, Chrome, and other browsers equipped with wallet chrome extensions: when they click on the webview while their wallet plug-in is prompting for input, the wallet vanishes. Our browser keeps the wallet visible at all times, which users find beneficial.
- Viewing all wallets simultaneously: In contrast to the traditional MetaMask approach, where wallets are concealed behind dropdowns and resemble separate accounts demanding constant reconfiguration, our browser enables effortless wallet-switching with just a swipe and a click to connect.
- Distinct wallet instances for each tab: Users found this feature helpful, as knowing which wallet is connected to a particular tab and network is crucial for multitasking.
Areas for Improvement
- Clarifying that tabs represent individual wallet instances: Users tend to expect a separate wallet module to function like MetaMask. We need to strike a balance between visually demonstrating the interaction between wallets and tabs while maintaining a user-friendly experience.
- Pending transaction states: How might we use the screen real estate in the wallet module to provide transaction updates?
- Streamlining wallet and contract addresses: How might we abstract these elements more?
Essential Features
I concluded each conversation by inquiring about the factors preventing users from adopting Dub as their default browser. Across the board, we received similar needs in two key areas before switching to the browser.
Extensions and Add-ons
- Our crypto-native user group, especially blockchain developers, considered Chrome extensions to be a fundamental aspect of their development workflows. These extensions, though some are blockchain-related, assist in the broader development process. For crypto-curious users, extensions ranging from WhatFont to Return YouTube Dislike remained crucial, adding to the switching costs.
- Multi-chain support: Developers using Brave are not utilizing its native wallet. Instead, they continue to rely on MetaMask and Phantom. We currently support EVM chains, but as we learn more about a developer-heavy user base, multi-chain becomes more imperative.
- Crypto Natives that switch browsers often choose Brave because it offers a seamless transition and can only enhance their browsing experience. Key features they need include:
- Built-in ad blocker
- Performance optimization
- IPFS integration
Shortcuts
- Our user interview sample typically experimented with a new browser for approximately one week. During that period, the greatest source of frustration and drop off was mastering new keyboard shortcuts.
Looking Forward
Next week, I’ll be ramping up the user interviews with the latest version of Dub, which launches today! Additionally, I’m eager to take a step back and assess our design mental models from a broader perspective in the coming week.