Domain: Fintech · Crypto · Security https://www.jnet-secure.com/

I created a clear, secure onboarding flow that became part of the fundraising pitch.

UX Metrics

User Activation +18% CR +1%

Impact

• 18% user activation via onboarding (from registration to the first transaction)
• Advanced users adopted the wallet as part of their business operations
• Raised investment for the product

My Activities

Requirements workshop Competitor analysis CJM User scenario User flow UI kit Visual accessibility Developer handoff Knowledge transfer Sprint design reviews (12 mo) Design QA & product advisory

Context

When I joined, nothing existed yet — just a card and an idea. GNET was a small Los Gatos startup with a big ambition:

A crypto wallet paired with a physical security card that you tap on your phone to approve sensitive actions.

The founder came from hardware. He understood microchips, NFC, and secure elements inside out, but the digital product didn’t exist:

• No screens
• No user journey
• No onboarding
• No architecture

Just a card that could talk to a phone.

I became the first designer, brought in to turn that idea into something real people could use.

Crypto onboarding is where beginners usually fail

I wasn’t a crypto expert when I joined.

And maybe that helped — because I immediately saw what new users struggle with:

• seed phrases feel abstract
• security steps are rushed
• people skip what they don’t understand
• and later discover they can’t recover their wallet

It had to teach, not just ask users to agree.

In crypto, a single skipped step can mean losing access forever.

I knew the onboarding couldn’t be a “next-next-finish.”

Designing onboarding

I built a clear, quiet, reassuring flow that walks users through the heart of crypto safety:

• We added short videos and micro-explanations that demystified the scary parts.
• And we made the UI behave safely by default — blocking screenshots, clipboard copying, and cloud sync.

My goal wasn’t to show off security.

It was to make a beginner feel:

I can do this safely. I understand what’s happening.

Four-step onboarding that actually explains security

Step 1 - Define what a recovery seed is (before users commit)

• Explains that a recovery seed is the only way to restore access
• Clarifies the 12 vs 24-word tradeoff: more words = stronger protection
• Gives beginners enough context to choose confidently, not guess

Step 2 - Make the consequences impossible to ignore

• Acknowledgement checks turn “I skimmed it” into real understanding
• Reinforces the two irreversible risks: losing the seed = lost access, sharing it = stolen funds
• Prevents users from treating security as optional onboarding fluff

Step 3 - Enforce offline storage and reduce exposure

• Seed is hidden by default to avoid accidental leaks and shoulder-surfing
• Strong guidance against screenshots/cloud storage (high-risk habits)
• Screenshot blocking/regeneration protects users from a common mistake with permanent impact
• Structured seed layout reduces order/formatting errors seen in competitor pat