Back
Prototype
Project Overview
Duration
14 Months
Team Size
10 Members
Role
Lead Designer
Overview
An all-in-one solution for users to store and interact with their Web 3 assets in a way that is safe and approachable. In other words... “make crypto less scary.”
Problem Statement
Many people, including those already in the space, find Web 3 and crypto to be quite exclusionary and unapproachable. Many are forced to rely on multiple different platforms with varying degrees of complexity and security for different tasks, making life more difficult and alienating newcomers.
Research
Market Analysis
After conducting thorough market research, we concluded that our main competitors in the crypto space included MetaMask, Coinbase, and Trust Wallet. None, however, featured any substantial identity credential solutions.We also interviewed dozens of users about their crypto habits to better understand their pain points and how recent government regulation influences their experience.
Research
User Interviews
From those who were uninitiated in the space, we gathered data about their understanding of Web 3/Crypto concepts as well as how they interact with their banks and banking apps.Key takeaways included a penchant for caution from users across the board. Many in the target audience were careful about privacy and security yet were very eager to share their contributions to their communities. This dichotomy presented interesting challenges along the way.We created three broad personas centered around Web 3 proficiency. Designs from this point forward attempted to address the pain points of individuals in all three camps. In short, our platform needed to be simple enough for beginners to understand yet powerful enough for more advanced users to appreciate. From our research, we were able to put together some very basic personas.
Personas
Target Audience
Wireframes
We used these personas to inform our decisions. As we worked on new features we would conceptualize our ideas through our versions of wireframes. As a startup we were often forced to move quickly and wireframes were skipped over in favor of reusing design elements to Frankenstein concepts together. Here are some examples of how we approached conceptualizing the "communities" aspect of our app.
Wireframe
Final
Wireframe
Final
Design Process
Credentials
Of the four features I will share, this was the very first. Grav.id enables users to find, earn, and store their credentials. In our attempt to make the Web3 space more approachable, we simplified the credential flow to two steps: add and scan. Adding the credentials allows users to view them in their wallet, similar to a diploma case without the actual diploma inside. Scanning the credential, however, results in indelible proof on the blockchain, ensuring that the credential is securely and permanently recorded.
Design Process
Crypto Currency
Next comes the crypto side of the app. One of the first consistent pieces of feedback we received when showcasing the MVP was a strong push to allow users to store crypto and transform the wallet into a full asset management solution. In an effort to keep things simple, we examined the current offerings on the market and asked ourselves: How can we simplify further?
By reducing visual clutter and paring down the features, we received very positive feedback from users who were new to the Web3 space.
Design Process
Communities
Upon showing the designs to stakeholders and other admins, the results were positive. The clear feedback was that naming conventions and abbreviations needed to be dealt with carefully as administrators require use a common vocabulary which should be maintained. This meant that a more simplified view was not user friendly and could prevent that seamless transition from spreadsheet to app. We revisited the tables and began adjusting columns and rows to maximaize information.
Design Process
Business
As exciting as the previous features are for the average user, we also had to consider what the business side would see. Businesses need the ability to set up their credentials and communities, manage their audience, and promote their services. This often required revising or modifying the user view to create viable business-facing designs. While it took additional research to understand these users’ needs, we successfully addressed the pain points of our business audience.
Design
Prototype
A crucial step in the design process was the prototype. It proved useful in three stages of the post-design process.
‍
Firstly, prototypes were used for stakeholder validation. Individual pages or wireframes often couldn’t effectively convey the full scope of our concepts, making prototypes essential for gaining stakeholder approval.
‍
Secondly, prototypes were incredibly useful for uncovering hidden yet vital interactions. While larger elements were sorted out in earlier wireframes, the fast-paced demands of a startup environment meant that smaller details—like a confirmation modal or a settings shortcut—often only became apparent once everything began coming together.
‍
Lastly, and potentially even more crucial, we used prototypes for user testing. As quickly as our developers could start building our concepts in Flutter, it was still vital to first subject our designs to a few rounds of user tests. These high-fidelity prototypes allowed us to identify any potential issues we may have overlooked, ensuring that the final product was polished and ready for development.
Conclusion
Conclusion
Key Metrics
98%
Task Completion Rate
95%
User Satisfaction Score
1min 35sec
Average Time on Task
Though we were thrilled with these results, in my departure from the team, I suggested to broaden the scope of our testing for reasons that will become important shortly.
Conclusion
Lessons Learned
A dedicated team can achieve anything. Our team, composed primarily of early-career designers, accomplished extraordinary things. Despite the fast-paced startup environment, we stayed focused and completed an app design that received near-unanimous praise. I’m incredibly fortunate to have worked with such an awesome team.
‍
However, there were some significant issues that I’m eager to address in future projects. Moving forward, I’d like to be involved in discussions about scope. Scope creep became a serious issue, forcing us to rework many elements we initially thought were finalized.
‍
Additionally, the Web3 space matured differently than we anticipated. Although it remains a prominent topic for many, major tech companies have largely implemented blockchain credentials quietly in backend infrastructure, rather than promoting them openly. As more cases of crypto fraud surface, the term “blockchain” is increasingly associated with these issues rather than its underlying potential.
‍
For future projects, I intend to take a more strategic approach to market research. Conducting thorough market analysis and understanding the direction from the outset could have led to different outcomes in this case.