Fix/pr525 - Update ⚡️Onboarding - Create a wallet --> First use, for Lightning

guide/onboarding/backing-up-a-recovery-phrase.md

@@ -75,8 +75,8 @@ However, there may be times when it is necessary to use a manual backup alternat
 The next sections will look at some UI considerations for [automatic cloud backups]({{ '/guide/onboarding/backing-up-a-recovery-phrase/automatic-cloud-backup' | relative_url }}) and [manual backups]({{ 'guide/onboarding/backing-up-a-recovery-phrase/manual-backup/' | relative_url }}).
 
 {% include next-previous.html
-   previousUrl = "/guide/onboarding/creating-a-new-wallet/"
-   previousName = "Creating a new wallet"
+   previousUrl = "/guide/onboarding/first-use/"
+   previousName = "First use"
    nextUrl = "/guide/onboarding/backing-up-a-recovery-phrase/automatic-cloud-backup/"
    nextName = "Automatic cloud backups"
 %}

guide/onboarding/creating-a-new-wallet.md → guide/onboarding/first-use.md

@@ -1,10 +1,10 @@
 ---
 layout: guide
-title: Creating a new wallet
-description: Steps to take when creating a new wallet, and tips for a great user experience.
+title: First use
+description: Common tasks when using a wallet application for the first time.
 parent: Onboarding
 nav_order: 1
-permalink: /guide/onboarding/creating-a-new-wallet/
+permalink: /guide/onboarding/first-use/
 main_classes: -no-top-padding
 image: https://bitcoin.design/assets/images/guide/onboarding/creating-a-new-wallet/creating-a-new-wallet-preview.png
 ---
@@ -20,17 +20,26 @@ image: https://bitcoin.design/assets/images/guide/onboarding/creating-a-new-wall
    layout = "full-width"
 %}
 
-# Creating a new wallet
+# First use
 
-First, bitcoin [wallets]({{ 'guide/glossary/#wallet' | relative_url }}) are not analogous to their namesakes. Physical wallets are places to store physical currency, credit cards, IDs, and so on. Bitcoin wallets don't store bitcoin. However, the [self custodial]({{ 'guide/glossary/wallet/#non-custodial--custodial-wallet' | relative_url }})  nature of bitcoin wallets gives users full control of what they do with their bitcoin.
+There are a number of common tasks a user might want to achieve the first time they open a wallet application:
 
-Instead, a Bitcoin wallet contains the "private keys" to a users bitcoin. The bitcoin is located on the Bitcoin network that contains a public ledger similar in many ways to a spreadsheet with a record of everyone's transactions and balances. Private keys let users access bitcoin associated with those keys. A more suitable analogy for a Bitcoin wallet would be a keychain.
+- [Create a new wallet](/guide/onboarding/first-use/#creating-a-wallet), or
+- [Restore an existing wallet](/guide/onboarding/restoring-a-wallet/)
+- [Backup a wallet](/guide/onboarding/backing-up-a-recovery-phrase/)
+- [Fund a wallet](/guide/onboarding/funding-a-wallet/)
 
- Like regular keys on a keychain, Bitcoin private keys can be copied. For example, if you gave someone a copy of your house keys, they can unlock the door to your home. Likewise, if someone has a copy of your private key, they can access your bitcoin. This makes [private key management]({{ '/guide/private-key-management/introduction' | relative_url }}) one of the most important considerations of any bitcoin owner.
+While the first two, creating or restoring a wallet, normally need to be tackled straight away, the last two can be designed to fit the flow and capability of your application.
 
- Most bitcoin wallets will automatically generate users' private keys during onboarding, and is not usually something a user controls. We will look at practical design solutions for guiding users through this process in this chapter. This page explains how we can help get a user comfortable with the idea of a self-custodial wallet.
+It is common to see onboarding flows that implore the user to do a manual backup of their recovery phrase straight away, often before they have even gotten to see the main screen of the application. While this can make sure the user is aware of the need to backup, their motivation and ability to safely do this at that exact moment might be limited.
 
-A few different types of wallets let you send, receive, store, and manage bitcoin. For this page, we focus on regular single-key wallets, which are the ones most commonly used.
+Alternative approaches can be to wait and prompt the user only once there are funds in the wallet, at regular intervals, or to use an automatic cloud backup for small amounts. It is up to you as the application designer to decide what works best in your users’ use case.
+
+### Creating a wallet
+
+[Bitcoin wallets]({{ 'guide/glossary/#wallet' | relative_url }}) contain the private keys to a user’s bitcoin. Private keys let users access bitcoin associated with those keys. If the user does not have a Bitcoin wallet already that they want to restore, it is necessary to create a new one. 
+
+Like regular keys on a keychain, Bitcoin private keys can be copied. This makes [private key management]({{ '/guide/private-key-management/introduction' | relative_url }}) one of the most important considerations of any bitcoin owner. Bitcoin wallet applications should automatically generate the user’s private keys locally, meaning they are only generated and stored on the device and not by the wallet provider, during onboarding. 
 
 <div class="center" markdown="1">
 
@@ -44,11 +53,9 @@ A few different types of wallets let you send, receive, store, and manage bitcoi
    layout = "float-left-desktop -background -shadow"
 %}
 
