
Web3 onboarding UX: from first visit to first transaction
Imran KhanNovember 19, 202613 min read

table of contents
Picture a first-time visitor who arrives curious, hits a screen asking for a wallet they don't have, and goes back to what they were doing. That visitor never reached the product. This guide is about not losing them there.
This guide is about the road from first visit to first completed action. We cover what onboarding is, the four ways a person can get in, the order of the journey, the wallet and recovery choices, gas, funding, how to word risk, sign-in accessibility, and how to measure it.
One thing up front. We're a design studio, not a wallet vendor, and we haven't designed a wallet or an embedded-wallet flow. We have designed a short onboarding for a payments app, Dino, and a Web3 product, Reputable, that doesn't ask for a wallet on day one. We use them for what they show, and rely on linked sources for the rest. Every outside page was read on 19 November 2026. Nothing here is legal or financial advice.
The short version
- The journey ends at the first thing the person came to do, not at account creation.
- There are four ways in: connect a wallet you already have, sign in with email or social and get an embedded wallet, use a passkey-based smart wallet, or use the product with no wallet at first. Offer more than one.
- Put the wallet as late as the product allows. Alliance DAO's essay, which we quote below, makes that point for games.
- Tell people how recovery works before they need it, in plain words, at the moment they can still act on it.
- Decide who pays for gas, and what stops abuse, before you design the screen.
- Keep the risk wording even when the technology disappears. A smoother door shouldn't hide what's behind it.
- Make sign-in work for everyone: don't block paste, and don't make people remember a puzzle.
- Measure time to first action, step by step, and fix the biggest gap first.
What onboarding is, and where it stops
It isn't the sign-up form. It's everything between "I opened this" and "I did the thing I came for." For a swap app that's a first swap. For a game it's a first match. For a reputation product like Reputable it's seeing your own profile.
That definition matters because it changes what you count. Sequence's guide describes a typical Web3 flow as five steps, including installing a wallet extension and storing a 12-word seed phrase, before the person reaches the product. Count those steps. Then count how many of them help the person do what they came for. The answer is usually none.
We wrote about wallet screens and signing in our Web3 UX guide, and about the app's screens in our crypto app design guide. This guide sits in front of both: the first few minutes.
The four ways in
Every sign-in choice you make is one of four doors. Most products need two of them.
| Door | What the person does | What to be honest about |
|---|---|---|
| Connect a wallet | Picks a wallet they already have and approves | Fast for people who have one, a dead end for everyone else |
| Email or social sign-in | Signs in with an account they know and gets an embedded wallet | Someone else's infrastructure holds part of the setup |
| Passkey smart wallet | Approves with a fingerprint, face or PIN on their device | Recovery depends on where the passkey is synced |
| No wallet yet | Uses the product in a limited way first | You need a clear moment where a wallet becomes necessary |
Connect a wallet
This is the original door, and it's still the right one for people who already hold crypto. Don't remove it to make the product look friendlier. We'd expect a person with a wallet who can't find the connect button to leave as quickly as a person without one who is told to install an extension.
Show it as one of the choices, not the only one, and don't open the wallet prompt until the person clicks. Our website design guide gives the reasons for keeping it off the first screen.
Email or social sign-in, with an embedded wallet
Here the person signs in with something they already use, and the product creates a wallet for them behind the scenes. Privy's docs describe its embedded wallets as non-custodial, and its architecture page says the wallet's key is split into two shares: one inside a trusted execution environment, and one encrypted by Privy and released only when valid authentication is presented. Both are needed to rebuild the key.
That's one vendor's description of its own system. Every vendor works differently, and the page we read doesn't cover key export or recovery. So before you pick one, ask four things in writing: who can recover this wallet if the person loses their login, can the person take their key out, what happens to their wallet if you stop using the vendor, and what's the vendor's own account of its security.
A passkey-based smart wallet
A passkey is, in the FIDO Alliance's words, an authentication credential based on FIDO standards. The person approves a sign-in the way they unlock their device, with a fingerprint, a face scan, a PIN or a pattern. The same page calls passkeys phishing-resistant and says they can be synced end-to-end encrypted across a person's devices.
Coinbase's developer docs use this for wallets. They say one passkey works across every Base-enabled app with no installs, seed phrases or network switches, and that people hold their own keys. The page doesn't cover recovery, so check that separately.
People are getting used to passkeys outside crypto. A 2024 survey cited on the FIDO Alliance's passkeys page found that 53% of people had turned them on for at least one account. That's a useful point for design: the sign-in feels familiar even if the wallet behind it isn't.
No wallet yet
Some products don't need a wallet until something is owned, paid for or signed. Reputable is an example. Developers sign in with GitHub and claim a profile that's already built from their public work, and the case study describes no wallet step. We're not saying every product can do this. We're saying you should check whether yours really needs the wallet at the start, because every step you remove is one fewer place to lose someone.
Order the journey: value first, wallet later
Alliance DAO's essay on onboarding says friction should arrive as late as possible. It's written about games, but the idea holds up. Its example is the tutorial round in Marvel Snap, which, the author says, includes only half of the game's mechanics and allows one valid place to put a card. The person succeeds before they've learned anything difficult.
For a Web3 product, a good order looks like this:
- Show the product working. A real screen, real data, or a demo with sample data.
- Let them do one small thing without a wallet, if the product allows it.
- Ask for identity or a wallet when they choose something that needs it, and say why in a sentence.
- Create the wallet or connect it.
- Explain recovery while they can still act on it.
- Make the first real action.
The wallet is step four here, not step one. That's our view: the hardest question shouldn't be the first one.
Nielsen Norman Group's guidance on progressive disclosure fits here. It says to defer advanced or rarely used features to a secondary screen, and that designs with more than two levels of disclosure usually have low usability. For onboarding that means two layers at most: the simple path in front, and "advanced options" behind one link.
The wallet, and the seed phrase
If your product creates a wallet, the person needs to understand three things, and not more.
What it is. ethereum.org describes a wallet as an app or device that lets you hold, send and receive ETH and other tokens, and sign in to apps. Use that level of plainness. "Your account on this app" is enough for the first screen.
What controls it. An account made of keys is, in ethereum.org's accounts documentation, controlled by anyone with the private keys. That's the reason seed phrases exist, and the reason they scare people. ethereum.org's own wallet page says the phrase must be written down and is the only way to recover the wallet, and that transactions can't be reversed.
What happens if they lose access. This is the screen most onboarding skips, and we cover it in the next section.
If you do show a seed phrase, three things help. Show it once, at a moment the person isn't rushing. Say in one sentence what it's for. And don't ask them to prove they saved it in a way that feels like an exam. If you use an embedded or smart wallet, you may not show one at all. Then recovery becomes your design problem, not the user's.
Recovery is a story told in advance
Seed phrases, social recovery, passkey sync and vendor recovery are all answers to the same question: what happens when the person loses their phone? The worst time to find out is after.
We'd write the recovery explanation as three short lines and place it right after the wallet exists:
- what you can get back, and how;
- what you can't get back, if anything;
- the one thing the person should do today, such as adding a second sign-in method.
If you use a vendor, put their limits in your words. If the vendor holds a share of a key and you can't change that, say so in the help text. In our view, a limit people were told about on day one is easier to accept than one they find at the worst moment.
Alliance's essay offers one more idea worth keeping: a low-stakes wallet for play, separate from the one that holds anything valuable. It presents this as an emerging pattern rather than a proven one, so treat it as something to test, not a rule.
The first transaction
Most products reach the first transaction with a person who has never signed anything. A few choices decide whether they finish.
Gas: decide who pays
On Ethereum, ERC-4337 describes account abstraction that works without changing the base protocol, and defines a paymaster as a helper contract that agrees to pay for the transaction instead of the sender. EIP-7702 lets ordinary accounts set code, and its motivation section lists batching and sponsorship as uses. Both are marked Final.
Those are tools. The design question is what you'll sponsor, for whom, and what stops someone from draining the budget. We'd write that down before drawing a screen:
- Which actions are free for the person, and which aren't.
- How many free actions a new person gets.
- What the screen says when the allowance runs out, in plain words and with a next step.
- Who sees the cost in the end: you, the person, or a partner.
The vendor guides we read mostly present sponsored gas as a feature and say little about who pays or what stops abuse. That's a business decision, and the screen has to tell the truth about it.
One screen, one action
Dino, a group payments app we redesigned, has a line in its case study that we'd use for any first transaction: "every number says whose money it is, and every screen has one obvious thing to do next." For a first signing screen that means one action, one amount, one sentence about what will change, and a plain name for what the person is approving.
Show what will happen before the wallet shows what will be signed. Say how much it will cost, and whether it can be reversed. ethereum.org says transactions can't be reversed, so say so where it matters.
When it fails
Say what happened, whether money moved, and what to try next, in that order. 925Studios and Sequence both cover error states in their guides. When it's true, "Nothing was sent" is the line a person is looking for, so put it first. Test every error message on someone who has never seen a blockchain.
Funding the account
Many people arrive with no crypto at all. That's a funding problem, not a wallet problem, and it deserves its own moment.
We'd ask for funding at the point of need, not before. If the first action needs money, say how much, offer the ways to add it, and show the balance in the currency the person thinks in. Dino's deposit screen is built from an amount, quick picks and the bank account the money comes from, which is about as little as a funding step can ask for. Dino isn't Web3, so treat it as a shape to copy, not proof that it works for crypto.
If your product takes a card or bank transfer, name the provider and where the fee goes. If it takes a bridge, say which chain the money lands on. Don't hide the cost in a later screen.
Wording risk when the door gets smoother
KuCoin's own article on onboarding makes a point that applies to every product with a smooth entrance: as onboarding becomes invisible, people can overlook that the products behind it are risky. It lists the risks of staking, including counterparty, smart contract and custody risk, and says disclosures need to stay in the flow.
We'd go further. A smooth onboarding that hides what's behind it is a design fault, not an achievement. Our advice:
- Say what the product does with money, once, in plain words, before the first action.
- Give each risk one line, near the action it applies to, not in a footer.
- Don't use a countdown, a streak or a "claim now" button on a money step.
- If you operate in a regulated market, ask a lawyer. We're not lawyers.
Sign-in that everyone can use
Web3 sign-in is full of tests: typing a code, copying a long address, remembering a phrase. WCAG 2.2 has a rule about this. Success criterion 3.3.8, Accessible Authentication (Minimum), says a cognitive function test, such as remembering a password or solving a puzzle, can't be required at any step of an authentication process unless that step offers an alternative, a helping mechanism, object recognition or personal content.
In practice, for onboarding:
- Don't block paste into code fields. The W3C page says copy and paste can be relied on to avoid transcription.
- Let password managers and autofill work.
- Offer passkeys or another device-based option next to codes.
- Don't ask people to retype a seed phrase from memory as the only way in.
Treat this as a floor, not a ceiling.
A worked example: three short screens
Dino is not a Web3 product. We include it because it shows how short a sign-up can be when nothing in it is optional trivia. The case study describes the new flow as three short screens: sign up, a six-digit code, and you are in. The app then leads with the user's own balance, then the group card they pay from. That's the same order we recommend above: show the product, then ask for what you need.
The first screen, in the picture earlier, is a welcome card with one line about what the app does, a Next button and a Skip link. The case study then describes "two kinds of balance, never in the same place without a label."
The Reputable case study is the other half of the point. Reputable is a Web3 product, and the onboarding it describes is GitHub sign-in and claiming a profile. Developers claim existing profiles rather than create new ones. In the first three months after launch, the case study reports 9.4k profiles claimed. We haven't published how many came through the sign-in step, so we don't claim that.
The honest summary: we've designed a short onboarding and a no-wallet entry. We haven't designed a wallet flow. If you need one, ask us what we'd do and how we'd test it, and weigh that against agencies that have shipped them. Our list of Web3 design agencies shows who else does this.
How to measure it
Sequence's guide recommends measuring time to first action and using analytics to find where people drop off. We agree, and we'd add a few specifics.
| Measure | Question it answers |
|---|---|
| Time to first action | How long until they do what they came for? |
| Step-by-step completion | Which step loses the most people? |
| Return after a day | Did the first action stick? |
Add one more: test it with five people who have never used crypto, and watch without helping. Write down every place they stop. That list is your roadmap, and it will be shorter and more specific than any benchmark.
FAQ
It's everything that happens between a person first opening a Web3 product and finishing the first thing they came to do. It usually includes sign-in, getting a wallet, recovery set-up, funding and a first action.
The guides we read name wallet installation, seed phrases, gas fees and jargon. Their percentages don't come with sources we could check, so we leave them out. Test with real people and measure your own steps.
Not always. Some products let people look around, or do something small, before a wallet is needed. The question is whether your product really needs one at the start.
A wallet that the product creates for a person, usually after they sign in with email or a social account. Vendors describe them differently, so ask who can recover the wallet and whether the person can export their key.
It lets accounts be controlled by code, which makes things like paying fees on someone's behalf possible. ERC-4337 defines this without changing Ethereum's base protocol, and EIP-7702 lets ordinary accounts set code. Both are marked Final. For onboarding, the practical effect is that a person may not need to hold the network token before their first action.
They remove the phrase to write down, and the FIDO Alliance calls them phishing-resistant. But recovery depends on where the passkey is stored and synced, so design that explanation either way.
Hide the parts that don't help the person, such as chain names and network switches. Don't hide what they need to make a decision: what the action does, what it costs and whether it can be undone.
Measure time to first action for your product and compare it with itself over time. Dino's sign-up is three short screens, which shows what's possible for a payments app. It isn't a Web3 benchmark.
Say what happened, whether money moved, and what to try next, in that order. Put "nothing was sent" first when it's true.
We can design the flow, the screens and the tests. We've designed a short onboarding for Dino and a Web3 product in Reputable. We haven't designed a wallet, so ask us for the exact work you need.
If you're building a Web3 product and want the first few minutes designed so people reach the first action, book a call. Our UI/UX design services cover onboarding from the first screen to the test with real users. Our pricing page shows how we work.
About the author
Imran Khan, Founder & Creative Head
15 years of industry experienceFormer Head of Design at Day TranslationsFormer Creative Lead at SupersideWork at Superside for brands including Meta, Red Bull and Ray-Ban

related articles
Book a call
Pick a time that suits you
Get in touch
Let’s build something amazing together
Let’s build somethingamazing together
For product, interface and web-system work that needs clear direction and careful execution.




