Muun — Onboarding

Positioning reviewNew

2 high3 medium1 low
Positioning review
Asks who the wallet appears built for and what it is betting people choose it for, judged from the product surface itself rather than its marketing. Doesn't examine step-by-step friction inside a flow, and makes no claims about the wallet's real user base.

Generated automatically and not manually verified. Findings quote the screens they reference so they can be checked against the originals.

Summary

Muun's onboarding is four screens, two of which are a PIN, and its entire positioning is one line: "Self-custodial wallet for bitcoin and lightning." That sentence describes a category rather than a reason, and Phoenix could print it unedited — so the moment where Muun should be distinguishing itself is the moment it is least distinguishable. Meanwhile the genuinely distinctive thing about Muun, that you run a Lightning wallet without ever meeting a channel or a liquidity decision, is observable only by noticing what its four-row Settings screen doesn't contain. Muun has a real position; its onboarding declines to take it, and instead spends its only safety statement on a PIN.

Findings

Six findings, most severe first. Every observed string is quoted from the screenshot named in the same entry.

Muun against Phoenix

Phoenix is the yardstick here, not a co-subject: the question is what Muun's choices look like when something adjacent is held up beside them. Both are self-custodial Lightning-first mobile wallets, and both were captured in the Gallery on 2025-10-23.

Muun Phoenix
What onboarding claims One line: "Self-custodial wallet for bitcoin and lightning." Three screens: "easy and safe" → "Bitcoin supercharged" → "Your key, your bitcoins"
Self-custody disclosed before the wallet exists No Yes — a dedicated screen (03-onboarding-3rd-screen)
Screens to a working wallet 4 (two are PIN entry) 5 (three are intro)
Device lock during onboarding Yes — PIN, mandatory, unskippable in these captures No — App access lives in Settings
First balance the user sees "0.00 BTC" over "0.00 USD" "0 sat", no fiat
Lightning machinery exposed One toggle, "Turbo channels" Channel management, Add liquidity, Electrum server, Tor, and a six-screen liquidity flow
Backed up when onboarding ends No — home-screen banner plus a Security Center tab No — a warning row in Settings and a warning message on the wallet screen

Where they clearly differ. Muun is built on the bet that the user should never see the machine; Phoenix is built on the bet that the user should be able to reach it. Muun's four-row Settings screen and Phoenix's Channel management / Add liquidity / Electrum server / Tor list are not two points on a spectrum, they are opposite answers. Muun also wins the first-balance moment outright: "0.00 BTC / 0.00 USD" is legible to someone who has never held bitcoin, where Phoenix's "0 sat" introduces a unit no screen has explained. And Muun's Security Center is a top-level destination with a three-step progress bar, against Phoenix's single Settings row.

Where they are interchangeable, which is the finding. The two screens that decide whether someone picks Muun — the welcome screen and the moment onboarding ends — are the two where the wallets are hardest to tell apart. Both lead on self-custody plus Lightning. Both put "create" and "restore" side by side with near-identical labels. Both end onboarding with an unbacked-up wallet and delegate recovery to a persistent warning on the home screen. Phoenix at least attempts a mechanism claim, however badly ("Phoenix uses payment channels to make Bitcoin fast and private"); Muun attempts none, so on the specific question of why this one, Muun currently offers strictly less than the wallet whose philosophy it opposes.

Who this appears to be built for

Read from the product surface alone: Muun's onboarding is built for someone who has already decided they want self-custody and does not want to be talked to about it. It explains nothing, assumes "self-custodial" and "lightning" are known words, offers restore as a peer to creation on the first screen, and gets out of the way in four taps. That is Dave's flow, not Priya's — except that Dave's other requirement, being able to reach fee control, node choice and coin control, is a requirement Muun's Settings screen deliberately cannot meet. So the flow is calibrated for a user Muun has no intention of serving past onboarding.

Everything downstream points at Priya instead: fiat alongside BTC by default, a Security Center that numbers backup 1–2–3, an Emergency Kit, no channel controls to misconfigure. The mismatch is not that Muun targets the wrong person — it is that the onboarding is pitched at a sophistication level the rest of the app doesn't assume, and the one line of copy that could correct that is spent on a category label. Marisol is not addressed anywhere in this flow.

Confidence: high that the product is built for a low-management, low-vocabulary audience — the Settings screen makes that unambiguous. Lower confidence on what Muun intends to be chosen for, precisely because the onboarding never argues for anything.

