SAFE.GLOBAL/WALLET
SAFE.GLOBAL/WALLET
SAFE.GLOBAL/WALLET
Description
Description
Safe is a leading smart account platform for securely managing digital assets, offering multi-signature security, modular account abstraction, and seamless integrations. I joined the web platform team as a Web Platform Designer to enhance users' daily tasks and make their experience smoother, keeping it easy to use and efficient across the platform.
Read - 10 min
Read - 10 min
Client
Client
Safe.Global
Safe.Global
Year
Year
2021-2024
2021-2024
Category
Category
Smart Contract Wallet
Smart Contract Wallet
My contribution
My contribution
Web platform, Token Launch Apps, Design System
Core interface.
0.0 Disclaimer
0.0 Disclaimer
Due to NDA agreements, only select design files and approved materials are displayed in this portfolio case. The designs presented here are solely to demonstrate my skills as a designer and the processes involved in creating these solutions.
If you represent a competitor company, please respect Safe’s intellectual property and refrain from using any information displayed here for competitive purposes.
Due to NDA agreements, only select design files and approved materials are displayed in this portfolio case. The designs presented here are solely to demonstrate my skills as a designer and the processes involved in creating these solutions.
If you represent a competitor company, please respect Safe’s intellectual property and refrain from using any information displayed here for competitive purposes.
Web Smart Wallet
Over three years, I contributed to a wide range of features, varying in scope and impact. In this case study, I highlight the key flows that made a significant impact on the product, explore the different user personas of Safe Wallet, and showcase how I helped bridge design and development while promoting Safe as a vital player in the ecosystem.
Over three years, I contributed to a wide range of features, varying in scope and impact. In this case study, I highlight the key flows that made a significant impact on the product, explore the different user personas of Safe Wallet, and showcase how I helped bridge design and development while promoting Safe as a vital player in the ecosystem.
1.1 Research
At Safe Design, we consistently conducted user research to enhance the overall experience. While making assumptions about different personas when designing features, we developed a general UX personas.
To better understand user needs, I collaborated with the Design Lead and UX Research team to create detailed user personas for the Safe Wallet. These personas helped shape the experience across mobile, web, and other platforms, ensuring a user-centered and scalable design approach.
Methods
Task Analysis – We broke down key user flows step by step to identify pain points and inefficiencies during wallet setup, usage, and recovery.
Usability Tests – We conducted remote and in-person tests to evaluate how users interact with the product, measuring task success, errors, and overall satisfaction.
1-on-1 User Interviews – These semi-structured interviews helped us explore user goals, behaviors, and mental models, providing deeper insight into their motivations and frustrations.
Contextual Inquiry – By observing users in real-world settings, we uncovered environmental constraints and behavioral patterns that informed mobile and multi-platform design decisions.
At Safe Design, we consistently conducted user research to enhance the overall experience. While making assumptions about different personas when designing features, we developed general UX persona files to ensure a structured approach.
To better understand user needs, I collaborated with the Design Lead and UX Research team to create detailed user personas for the Safe Wallet. These personas helped shape the experience across mobile, web, and other platforms, ensuring a user-centered and scalable design approach.
Onboarding
Onboarding
When I joined Safe, my first initiative in enhancing the user experience was optimizing the Safe creation flow. Since using a smart contract wallet can already be complex for non-technical users, the onboarding process is needed to educate, simplify, and guide users effectively. Some of the key improvements included:
Onboarding structure – Defining a clear, intuitive first setup framework. (2021)
Counterfactual deployment – Enabling gas-efficient and flexible Safe creation. (2023)
One of the first key initiatives in enhancing the user experience was optimizing the Safe creation flow. Since using a smart contract wallet can already be complex for non-technical users, the onboarding process is needed to educate, simplify, and guide users effectively. Some of the key improvements included:
Onboarding structure – Defining a clear, intuitive first setup framework. (2021)
Counterfactual deployment – Enabling gas-efficient and flexible Safe creation. (2023)
2.1 Onboarding - First iteration
Hypothesis
If we simplify and structure the Safe creation process while educating users along the way, we can improve onboarding and help more users confidently set up and start using Safe.
Goal
Design a clear and intuitive setup flow that builds user confidence and reduces friction.
Constrains
With the broader Safe redesign and ongoing code cleanup, I had to propose quick, lightweight design solutions—small changes that could be implemented fast and still deliver real value.
Primary KPIs
Onboarding Completion Rate
Support Tickets or Errors
One of the first key initiatives in enhancing the user experience was optimizing the Safe creation flow. Since using a smart contract wallet can already be complex for non-technical users, the onboarding process needed to educate, simplify, and guide users effectively.
Hypothesis
By simplifying, structuring, and educating users during the Safe creation process, we can improve onboarding rates and encourage more users to successfully set up and use Safe.
Goal
Design a clear, intuitive, and meaningful Safe creation flow that reduces friction and enhances user confidence.
Constrains
Due to the global Safe redesign and ongoing code optimization by the development team, I was constrained to proposing only simple, quick-to-develop solutions. This limitation ensured that design improvements could be validated efficiently while establishing a workflow for rapid UI iterations without disrupting the larger development process.
Onboarding flow steps.
2.2 Onboarding - First iteration - Results
The key things I wanted to improve in the Safe creation flow included:
Education – Introduced assistive tooltips at key steps to guide users on security, system status, and wallet features.
Security tips – To emphasize the multisig security feature, I implemented an interactive tooltip that dynamically adjusted based on the number of signers. It provided optimized threshold recommendations to help users achieve the best security setup.
Transaction status – Since deploying a Safe takes time, I designed a real-time deployment status screen to keep users informed throughout the process.
The redesigned Safe creation flow significantly improved onboarding clarity and user confidence. By introducing educational tooltips, contextual security guidance, and real-time deployment feedback, we addressed key friction points in the setup process. Despite technical constraints, lightweight design improvements led to measurable impact:
+9% increase in onboarding completion rate within the first 3 months
Fewer support tickets related to Safe creation setup, indicating clearer user guidance
Higher engagement with security tips—users adjusted signer thresholds more often in line with recommendations
These results validated the hypothesis that simplifying and educating during onboarding encourages more successful wallet setups and strengthens user trust in a technically complex product.
The main areas of improvement in the Safe creation flow included:
Education – Introduced assistive tooltips at key steps to guide users on security, system status, and wallet features.
Security tips – To emphasize the multisig security feature, I implemented an interactive tooltip that dynamically adjusted based on the number of signers. It provided optimized threshold recommendations to help users achieve the best security setup.
Transaction status – Since deploying a Safe takes time, I designed a real-time deployment status screen to keep users informed throughout the process.
2.3 Onboarding - "Pay later"
Another pain point we identified through surveys and user conversations was the cost of deploying a smart account. While developers and crypto-savvy users understand the necessity and cost of deploying a smart contract, new users found it to be a barrier.
Hypothesis
If we remove the initial deployment costs, provide a seamless, fee-free onboarding flow, and guide users through the setup process, we can increase the number of Safes created and actively used.
Goal
Increased number of created and active Safes..
Another pain point we identified through surveys and user conversations was the cost of deploying a smart account. While developers and crypto-savvy users understand the necessity and cost of deploying a smart contract, new users found it to be a barrier. To make onboarding smoother, I collaborated with development and product teams to implement counterfactual deployment, allowing users to start using Safe without upfront deployment costs.
Hypothesis
If we remove the initial deployment costs, provide a seamless, fee-free onboarding flow, and guide users through the setup process, we can increase the number of Safes created and actively used.
Goal
Increased number of created and active Safes..
Create Safe Flow
Step-by-step post deployment onboarding
2.4 Onboarding - "Pay later" - Results
Although the persona-based onboarding approach wasn’t approved by product team, I moved forward with a simplified account creation flow that only required users to choose between 'Pay now' or 'Pay later' deployment options.
In testing, this wording proved to be the most engaging during user studies.
Persona-based variant kill
The persona-based variant was sunset because, over time, it proved difficult to scale and maintain tailored solutions for each user group without introducing complexity or inconsistency. Instead, I shifted focus toward white-label and modular design solutions that could flexibly serve different user needs while maintaining a unified system. This allowed the product to scale more efficiently across platforms and partners without fragmenting the experience.
Step-by-step post deployment onboarding
Additionally, the step-by-step post deployment onboarding approach (picture to the right) showed positive results, reinforcing the decision to streamline the proces
The introduction of the “Pay now” / “Pay later” deployment option lowered entry barriers and made onboarding more accessible for non-technical users. This lightweight update, supported by clear language and streamlined UI, contributed to noticeable improvements:
+7% increase in the number of Safes created after introducing the pay-later option
Higher engagement among first-time users, with smoother transitions into post-deployment onboarding
Reduced confusion and drop-off during the setup process, as confirmed by usability testing and support feedback
While the persona-based onboarding variant was sunset due to scalability issues, shifting toward modular, white-label design proved to be a more sustainable approach. The simplified account creation flow and the step-by-step onboarding guidance post-deployment helped users better understand their wallet setup and fostered long-term engagement.
Transaction flow
The Safe user interface is inherently complex, offering extensive adaptability for developers and tech-savvy users. A simple transaction flow goes beyond just sending tokens from point A to point B—it also includes advanced transaction details, security checks, and the flexibility to schedule or execute transactions at different times.
Transaction flow
The Safe user interface is inherently complex, offering extensive adaptability for developers and tech-savvy users. A simple transaction flow isn’t just about sending tokens from point A to point B, it also involves advanced transaction info, security checks, and the ability to schedule or execute transactions at different times.
3.1 Transaction flow - redesign
Pain points
No unified structure and documentation of user actions within transactions.
The modal transaction view had outgrown its content, making it cluttered.
It was difficult for non-crypto-savvy users to quickly understand the required action (Create, Sign, Execute).
Hypothesis
A well-organized transaction flow will simplify transaction creation, reduce the average time required to create and execute transactions, and encourage users to transact more frequently.
Goal
Increase number of created and executed transactions.
Design documentation
Beyond ensuring a user-friendly UI, it was crucial to establish a clear and meaningful structure. I took the initiative to create a detailed list of all potential transactions and states. This allowed anyone in the company to review, identify areas for improvement, and spot potential issues.
Pain points
No unified structure for user actions within transactions.
The modal transaction view had outgrown its content, making it cluttered.
It was difficult for non-crypto-savvy users to quickly understand the required action (Create, Sign, Execute).
Hypothesis
A well-organized transaction flow will simplify transaction creation, reduce the average time required to create and execute transactions, and encourage users to transact more frequently.
Goal
Increased number of created and executed transactions.
Beyond ensuring a user-friendly UI, it was crucial to establish a clear and meaningful structure. At the time, Safe lacked comprehensive documentation on possible user actions, so I took the initiative to create a detailed list of all potential transactions and states. This allowed anyone in the company to review, identify areas for improvement, and spot potential issues.
3.2 Batch transactions
A crucial aspect of optimizing the transaction flow is enabling users to execute multiple transactions at the same time. By enabling batch transactions to be executed in a single batch, we sought to reduce gas fees, improve transaction speed, and enhance the overall blockchain transaction experience.
Design Decisions
Persistent Access Point
I positioned the entry to the feature so it remains visible at all times, ensuring accessibility regardless of where the transaction originates within the UI.
Reorder Functionality
I introduced a reorder feature, as the position of a transaction within a batch can impact execution costs. This allows users to optimize their transaction order for better efficiency.
Educational Onboarding
During early testing, we discovered that some users weren’t aware they could batch different types of transactions beyond just sending tokens. To address this, I added informational guidance in the empty batch view state to clarify its full capabilities.
A crucial aspect of optimizing the transaction flow is enabling users to execute multiple transactions at the same time. By enabling batch transactions to be executed in a single batch, we sought to reduce gas fees, improve transaction speed, and enhance the overall blockchain transaction experience.
Design Decisions
Persistent Access Point
I positioned the entry to the feature so it remains visible at all times, ensuring accessibility regardless of where the transaction originates within the UI.
Reorder Functionality
I introduced a reorder feature, as the position of a transaction within a batch can impact execution costs. This allows users to optimize their transaction order for better efficiency.
Educational Onboarding
During early testing, we discovered that some users weren’t aware they could batch different types of transactions beyond just sending tokens. To address this, I added informational guidance in the empty batch view state to clarify its full capabilities.
3.3 Results
Redesigning the transaction flow and introducing batch transaction support led to a more intuitive and powerful experience for both technical and non-technical users. Key outcomes included:
+13% increase in executed transactions, driven by improved clarity and efficiency
Faster execution times, with users completing complex transaction flows more quickly thanks to better structure and guidance
Fewer support requests related to unclear transaction states or steps, especially from less technical users
The implementation of persistent access points and the ability to reorder transactions helped advanced users optimize gas costs and streamline workflows. At the same time, educational onboarding in empty states clarified the value of batching, increasing discoverability of advanced functionality.
Finally, the internal documentation of transaction types and states improved cross-team alignment, reducing confusion for developers and enabling quicker iteration on future improvements.
A crucial aspect of optimizing the transaction flow is enabling users to execute multiple transactions at the same time. By enabling batch transactions to be executed in a single batch, we sought to reduce gas fees, improve transaction speed, and enhance the overall blockchain transaction experience.
Design Decisions
Persistent Access Point
I positioned the entry to the feature so it remains visible at all times, ensuring accessibility regardless of where the transaction originates within the UI.
Reorder Functionality
I introduced a reorder feature, as the position of a transaction within a batch can impact execution costs. This allows users to optimize their transaction order for better efficiency.
Educational Onboarding
During early testing, we discovered that some users weren’t aware they could batch different types of transactions beyond just sending tokens. To address this, I added informational guidance in the empty batch view state to clarify its full capabilities.
Create batch transaction - New Transaction
Create batch transaction - Using Safe App
Token Claiming App
As Safe spun off from Gnosis, we were actively preparing for the Safe token launch. Deadlines were tight, with a high volume of tasks across different stages of token interactions. One key task was designing an Airdrop app that allowed Safe users to claim their tokens.
As Safe spun off from Gnosis, we were actively preparing for the Safe token launch. Deadlines were tight, with a high volume of tasks across different stages of token interactions. One key task was designing an Airdrop app that allowed Safe users to claim their tokens.
4.1 App Design
Goal
Effectively educate users about the token utility and SafeDAO. Activate users' voting power to engage them in governance.
Constrains
Time pressure required a simplified UI to meet tight release deadlines.
The design needed to be adaptable, allowing stakeholders to update content without disrupting the layout.
The UI had to integrate the new branding while transitioning to the new Design System.
Goal
Effectively educate users about the token utility and SafeDAO. Activate users' voting power to engage them in governance.
Constrains
Time pressure required a simplified UI to meet tight release deadlines.
The design needed to be adaptable, allowing stakeholders to update content without disrupting the layout.
The UI had to integrate the new branding while transitioning to the new Design System.
Info flow
Voting power and Safe allocation
Safe{Pass}
One of the big milestones for Safe was the token launch, and I was excited to contribute by working on the designs for it. As part of the follow-up, the team introduced an initiative to encourage users to lock their Safe tokens and earn rewards while engaging with Safe and its partners. The goal was to give users more value—not just for holding the token, but by actively participating in the ecosystem. It was a great way to help them unlock utility and benefit from deeper integrations within the Safe ecosystem.
As Safe spun off from Gnosis, we were actively preparing for the Safe token launch. Deadlines were tight, with a high volume of tasks across different stages of token interactions. One key task was designing an Airdrop app that allowed Safe users to claim their tokens.
5.1 App Design
Hypothesis
If we create a seamless and transparent locking mechanism for Safe tokens with clear incentives and an intuitive user experience, we can encourage more users to participate in the initiative, increasing engagement with Safe and its partners while reinforcing long-term commitment to the ecosystem.
Constrains
Rapid design iterations and a live design approach to keep up with evolving requirements.
Hypothesis
If we create a seamless and transparent locking mechanism for Safe tokens with clear incentives and an intuitive user experience, we can encourage more users to participate in the initiative, increasing engagement with Safe and its partners while reinforcing long-term commitment to the ecosystem.
Constrains
Rapid design iterations and a live design approach to keep up with evolving requirements.
App info
Token locking mechanism
4.2 Landing Page & Visual language
4.2 Landing Page & Visual language
To support the app launch, I also designed a landing page. It was built using pre-made blocks that were already used for other pages of the website, ensuring consistency and efficiency. While working on the app, I developed a visual language that was later repurposed for marketing materials and supporting visuals, creating a cohesive brand experience.
To support the app launch, I also designed a landing page. It was built using pre-made blocks that were already used for other pages of the website, ensuring consistency and efficiency. While working on the app, I developed a visual language that was later repurposed for marketing materials and supporting visuals, creating a cohesive brand experience.
Safe Design System
While working on the app redesign and Safe’s rebranding post-spinoff, we set a design team KPI to create a public design system—one of the first for a multisignature wallet.
Since most teams lack dedicated designers, we aimed to provide an easy-to-implement, shareable solution, making Safe’s design system accessible and adaptable for the broader community.
To support me in this project, we hired a freelance design system specialist to help refine and perfect the system elements. Through this collaboration, I deepened my expertise in building design systems, gaining valuable insights into scalability, consistency, and best practices
Safe Design System
While working on the app redesign and Safe’s rebranding post-spinoff, we set a design team KPI to create a public design system—one of the first for a multisignature wallet.
Since most teams lack dedicated designers, we aimed to provide an easy-to-implement, shareable solution, making Safe’s design system accessible and adaptable for the broader community.
To support me in this project, we hired a freelance design system specialist to help refine and perfect the system elements. Through this collaboration, I deepened my expertise in building design systems, gaining valuable insights into scalability, consistency, and best practices
5.1 Results
5.1 Results
Goal
Develop a shareable design system to position the Safe design team as an active contributor to the ecosystem and promote collaboration within the community.
Constrains
The design system was MUI-based, optimized for developer efficiency, which limited customization and required aligning with MUI’s component structures and patterns.
Let's Connect!
Currently, I'm looking for a next big thing.
Let's Connect!
Currently, I'm looking for a next big thing.
Let's Connect!
Currently, I'm looking for a next big thing.
