Opening the ROSE Wallet to non-native web3 users

Client

Oasis Protocol

Timeline

10 weeks

Services

UX Design
UX Design · Design leadership · UI design · Product design
·
UX Design · Design leadership · UI design · Product design
·
UX Design · Design leadership · UI design · Product design
·
UX Design · Design leadership · UI design · Product design
·
UX Design · Design leadership · UI design · Product design
·
UX Design · Design leadership · UI design · Product design
·
UX Design · Design leadership · UI design · Product design
·
UX Design · Design leadership · UI design · Product design
·
UX Design · Design leadership · UI design · Product design
·
UX Design · Design leadership · UI design · Product design
·
UX Design · Design leadership · UI design · Product design
·
UX Design · Design leadership · UI design · Product design
·
UX Design · Design leadership · UI design · Product design
·
UX Design · Design leadership · UI design · Product design
Opening the ROSE Wallet to non-native web3 users

Intro

Overview

With more non-native web3 users accessing the industry, the user experience of a web wallet can make or break user adoption. This case study explores my role as the Senior UX/UI Product Designer in optimizing the Oasis web wallet, also known as the ROSE wallet. The project aimed to update the information architecture, improve UX writing, and refine the onboarding flow to enhance user engagement and satisfaction.

Role & Responsibilities

As the lead designer on this project, I was responsible for:

  • Updating and optimizing the information architecture (IA)
  • Reviewing and enhancing UX writing for clarity and consistency
  • Redesigning the onboarding flow with a focus on profile creation
  • Conducting user interviews and testing to inform design decisions
  • Collaborating with the engineering team for seamless implementation

details
·
details
·
details
·
details
·

details

·
details
·
details
·
details
·
details
·
details
·
details
·
details
·
details
·
details

The Challenge: Enhancing Usability and Feature Adoption

The ROSE wallet faced several challenges, including a complex information architecture that led to user errors and a high cognitive load. Key features were difficult to find, and inconsistent UX writing added to user confusion. Additionally, the onboarding flow needed refinement to improve user understanding and interaction, particularly around profile creation and password management.

To start the project, I conducted user interviews and usability testing to gather insights into the current state of the ROSE wallet. Users frequently mentioned confusion around certain features, difficulty navigating the interface, and unclear language that led to errors. These insights highlighted the need for a more intuitive information architecture, clearer UX writing, and an improved onboarding experience.

Based on the feedback, I began by optimizing the information architecture to reduce user errors and cognitive load. This involved simplifying the IA by relocating and merging content, making it easier for users to find essential features like the fiat on-ramp and the address book. By reducing the depth of the IA, users could navigate the wallet more intuitively, leading to increased feature adoption rates.

Improving UX Writing: Clarity and Consistency

Next, I focused on reviewing and enhancing the UX writing. Two significant changes were made to improve clarity:

  1. Renaming 'Address Book' to 'Contacts': To avoid confusion, we renamed the ‘Address Book’ to ‘Contacts’. This change clarified that the section contained external addresses rather than the user’s own accounts.
  2. Simplifying Password Creation Language: Previously, the phrase ‘Store private keys locally, protected by a password’ caused confusion. We renamed this feature to ‘Create a profile’ and added a brief explanation to make it easier for users to understand and use.

The onboarding flow, particularly around profile creation, required significant improvements. Initially, a simple checkbox with minimal explanation was used for profile creation, leading to user confusion. User interviews revealed the need for a more intuitive and informative interface.

We introduced a toggle feature for enabling profile creation. Users could now create their own passwords and were informed that this password did not replace the wallet’s mnemonic. This change provided a clearer and more user-friendly experience, addressing the confusion and enhancing user understanding.

Transforming the ROSE Wallet Experience

With the design improvements finalized, I worked closely with the engineering team to ensure a smooth handoff and implementation. Detailed documentation and regular communication were essential to maintaining design integrity and addressing any technical challenges that arose.

The optimized information architecture, improved UX writing, and refined onboarding flow significantly enhanced the user experience of the ROSE wallet. Key results included:

  • Increased Feature Adoption: Users found essential features more easily, leading to higher engagement with tools like the fiat on-ramp and contacts.
  • Reduced Cognitive Load: Simplifying the IA and clarifying language reduced user errors and frustration.
  • Enhanced User Understanding: The improved onboarding flow and clearer language increased user confidence and satisfaction.

Conclusion
·
Conclusion
·
Conclusion
·
Conclusion
·

Conclusion

·
Conclusion
·
Conclusion
·
Conclusion
·
Conclusion
·
Conclusion
·
Conclusion
·
Conclusion
·
Conclusion
·
Conclusion
 

Conclusion

The product now sees thousands of unique monthly users, with newly added features and continuous improvements driving traffic up by an additional 47.8%.

 

Key Takeaways

This project demonstrates the impact of thoughtful design on user engagement and satisfaction. By updating the information architecture, improving UX writing, and refining the onboarding flow, we transformed the ROSE wallet into a more intuitive and user-friendly product. This case study highlights my commitment to creating seamless and engaging user experiences in the dynamic web3 landscape.

 

GAllery
·
GAllery
·
GAllery
·
GAllery
·

GAllery

·
GAllery
·
GAllery
·
GAllery
·
GAllery
·
GAllery
·
GAllery
·
GAllery
·
GAllery
·
GAllery
 

 

let's Talk
·
let's Talk
·
let's Talk
·
let's Talk
·
let's Talk
·
let's Talk
·
let's Talk
·
let's Talk
·
let's Talk
·
let's Talk
·
let's Talk
·
let's Talk
·
let's Talk
·
let's Talk
Let's research and
Create together ✌🏼
Copyright donouwens.com