Findings

  1. Welcome screen with wallet creation options
    Welcome screen with wallet creation options
    Wallet creation success screen with astronaut illustration
    Wallet creation success screen with astronaut illustration
    1highTrust erosion
    Self-custodial wallet for bitcoin and lightning.

    "Self-custodial" is the entirety of Muun's positioning statement, and it is used as a category adjective on a screen that then goes straight to PIN entry. Nothing in the four-screen flow tells the user what self-custody costs them: that Muun cannot restore their access, and that until they do something about it, losing the phone loses the money. The flow instead closes on "You created a new wallet. Welcome to Muun!" — a completion claim over a wallet with no recovery method. The Design Guide's first-use page treats this as the one thing onboarding must not skip: users should be informed they cannot recover lost access, and "these caveats mustn't be hidden. Doing so may severely compromise their funds' safety, as their default assumptions and behaviors could potentially mimic how they typically use centralized applications." Phoenix spends a whole screen on exactly this before the wallet exists (`03-onboarding-3rd-screen`: "Phoenix is self-custodial. You take control."). Muun asserts the same property in one word and defers the consequence to a banner the user only meets after being congratulated.

    Suggested fix Cash the word out inside the flow. One line is enough, and the success modal is the natural place for it — replace the congratulation with the handoff: "Your wallet is yours alone. Muun can't restore it for you, so the next step is setting up a way to recover it." Don't spend the welcome screen's only sentence on a category name.

  2. PIN creation screen with numeric keypad
    PIN creation screen with numeric keypad
    Main wallet screen with zero balance and backup reminder
    Main wallet screen with zero balance and backup reminder
    2highConfusion
    Keep your wallet safe

    Half of Muun's onboarding is PIN entry, and the subtitle under "Create your PIN" is the flow's only statement about safety. A PIN protects this handset from someone holding it; it does nothing about the risk that actually ends wallets, which is losing the device. Muun knows this — the screen waiting on the other side of the flow says "Back up your wallet. Create a backup to never lose access to your wallet." So onboarding makes its single security promise about the mechanism carrying the least of the risk, and then immediately corrects itself. A newcomer of the kind this flow is otherwise pitched at finishes it believing the wallet is secured, which is the specific wrong belief self-custodial onboarding exists to prevent.

    Suggested fix Scope the claim to what the PIN does — "Protect this app on your phone" — and reserve wallet-safety language for recovery. If two of four onboarding screens are going to be a PIN, the flow can afford one screen on the thing the PIN doesn't cover.

  3. Welcome screen with wallet creation options
    Welcome screen with wallet creation options
    Settings screen with general and advanced options
    Settings screen with general and advanced options
    Lightning Network settings with turbo channels enabled
    Lightning Network settings with turbo channels enabled
    3mediumMissed opportunity
    The "ADVANCED SETTINGS" section contains one row, "Lightning Network"; the full Settings screen is "Bitcoin Unit / Bitcoin", "Main Currency / US Dollar", "Lightning Network", "Log out", "Version 0.7.2 (205)"

    The truest and most distinctive thing about Muun is visible only as an absence. Its entire settings surface is four rows, its "advanced" section is a single toggle, and nowhere in the app does a user meet a channel, a liquidity decision, a node choice or a fee policy. Phoenix's equivalent screen (`11-after-tapping-settings-icon-on-main-wallet-screen`) lists Channel management and Add liquidity under a FEES heading, plus Electrum server and Tor under PRIVACY & SECURITY, and devotes a whole flow to buying liquidity. These are opposite bets about what a Lightning wallet should ask of its owner, and Muun's is the more defensible one for a mass-market audience — but an absence cannot advertise itself, and Muun's one line of positioning is a sentence Phoenix could print unedited. Someone choosing between the two on their welcome screens has nothing to choose on.

    Suggested fix Say the negative claim out loud on the welcome screen, where the category label currently sits: "Bitcoin and Lightning in one balance. No channels, no liquidity, nothing to manage." That is both true of the product and unavailable to Phoenix, which is what a positioning line is supposed to be.

  4. Lightning Network settings with turbo channels enabled
    Lightning Network settings with turbo channels enabled
    4mediumConfusion
    Learn more about the trade-offs of turbo channels.

    Muun hides every other Lightning mechanic, then files this one under ADVANCED SETTINGS, defaults it on, and explains it with a link somewhere else. The screen states that a trade-off exists and declines to say what it is. For the audience the rest of the app is built for, "turbo channels" is undecodable and the toggle is unactionable; for a user who does know the term, being sent off-app for the trade-off is less than they came for. It is the sole survivor of a philosophy of not making users think about channels, and in its current form it serves neither end of the audience.

    Suggested fix Either state the trade-off inline in one sentence — what you gain, what you risk, what changes if you switch it off — or drop the control and make the choice on the user's behalf, consistent with every other Lightning decision Muun already makes for them.

  5. Receive screen with notification prompt for Bitcoin payments
    Receive screen with notification prompt for Bitcoin payments
    Main wallet screen with zero balance and backup reminder
    Main wallet screen with zero balance and backup reminder
    5mediumFriction
    Segmented control at the top of the Receive screen with two tabs, "Bitcoin" (selected) and "Lightning"

    Muun's best-delivered promise is on the wallet screen: one balance, "0.00 BTC" over "0.00 USD", with no on-chain/Lightning split anywhere in the frame — where Phoenix shows "0 sat" and keeps incoming on-chain funds in a separate swap-in wallet the user has to go find. Receive hands the distinction straight back. The tab pair is the topmost element on the screen, above the notification prompt, and the flow has given the user no basis for choosing between the two. Bitcoin is preselected, so there is a default — but the control is presented as a decision, and for a merchant with someone waiting it is a decision she has neither the grounds nor the time to make.

    Suggested fix Demote the choice. Lead with a single request that works for the common case and offer the other network as a secondary option on the same screen, rather than opening on a fork the user is not equipped to resolve.

  6. Wallet creation success screen with astronaut illustration
    Wallet creation success screen with astronaut illustration
    6lowMissed opportunity
    You created a new wallet. Welcome to Muun!

    The flow's one moment of brand personality — astronaut, flag, exclamation mark, "LET'S GO" — is spent declaring completion at the point where the wallet is least safe. The contradiction is literally rendered behind the dialog: a padlock icon and a bordered card sit dimmed under the overlay, in the same position as the wallet screen's "Back up your wallet" banner. The warmest screen in the flow is doing the least useful job available to it, and it is the last impression onboarding leaves.

    Suggested fix Keep the astronaut, change the job. Make the modal the handoff into recovery setup — "Your wallet is ready. One more step: set up a way to recover it." with the button reading "SET UP RECOVERY" — so the celebration marks something that is actually finished.