-Most wallets will begin the onboarding process by creating a new or restoring an existing wallet. New users to Bitcoin will usually be going through the flow of creating a new wallet.
+After the user  selects “Create a new wallet”, you might present informational carousels that provide a high-level overview of the implications, benefits, and responsibility that comes with having a self-custodial wallet. Here you can explain to your user that access to the wallet will not require collecting any sensitive information such as usernames and passwords, which is often the case with traditional financial products.
 
-Once an individual selects “create a new wallet”, you might present informational carousels that provide a high-level overview of the implications, benefits, and responsibility that comes with having a self-custodial wallet. Here you can explain to your user that access to the wallet will not require collecting any sensitive information such as usernames and passwords, which is often the case with traditional financial products.
-
-Rather, the user can directly access their funds as long as they have access to the private key or recovery phrase. You should help your users understand that your team do not have the ability to recover their funds in the event they lose their private key. A self custodial wallet often means the user will have to take on greater responsibilty to safely protect their private key so they can always access their funds.
+Bitcoin owners can directly access their funds as long as they have access to their private keys or recovery phrase. You should help your users understand that your team does not have the ability to recover their funds in the event they lose their private key. A self-custodial wallet means the user will have to take on greater responsibility to safely protect their private key so they can always access their funds.
 
 </div>
 
@@ -61,13 +68,15 @@ Wallet creation during onboarding is an excellent opportunity to educate your us
 
 While this may sound daunting to first-time users, 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 (for example, feeling like it is OK if they forget their account information because they can contact customer support to help them recover it).
 
-Some studies suggest that users struggled greatly with technical terminology and feeling as though they had a lack of guidance during wallet setup. By walking users through single steps that clearly frame the features of self-custody Bitcoin wallets, users will feel well-equipped to navigate and use the wallet confidently.
+Ideally your application supports both the base layer and the Lightning network. When talking about backups, you should be clear on what is possible and required in terms of restoring the user’s wallet from a backup.
+
+Some studies suggest that users struggled greatly with technical terminology and feeling as though they had a lack of guidance during wallet setup. By walking users through single steps that clearly frame the features of self-custodial Bitcoin wallets, users will feel well-equipped to navigate and use the wallet confidently.
 
 > Users reported that they often felt like they lacked guidance and understanding during wallet setup
 >
 > <cite>As researched by <a href="https://arxiv.org/pdf/1802.04351.pdf">Eskandari et al</a></cite>
 
-Below is an example of some carousel screens that might be useful in helping a user understand what to expect from this wallet. For this example, we have opted to backup up the users' recovery phrase to a cloud provider but other alternatives exist.
+Below is an example of some carousel screens that might be useful in helping a user understand what to expect from this wallet. For this example, we have opted to backup the users' recovery phrase to a cloud provider, but other alternatives exist.
 
 <div class="image-slide-gallery">
 
@@ -100,7 +109,7 @@ Below is an example of some carousel screens that might be useful in helping a u
 
 </div>
 
- These screens explicitly lay out/guide users on the unique features of self-custodial wallets to make sure they understand these caveats. These screens suggest talking about ownership, explicitly stating the recovery mechanism that the respective wallet uses, and security measures that they should take to protect their wallet.
+ These screens lay out the unique features of self-custodial wallets to make sure the user understands these caveats. These screens suggest talking about ownership, explicitly stating the recovery mechanism that the respective wallet uses, and security measures that they should take to protect their wallet.
 
 ---
 

guide/onboarding/introduction.md

@@ -43,9 +43,9 @@ Remember: Onboarding should not be a crutch for bad design. Avoid trying to expl
 
 ---
 
-### [Creating a new wallet]({{ '/guide/onboarding/creating-a-new-wallet/' | relative_url }})
+### [First use]({{ '/guide/onboarding/first-use/' | relative_url }})
 
-An overview of what information to include when creating a wallet for the first time.
+An overview of common tasks when using a wallet application for the first time.
 
 ---
 
@@ -76,6 +76,6 @@ An overview of how users are likely to fund their wallets
 {% include next-previous.html
    previousUrl = "/guide/designing-products/design-resources/"
    previousName = "Design resources"
-   nextUrl = "/guide/onboarding/creating-a-new-wallet/"
-   nextName = "Creating a new wallet"
+   nextUrl = "/guide/onboarding/first-use/"
+   nextName = "First use"
 %}