{% include image.html image = "/assets/images/guide/designing-products/common-user-flows/onboarding.jpg" retina = "/assets/images/guide/designing-products/common-user-flows/onboarding@2x.jpg" alt-text = "" width = 100 height = 100 layout = "float-left" %} Bitcoin is complex, and so it is recommended to think through and carefully shape the first experience users have in your product. Without being overwhelming or getting into too much detail, this user flow should explain core concepts and features that allow users to create mental models on how they will use the application. Onboarding may be purely informational based on the content, but it also includes an initial setup that helps personalize the software towards the users' specific needs and context. After onboarding, users are mostly on their own, so the goal is to leave users with a clear idea of achieving what they came for. The example screens below from the [Muun](https://muun.com/) iOS wallet (taken January 2021) use several different methods: 1. Guide the user through information and setup one step at a time 1. Offer carousels of information users can choose to read (or skip) 1. Provide simple prompts of key actions 1. Confirm users are aware of their responsibilities You can find more screenshots [here](https://www.figma.com/file/rPyJ0Y8xg0kN4FrHFCeDRg/Muun-wallet?node-id=1%3A40).

{% include picture.html image = "/assets/images/guide/designing-products/common-user-flows/muun-onboarding-1.png" retina = "/assets/images/guide/designing-products/common-user-flows/muun-onboarding-1@2x.png" alt-text = "Muun iOS app cover screen" caption = "Cover screen for new users." width = 250 height = 541 layout = "shadow" %} {% include picture.html image = "/assets/images/guide/designing-products/common-user-flows/muun-onboarding-2.png" retina = "/assets/images/guide/designing-products/common-user-flows/muun-onboarding-2@2x.png" alt-text = "Pin entry screen" caption = "Choosing a PIN for security." width = 250 height = 541 layout = "shadow" %} {% include picture.html image = "/assets/images/guide/designing-products/common-user-flows/muun-onboarding-3.png" retina = "/assets/images/guide/designing-products/common-user-flows/muun-onboarding-3@2x.png" alt-text = "Confirmation screen that a wallet was created" caption = "Letting users know that a wallet was successfully created." width = 250 height = 541 layout = "shadow" %} {% include picture.html image = "/assets/images/guide/designing-products/common-user-flows/muun-onboarding-4.png" retina = "/assets/images/guide/designing-products/common-user-flows/muun-onboarding-4@2x.png" alt-text = "Home screen" caption = "The home screen with a prompt to back up the wallet." width = 250 height = 541 layout = "shadow" %} {% include picture.html image = "/assets/images/guide/designing-products/common-user-flows/muun-onboarding-5.png" retina = "/assets/images/guide/designing-products/common-user-flows/muun-onboarding-5@2x.png" alt-text = "Security center" caption = "The security center guides users through different backup options." width = 250 height = 541 layout = "shadow" %} {% include picture.html image = "/assets/images/guide/designing-products/common-user-flows/muun-onboarding-6.png" retina = "/assets/images/guide/designing-products/common-user-flows/muun-onboarding-6@2x.png" alt-text = "Information about the emergency kit backup option" caption = "An instructional screen to inform users about the security option they are about to set up." width = 250 height = 541 layout = "shadow" %} {% include picture.html image = "/assets/images/guide/designing-products/common-user-flows/muun-onboarding-7.png" retina = "/assets/images/guide/designing-products/common-user-flows/muun-onboarding-7@2x.png" alt-text = "Starting the backup process" caption = "Another informational screen for the manual backup option." width = 250 height = 541 layout = "shadow" %} {% include picture.html image = "/assets/images/guide/designing-products/common-user-flows/muun-onboarding-8.png" retina = "/assets/images/guide/designing-products/common-user-flows/muun-onboarding-8@2x.png" alt-text = "Asking users to write down their recovery code" caption = "A screen that requests users to copy their recovery code." width = 250 height = 541 layout = "shadow" %} {% include picture.html image = "/assets/images/guide/designing-products/common-user-flows/muun-onboarding-9.png" retina = "/assets/images/guide/designing-products/common-user-flows/muun-onboarding-9@2x.png" alt-text = "Ensuring users understand their responsibility in the security mechanisms of the application" caption = "Confirming that users understand their responsibility in the security mechanisms of the app." width = 250 height = 541 layout = "shadow" %} {% include picture.html image = "/assets/images/guide/designing-products/common-user-flows/muun-onboarding-10.png" retina = "/assets/images/guide/designing-products/common-user-flows/muun-onboarding-10@2x.png" alt-text = "Success screen" caption = "Giving users confirmation that the app is set up properly." width = 250 height = 541 layout = "shadow" %}