What's working

  • The four-screen flow is an asset, not a deficiency. welcome-screen-with-wallet-creation-options to wallet-creation-success-screen-with-astronaut-illustration is the shortest route to a self-custodial bitcoin-and-Lightning wallet in the Gallery. The fix for the disclosure gap is one screen or one rewritten modal, not an intro carousel.
  • "0.00 BTC" over "0.00 USD" on main-wallet-screen-with-zero-balance-and-backup-reminder, with a single balance and no on-chain/Lightning split in the frame. This is the clearest in-product expression of Muun's actual position, and it is doing that work silently. Protect it.
  • The Security Center is a top-level tab. security-center-showing-backup-options opens on "Your wallet is not backed up" with a red progress bar and three numbered methods. Muun's depth is real; it is simply all behind the onboarding rather than in it.
  • Settings restraint is a position, not an omission. Four rows and one advanced toggle is a coherent product decision that most Lightning wallets are unwilling to make.

Gaps in this review

  • This is inference from the product surface only. Nothing here is a claim about Muun's real users, market share, funding or strategy; the review reads what the screens choose to say and not say.
  • The "I ALREADY HAVE A WALLET" path is not captured. Given that the welcome screen gives restore equal billing, that flow likely carries positioning material this review can't see.
  • No funding or purchase path is in these captures. The Design Guide's first-use page asks that onboarding support both receiving existing bitcoin and buying new bitcoin; whether Muun offers the latter can't be determined from the Gallery screens.
  • The chat/support icon on the wallet screen is never opened. If Muun explains self-custody anywhere in-app, that is a plausible location.
  • The capture may be old. settings-screen-with-general-and-advanced-options reads "Version 0.7.2 (205)", and the wallet's Taproot screens are dated 2021-12-09, so the onboarding above may not match what ships today. Treat this as a baseline for the captured build.
  • The Phoenix comparison rests on captured screens too — its Settings screen is cut off below the ADVANCED heading, so its full advanced surface is larger than what this review counted, which strengthens rather than weakens the contrast.
  • Curated link. This flow's Design Guide link, https://bitcoin.design/guide/onboarding/first-use/, still returns 200 but only to serve a client-side redirect to https://bitcoin.design/guide/daily-spending-wallet/first-use/. Same issue the Phoenix report flagged, here in app/data/muun.json.

Carried forward

No prior report on muun + onboarding, so this run is the baseline. One thread does connect to the 2026-08-17 backup copy review: it found "Back up your wallet" overloaded as a label across four different things inside the backup flow. That overload starts one screen earlier than that review recorded — the phrase is already doing duty as the exit banner on main-wallet-screen-with-zero-balance-and-backup-reminder, which is the first thing a user sees when onboarding ends.