UiFlow
Studio Refactor
Read Case Study
Description
Flint is a friendly go-to wallet for DeFi and NFTs. Before I was brought in to redesign the platform, users faced immediate friction: too many wallet options, unclear guidance, technical jargon, and inconsistent UI, leading to hesitation and setup drop-off.
My role was to redesign onboarding so that first-time users could set up a wallet quickly and feel confident doing it.
This new experience unifies mobile and web chrome extension flows: copy, visuals, and interactions so the product feels consistent from the very first screen.
Challenge
How might we guide first-time users through wallet setup, including creating, restoring, or connecting a wallet, using clear language, fewer steps, and a consistent cross-platform experience?
Constraints
We had to keep strict security practices (especially around seed phrases), reuse existing engineering infrastructure, and ship improvements to both mobile and extension at the same time. The work also needed to lay a small but durable visual system we could extend to future features.
Research
Our team collaborated closely to understand where and why users struggled during onboarding. We conducted focused usability sessions with first-time and light crypto users, documenting their experience from the initial screen through account setup. In parallel, we performed a comprehensive audit of the onboarding flow, reviewing UX writing, visual hierarchy, and cross-platform consistency to uncover unnecessary complexity and gaps in user feedback.
From this research, three key issues emerged as critical barriers for both users and the business:
Technical jargon confused beginners and increased drop-off during setup.
Unclear calls to action made it difficult for users to understand the next step.
Visual inconsistencies weakened user trust and reduced brand credibility.
Unified Visual Language
Together with the senior designer, I helped establish a consistent visual foundation across mobile and extension. We defined shared typography, spacing, and color tokens that improved readability and brand cohesion. This alignment not only built user trust but also simplified developer implementation by ensuring both platforms followed the same design logic.
Step-by-step Onboarding
As a team, we redesigned onboarding into a guided, linear flow. Each screen focused on a single task with clear progress indicators, allowing users to move forward with confidence. By revealing information gradually and reducing cognitive load, we made setup faster and easier for first-time crypto users.
User-friendly Microcopy & Inline Help
Working closely with upper management, we rewrote technical copy into clear, approachable language. Helper text and tooltips were added directly where users needed context—explaining terms like “seed phrase” or “hardware wallet” without overwhelming them. This collaborative rewrite made the experience more inclusive and user-friendly.
Takeaway
We delivered a production‑ready onboarding system for Flint Mobile and Flint Chrome Extension, backed by a solid design system (tokens, core components, and copy guidelines). In testing, more users finished setup, made fewer errors, and reported higher confidence on first run. The shared foundations now support future wallet flows without re‑solving the same problems.
Result: Faster completion, fewer drop‑offs, and higher first‑session confidence in testing.
Clocks is an app designed, developed and released on the App Store.
View in App Store
Challenge
How might we guide first-time users through wallet setup, including creating, restoring, or connecting a wallet, using clear language, fewer steps, and a consistent cross-platform experience?
Constraints
Users had trouble locating the logic and data tools, and even when they did, the workspace for creating data connections and logical workflows felt cramped and limiting.
At the same time, we had finalized our feature roadmap for the upcoming quarters, which included several visual editor improvements. Because many of these features would require changes to placement, visibility, and layout, it made sense to address all of these usability issues together.
Unified Visual Language
Together with the senior designer, I helped establish a consistent visual foundation across mobile and extension. We defined shared typography, spacing, and color tokens that improved readability and brand cohesion. This alignment not only built user trust but also simplified developer implementation by ensuring both platforms followed the same design logic.
Step-by-Step Onboarding
As a team, we redesigned onboarding into a guided, linear flow. Each screen focused on a single task with clear progress indicators, allowing users to move forward with confidence. By revealing information gradually and reducing cognitive load, we made setup faster and easier for first-time crypto users.
User-friendly Microcopy & Inline Support
Working closely with upper management, we rewrote technical copy into clear, approachable language. Helper text and tooltips were added directly where users needed context—explaining terms like “seed phrase” or “hardware wallet” without overwhelming them. This collaborative rewrite made the experience more inclusive and user-friendly.
Research
Our team collaborated closely to understand where and why users struggled during onboarding. We conducted focused usability sessions with first-time and light crypto users, documenting their experience from the initial screen through account setup. In parallel, we performed a comprehensive audit of the onboarding flow, reviewing UX writing, visual hierarchy, and cross-platform consistency to uncover unnecessary complexity and gaps in user feedback.
From this research, three key issues emerged as critical barriers for both users and the business:
Technical jargon confused beginners and increased drop-off during setup.
Unclear calls to action made it difficult for users to understand the next step.
Visual inconsistencies weakened user trust and reduced brand credibility.
Takeaway & Reflection
We delivered a production‑ready onboarding system for Flint Mobile and Flint Chrome Extension, backed by a solid design system (tokens, core components, and copy guidelines). In testing, more users finished setup, made fewer errors, and reported higher confidence on first run. The shared foundations now support future wallet flows without re‑solving the same problems.
Result: Faster completion, fewer drop‑offs, and higher first‑session confidence in testing.
Description
Flint is a friendly go-to wallet for DeFi and NFTs. Before I was brought in to redesign the platform, users faced immediate friction: too many wallet options, unclear guidance, technical jargon, and inconsistent UI, leading to hesitation and setup drop-off.
My role was to redesign onboarding so that first-time users could set up a wallet quickly and feel confident doing it.
This new experience unifies mobile and web chrome extension flows: copy, visuals, and interactions so the product feels consistent from the very first screen.