Contributions
Contributions
Design Lead — Interaction Design, Visual Design, Prototyping, User Flows
Design Lead — Interaction Design, Visual Design, Prototyping, User Flows
Timeline & Status
Timeline & Status
3 Weeks, Sunset
3 Weeks, Sunset
*To protect key functionalities and sensitive features, certain details have been intentionally omitted while maintaining the integrity of the project’s narrative.
*To protect key functionalities and sensitive features, certain details have been intentionally omitted while maintaining the integrity of the project’s narrative.
Contributions
Design Lead — Interaction Design, Visual Design, Prototyping, User Flows
Timeline & Status
3 Weeks, Sunset
*To protect key functionalities and sensitive features, certain details have been intentionally omitted while maintaining the integrity of the project’s narrative.
I led the design direction for Universal Connect at Blockus—bridging traditional social logins and blockchain wallets into a single, unified solution.
I led the design direction for Universal Connect at Blockus—bridging traditional social logins and blockchain wallets into a single, unified solution.
I led the design direction for Universal Connect at Blockus—bridging traditional social logins and blockchain wallets into a single, unified solution.
For new users, onboarding into Web3 felt overwhelming—complex steps like creating accounts and connecting wallets led many to drop off before they even got in.
We designed a builder to help Web3 teams ease that friction—making sign-in feel simple, familiar, and fast, so users could start with confidence and teams could focus on what they came to build.
For new users, onboarding into Web3 felt overwhelming—complex steps like creating accounts and connecting wallets led many to drop off before they even got in.
We designed a builder to help Web3 teams ease that friction—making sign-in feel simple, familiar, and fast, so users could start with confidence and teams could focus on what they came to build.
For new users, onboarding into Web3 felt overwhelming—complex steps like creating accounts and connecting wallets led many to drop off before they even got in.
We designed a builder to help Web3 teams ease that friction—making sign-in feel simple, familiar, and fast, so users could start with confidence and teams could focus on what they came to build.
Context
Context
Context
Onboarding into Web3 felt overwhelming—seed phrases, wallet setup, and unfamiliar crypto concepts made it feel like one wrong move could cost everything.
Onboarding into Web3 felt overwhelming—seed phrases, wallet setup, and unfamiliar crypto concepts made it feel like one wrong move could cost everything.
Onboarding into Web3 felt overwhelming—seed phrases, wallet setup, and unfamiliar crypto concepts made it feel like one wrong move could cost everything.
For Web3 apps, this wasn’t just a UX issue—it meant losing users before they even got in. And in a space this early, every user mattered.
So we designed a builder to ease that first step—connecting familiar logins like Google or Discord to wallets, making onboarding feel simple, safe, and more like something people actually wanted to finish.
For Web3 apps, this wasn’t just a UX issue—it meant losing users before they even got in. And in a space this early, every user mattered.
So we designed a builder to ease that first step—connecting familiar logins like Google or Discord to wallets, making onboarding feel simple, safe, and more like something people actually wanted to finish.
For Web3 apps, this wasn’t just a UX issue—it meant losing users before they even got in. And in a space this early, every user mattered.
So we designed a builder to ease that first step—connecting familiar logins like Google or Discord to wallets, making onboarding feel simple, safe, and more like something people actually wanted to finish.
Problem
Problem
Problem
Customization was limited, and every change felt disconnected—the MVP just didn’t give teams the flexibility they needed.
Customization was limited, and every change felt disconnected—the MVP just didn’t give teams the flexibility they needed.
Customization was limited, and every change felt disconnected—the MVP just didn’t give teams the flexibility they needed.
Core functions were scattered, previews were isolated, and the structure didn’t match how people actually worked. It made simple decisions feel like scavenger hunts—and turned quick edits into frustrating guesswork.
Core functions were scattered, previews were isolated, and the structure didn’t match how people actually worked. It made simple decisions feel like scavenger hunts—and turned quick edits into frustrating guesswork.
Core functions were scattered, previews were isolated, and the structure didn’t match how people actually worked. It made simple decisions feel like scavenger hunts—and turned quick edits into frustrating guesswork.
Opportunity
Opportunity
Opportunity
What if customization felt less like work and more like play?
What if customization felt less like work and more like play?
What if customization felt less like work and more like play?
The existing builder had potential—it just lacked direction. With support from leadership, I was given full creative freedom to reimagine the experience from the ground up and bring clarity, control, and confidence back to the process.
The existing builder had potential—it just lacked direction. With support from leadership, I was given full creative freedom to reimagine the experience from the ground up and bring clarity, control, and confidence back to the process.
The existing builder had potential—it just lacked direction. With support from leadership, I was given full creative freedom to reimagine the experience from the ground up and bring clarity, control, and confidence back to the process.
NORTH STAR
NORTH STAR
NORTH STAR
Customizable for every brand
Customizable for every brand
Customizable for every brand
Empower teams to create authentication flows that reflect their unique branding, offering flexibility to meet diverse design and functional needs.
Empower teams to create authentication flows that reflect their unique branding, offering flexibility to meet diverse design and functional needs.
Empower teams to create authentication flows that reflect their unique branding, offering flexibility to meet diverse design and functional needs.
Effortless visibility
Effortless visibility
Effortless visibility
Give teams real-time feedback on their changes so they can move faster, experiment confidently, and optimize without second-guessing.
Give teams real-time feedback on their changes so they can move faster, experiment confidently, and optimize without second-guessing.
Give teams real-time feedback on their changes so they can move faster, experiment confidently, and optimize without second-guessing.
Layout
Layout
Layout
We identified a critical problem in the flow—developers couldn’t see the impact of their changes without bouncing between tabs and interfaces.
We identified a critical problem in the flow—developers couldn’t see the impact of their changes without bouncing between tabs and interfaces.
We identified a critical problem in the flow—developers couldn’t see the impact of their changes without bouncing between tabs and interfaces.
The old layout buried the preview, turning simple edits into guesswork. I restructured the interface with one goal: keep the preview front and center.
By anchoring the layout around a live, persistent preview, every customization stayed grounded in context—giving developers clarity, speed, and confidence as they worked.
The old layout buried the preview, turning simple edits into guesswork. I restructured the interface with one goal: keep the preview front and center.
By anchoring the layout around a live, persistent preview, every customization stayed grounded in context—giving developers clarity, speed, and confidence as they worked.
The old layout buried the preview, turning simple edits into guesswork. I restructured the interface with one goal: keep the preview front and center.
By anchoring the layout around a live, persistent preview, every customization stayed grounded in context—giving developers clarity, speed, and confidence as they worked.
Important tools were buried, scattered across tabs, and the logic behind the grouping never really clicked.
Important tools were buried, scattered across tabs, and the logic behind the grouping never really clicked.
Important tools were buried, scattered across tabs, and the logic behind the grouping never really clicked.
I redesigned the layout to group tools by intent—organizing property types into clear, scannable sections that made it easier to find what’s needed, reduce decision fatigue, and customize with confidence.
I redesigned the layout to group tools by intent—organizing property types into clear, scannable sections that made it easier to find what’s needed, reduce decision fatigue, and customize with confidence.
I redesigned the layout to group tools by intent—organizing property types into clear, scannable sections that made it easier to find what’s needed, reduce decision fatigue, and customize with confidence.
Customization
Customization
Customization
Toggles were buried in panels, so I opened everything up—surfacing options and letting teams get granular.
Toggles were buried in panels, so I opened everything up—surfacing options and letting teams get granular.
Toggles were buried in panels, so I opened everything up—surfacing options and letting teams get granular.
From border radius to font weight, every detail was surfaced—accessible, editable, and visible—so teams could move from generic configuration to thoughtful expression, and actually see the brand they were shaping.
From border radius to font weight, every detail was surfaced—accessible, editable, and visible—so teams could move from generic configuration to thoughtful expression, and actually see the brand they were shaping.
From border radius to font weight, every detail was surfaced—accessible, editable, and visible—so teams could move from generic configuration to thoughtful expression, and actually see the brand they were shaping.
To support more teams and use cases, I made the layout flexible in both shape and style—so it could fit naturally into any product experience.
To support more teams and use cases, I made the layout flexible in both shape and style—so it could fit naturally into any product experience.
To support more teams and use cases, I made the layout flexible in both shape and style—so it could fit naturally into any product experience.
Developers needed more than just options—they needed control.
Developers needed more than just options—they needed control.
Developers needed more than just options—they needed control.
By letting them reorder login methods, I gave teams the ability to lead with what matters most to their users—whether it’s Discord for communities, or Google for mass-market apps.
By letting them reorder login methods, I gave teams the ability to lead with what matters most to their users—whether it’s Discord for communities, or Google for mass-market apps.
By letting them reorder login methods, I gave teams the ability to lead with what matters most to their users—whether it’s Discord for communities, or Google for mass-market apps.
Preview
Preview
Preview
I designed a live, real-time preview that updates as developers customize—right where they’re working.
I designed a live, real-time preview that updates as developers customize—right where they’re working.
I designed a live, real-time preview that updates as developers customize—right where they’re working.
No more switching tabs or guessing how things will look. It gave teams immediate feedback and a tighter feedback loop—so they could tweak, refine, and actually enjoy seeing their work take shape.
No more switching tabs or guessing how things will look. It gave teams immediate feedback and a tighter feedback loop—so they could tweak, refine, and actually enjoy seeing their work take shape.
No more switching tabs or guessing how things will look. It gave teams immediate feedback and a tighter feedback loop—so they could tweak, refine, and actually enjoy seeing their work take shape.
I introduced the ability for studios to reorder sign-in options—recognizing that some may want to prioritize Web2 sign-in methods to attract broader audiences, while others may choose to highlight Web3 options to engage crypto-native users.
I introduced the ability for studios to reorder sign-in options—recognizing that some may want to prioritize Web2 sign-in methods to attract broader audiences, while others may choose to highlight Web3 options to engage crypto-native users.
I introduced the ability for studios to reorder sign-in options—recognizing that some may want to prioritize Web2 sign-in methods to attract broader audiences, while others may choose to highlight Web3 options to engage crypto-native users.
To support different workflows, I added a bottom bar that lets teams toggle between layouts and see the exact code they’d need to implement it.
To support different workflows, I added a bottom bar that lets teams toggle between layouts and see the exact code they’d need to implement it.
To support different workflows, I added a bottom bar that lets teams toggle between layouts and see the exact code they’d need to implement it.
It helped developers move from exploring to shipping—without second-guessing what things would look like in production.
It helped developers move from exploring to shipping—without second-guessing what things would look like in production.
It helped developers move from exploring to shipping—without second-guessing what things would look like in production.
Testing
Testing
Testing
Seeing changes wasn’t enough—they had to experience them.
Seeing changes wasn’t enough—they had to experience them.
Seeing changes wasn’t enough—they had to experience them.
By integrating a testnet environment, developers could interact with the sign-in flow exactly as their users would—testing configurations, validating methods, and building confidence before going live.
By integrating a testnet environment, developers could interact with the sign-in flow exactly as their users would—testing configurations, validating methods, and building confidence before going live.
By integrating a testnet environment, developers could interact with the sign-in flow exactly as their users would—testing configurations, validating methods, and building confidence before going live.
Feedback
Feedback
Feedback
Through conversations with my CTO and PM, we found opportunities to simplify—without sacrificing flexibility.
Through conversations with my CTO and PM, we found opportunities to simplify—without sacrificing flexibility.
Through conversations with my CTO and PM, we found opportunities to simplify—without sacrificing flexibility.
I originally approached the project with a mindset of offering total customization. But as feedback came in, I realized too much choice can lead to hesitation.
So I started making the defaults smarter—surfacing the most common configurations first, while still giving teams room to adapt things to their needs.
I originally approached the project with a mindset of offering total customization. But as feedback came in, I realized too much choice can lead to hesitation.
So I started making the defaults smarter—surfacing the most common configurations first, while still giving teams room to adapt things to their needs.
I originally approached the project with a mindset of offering total customization. But as feedback came in, I realized too much choice can lead to hesitation.
So I started making the defaults smarter—surfacing the most common configurations first, while still giving teams room to adapt things to their needs.
View previous
View previous
View previous
I simplified the interaction without removing functionality by using progressive disclosure—feature remains available for users who need it, but is intentionally tucked away to prevent overwhelming the experience.
I simplified the interaction without removing functionality by using progressive disclosure—feature remains available for users who need it, but is intentionally tucked away to prevent overwhelming the experience.
Retrospective
Retrospective
Retrospective
The project was ultimately sunset as the company’s mission and objectives pivoted, redirecting resources to align with new priorities.
Despite this, the work laid a strong foundation and provided valuable insights for future initiatives.
The project was ultimately sunset as the company’s mission and objectives pivoted, redirecting resources to align with new priorities.
Despite this, the work laid a strong foundation and provided valuable insights for future initiatives.
The project was ultimately sunset as the company’s mission and objectives pivoted, redirecting resources to align with new priorities.
Despite this, the work laid a strong foundation and provided valuable insights for future initiatives.
LEARNINGS
LEARNINGS
LEARNINGS
Driving meaningful conversations
Driving meaningful conversations
Driving meaningful conversations
Building high-fidelity prototypes early in the process wasn’t just about validating ideas—it helped spark excitement among stakeholders and created momentum to move the project forward. It made abstract concepts tangible, leading to faster buy-ins from both leadership and engineering teams.
Building high-fidelity prototypes early in the process wasn’t just about validating ideas—it helped spark excitement among stakeholders and created momentum to move the project forward. It made abstract concepts tangible, leading to faster buy-ins from both leadership and engineering teams.
Building high-fidelity prototypes early in the process wasn’t just about validating ideas—it helped spark excitement among stakeholders and created momentum to move the project forward. It made abstract concepts tangible, leading to faster buy-ins from both leadership and engineering teams.
Clarity through focus
Clarity through focus
Clarity through focus
Instead of overloading the design with endless options, I learned the value of focusing on the core behaviors I wanted to drive. Simplifying decisions and tailoring the experience to specific goals created a more impactful and intuitive solution.
Instead of overloading the design with endless options, I learned the value of focusing on the core behaviors I wanted to drive. Simplifying decisions and tailoring the experience to specific goals created a more impactful and intuitive solution.
Instead of overloading the design with endless options, I learned the value of focusing on the core behaviors I wanted to drive. Simplifying decisions and tailoring the experience to specific goals created a more impactful and intuitive solution.
Collaborative design is key
Collaborative design is key
Collaborative design is key
Regular discussions with the CTO, PM, and engineers revealed opportunities to streamline the product further. Involving cross-functional teams early ensured alignment and helped shape the project to meet both technical and business goals.
Regular discussions with the CTO, PM, and engineers revealed opportunities to streamline the product further. Involving cross-functional teams early ensured alignment and helped shape the project to meet both technical and business goals.
Regular discussions with the CTO, PM, and engineers revealed opportunities to streamline the product further. Involving cross-functional teams early ensured alignment and helped shape the project to meet both technical and business goals.
Adaptability is crucial
Adaptability is crucial
Adaptability is crucial
When company priorities shifted, this project demonstrated the importance of designing in a way that can be repurposed or provide value beyond its original intent. Even projects that don’t ship fully can drive future initiatives.
When company priorities shifted, this project demonstrated the importance of designing in a way that can be repurposed or provide value beyond its original intent. Even projects that don’t ship fully can drive future initiatives.
When company priorities shifted, this project demonstrated the importance of designing in a way that can be repurposed or provide value beyond its original intent. Even projects that don’t ship fully can drive future initiatives.