{% include image.html image = "/assets/images/guide/designing-products/common-user-flows/secure-wallet.jpg" retina = "/assets/images/guide/designing-products/common-user-flows/secure-wallet@2x.jpg" alt-text = "" width = 100 height = 100 layout = "float-left" %} Like fiat currencies, securely storing funds can be as simple as storing some coins in your pocket or highly complex with multiple banks’ safety deposit boxes. For self-custodial wallets, all of this is in the users’ hands, although wallet software ideally provides guidelines and support to more easily follow best practices. See also, the [Private key management](/guide/private-key-management/introduction/) section and [Protecting a wallet](/guide/onboarding/protecting-a-wallet/).

{% include image.html image = "/assets/images/guide/designing-products/common-user-flows/import-wallet.jpg" retina = "/assets/images/guide/designing-products/common-user-flows/import-wallet@2x.jpg" alt-text = "" width = 100 height = 100 layout = "float-left" %} If the user is in possession of the [recovery phrase](/guide/glossary/#recovery-phrase) for a bitcoin wallet, they should be able to import it into any application that supports the same standards. Some technical caveats apply, generally users are best advised to attempt recovery of a wallet with the same application as the wallet was created with for full compatibility. See also, [Wallet interoperability](/guide/designing-products/interoperability/) and [Restoring a wallet](/guide/onboarding/restoring-a-wallet/).

{% include image.html image = "/assets/images/guide/designing-products/common-user-flows/sending-ui-basic.png" retina = "/assets/images/guide/designing-products/common-user-flows/sending-ui-basic@2x.png" alt-text = "Example of a basic send screen" caption = "A UI for sending bitcoin with just the basic information ([source](https://www.figma.com/file/VB3GQdAnhl8yta44DY3PSV/Bitcoin-Wallet-UI-Kit?node-id=1374%3A33577))." width = 400 height = 243 layout = "shadow" %} {% include image.html image = "/assets/images/guide/designing-products/common-user-flows/sending-ui-complex.png" retina = "/assets/images/guide/designing-products/common-user-flows/sending-ui-complex@2x.png" alt-text = "Example of a complex send screen" caption = "An overly complex interface with advanced send options ([source](https://www.figma.com/file/VB3GQdAnhl8yta44DY3PSV/Bitcoin-Wallet-UI-Kit?node-id=1374%3A33792))." width = 400 height = 690 layout = "shadow" %}

{% include image.html image = "/assets/images/guide/designing-products/common-user-flows/receiving-ui-example-enter-info.png" retina = "/assets/images/guide/designing-products/common-user-flows/receiving-ui-example-enter-info@2x.png" alt-text = "Example interface for entering payment request information." caption = "A payment request starts with entering invoice information." width = 400 height = 276 layout = "shadow" %} {% include image.html image = "/assets/images/guide/designing-products/common-user-flows/receiving-ui-example-share-request.png" retina = "/assets/images/guide/designing-products/common-user-flows/receiving-ui-example-share-request@2x.png" alt-text = "Example interface for sharing a payment request." caption = "Then the payment request needs to be shared with the payer." width = 400 height = 260 layout = "shadow" %}

{% include image.html image = "/assets/images/guide/designing-products/common-user-flows/receive-notification.jpg" retina = "/assets/images/guide/designing-products/common-user-flows/receive-notification@2x.jpg" alt-text = "Smartphone notification about an incoming transaction" width = 400 height = 158 layout = "float-right" %} A user may also want to check in and see if any previous requests have not been completed yet. This is easily possible if the user has initiated all requests on the same wallet and used a new address for each one. In this case, a request can be considered fulfilled if at least one payment has been received with the total amount the user asked for. It is not as clear if addresses are getting re-used (how to tell which payment was for which purpose?) or the request has been made with another wallet (as this metadata is not stored and synced via the bitcoin network). On the lightning network, receiving bitcoin requires an invoice. This makes it easy to track if payments have been completed or not.

{% include image.html image = "/assets/images/guide/designing-products/common-user-flows/transactions.jpg" retina = "/assets/images/guide/designing-products/common-user-flows/transactions@2x.jpg" alt-text = "" width = 100 height = 100 layout = "float-left" %} While the bitcoin network only stores transactions, a wallet is more than just a list of bitcoin sent and received. Behind each transaction is an interaction between people and companies (or software). To make sense and work with transactions, they typically need to apply an organizational system. This could be a list of [contacts]({{ '/guide/payments/contacts/' | relative_url }}) they assign addresses to, tags like "allowance" or "business expenses," or simply describing what a transaction was for.

{% include image.html image = "/assets/images/guide/designing-products/common-user-flows/migrate.jpg" retina = "/assets/images/guide/designing-products/common-user-flows/migrate@2x.jpg" alt-text = "" width = 100 height = 100 layout = "float-left" %} There are several reasons a user might want to switch wallets. A different wallet application might have features they need, or be better supported than the one they originally created the bitcoin wallet with. Importing the wallet with the recovery phrase into the new application should be possible, and will be free from fees as no transfer of funds is happening. The owner may want to increase the security of their wallet, either by using a single-key wallet with a [passphrase](/guide/glossary/#passphrase), or a [multi-key](/guide/private-key-management/multi-key/) wallet. As both of these include transferring funds to a new bitcoin wallet, there will be fees to pay. In the worst-case scenario, the wallet might have been compromised, and funds should be saved by sending them all to a different bitcoin wallet. Whatever the reason, the import and backup of wallets is a vital function for users that applications should support. While it is easy to send all funds to a new address, additional meta and state data stored in wallet applications also need to be considered for full compatibility. It's not recommended to switch wallets that include funds on the lightning network, as standards for backing up channel state have yet to emerge. See also, [Wallet interoperability](/guide/designing-products/interoperability/).

{% include image.html image = "/assets/images/guide/designing-products/common-user-flows/sweep.jpg" retina = "/assets/images/guide/designing-products/common-user-flows/sweep@2x.jpg" alt-text = "" width = 100 height = 100 layout = "float-left" %} This is similar to exchanging many small coins into bills (like exchanging 100 one-dollar bills to a single one-hundred dollar bill). Dust refers to small amounts of unspent bitcoin in a wallet. If they add up, future transaction fees can become costly. That's because fees are partially based on transaction size. This size increases with every output from a previous transaction that is included. Sweeping dust helps by making a transaction to yourself that turns the many outputs with small amounts into a single output with a larger amount. This is typically done when few transactions are being done on the bitcoin network, which is another factor in fee calculation (senders choose how much they want to pay in fees, and the network prioritizes transactions that pay more).

{% include image.html image = "/assets/images/guide/designing-products/common-user-flows/resolving-problems.jpg" retina = "/assets/images/guide/designing-products/common-user-flows/resolving-problems@2x.jpg" alt-text = "" width = 100 height = 100 layout = "float-left" %} This can be a tricky experience to address. For one, non-custodial cryptocurrency management by nature places a lot of responsibility on the user. This also puts much of the burden of solving problems on users. The second aspect is that open-source software typically relies on online documentation and forums for "customer service." Ideally, the software helps prevent errors as much as possible through validating user input and requiring extra approvals for impactful actions. When this is not possible, though, and errors do occur, they should be communicated as clearly as possible.