Skip to content

📱 Revise Daily spending wallet -> Backup & Recovery section #763

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Bosch-0 opened this issue Apr 11, 2022 · 7 comments · Fixed by #892
Closed

📱 Revise Daily spending wallet -> Backup & Recovery section #763

Bosch-0 opened this issue Apr 11, 2022 · 7 comments · Fixed by #892
Assignees
Labels
Copy Task is about improving text. Daily spending wallet Referring to the Daily spending wallet reference design section. Design Task is about designing something.

Comments

@Bosch-0
Copy link
Collaborator

Bosch-0 commented Apr 11, 2022

This issue will be part of a bigger milestone that focuses on revising the newly formed Daily spending wallet reference design we now have in the guide.

Need to address metadata backups: #648

@Bosch-0 Bosch-0 added Copy Task is about improving text. Design Task is about designing something. Daily spending wallet Referring to the Daily spending wallet reference design section. labels Apr 11, 2022
@Bosch-0
Copy link
Collaborator Author

Bosch-0 commented Apr 13, 2022

For these revision pages the images should also be generally updated:

  • Ensure they reflect what is shown in the UI kit
  • Apply new modal formatting to images
  • Remove grey area on the iPhone 'dip' at the top of the phone (see below).

image

@Bosch-0
Copy link
Collaborator Author

Bosch-0 commented Apr 20, 2022

We need to address multi-language recovery phrase backups as part of this issue: #753

@GBKS
Copy link
Contributor

GBKS commented Jul 18, 2022

@sbddesign you think it makes sense to split this issue into 4 separate ones? One for each of the pages?

@sbddesign
Copy link
Collaborator

No -- content between the pages is somewhat dependent on the other pages.

@sbddesign
Copy link
Collaborator

I've been doing more work on this for #856, focusing on the recovery flows this time.

Figma

Looking for feedback on this work here.

Screen Shot 2022-07-19 at 11 18 57 AM

Video

Here's a video of me narrating my thoughts over the Figma file. It ended up being long, so if you're interested in watching, save yourself the trouble and pop it on 2x speed, or use the timecodes in the notes to skip around. Notes below:

High level overview

  • Recovery scenarios
    • Basic Recovery - this is for non-hostile scenarios, like the user losing their phone or replacing the phone with a newer one.
    • Emergency recovery - this is for hostile scenarios, such as app provider or LSP becoming evil, censorship, or technical/business problems on part of app provider or LSP.
  • For this particular product, all that's needed is:
    • Recovery phrase
    • Channel state
  • Manual backup means manually backing up the key
    • Obviously it's for advanced users
    • It does not mean manually backing up the channel state -- such backups will almost always be out-of-date and so would harm the user's access to funds in a recovery scenario
    • An advanced user might opt-out of using the stock auto channel backup location (say, store in NextCloud instead of Apple), but we must assume that there will be some form of cloud backup for the channel state in all scenarios.
  • Recovery tool
    • There should be a sovereign recovery tool that can be published independently of an app store
    • This could be useful for an emergency recovery scenario, particularly one where an app has been pulled from the app store
    • This sort of content could be applicable beyond just the daily spending wallet, so maybe recovery tool info could go on another page
    • Recovery tool could potentially restore access to funds without channel state by asking LSP to force close. Good to have this option for an emergency, but this would not work in a scenario where the LSP is offline or uncooperative.

@sbddesign
Copy link
Collaborator

Thanks for leaving feedback on the Figma, everyone. I've been making some revisions to the frames and also laying out updates inside of a Google Doc. I'm trying to make sure that I avoid redundancy and keep all the content relevant to this specific daily spending wallet. Working with all the content inside a single document is helpful to this end.

https://docs.google.com/document/d/1CfeIfygTdTWTm6I61iIlEYI8RPE58UjTmIoAB4DeG5A/edit?usp=sharing

I'm not quite ready for feedback on it, but will be very soon. Then we I can start turning that into commits for #856.

@sbddesign
Copy link
Collaborator

Update: I am ready for feedback on this document.

@GBKS GBKS linked a pull request Aug 15, 2022 that will close this issue
@GBKS GBKS closed this as completed in #892 Aug 24, 2022
Repository owner moved this from In Progress 🏗️ to Done ✅ in Bitcoin Design Guide Roadmap 🎨🎯 Aug 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Copy Task is about improving text. Daily spending wallet Referring to the Daily spending wallet reference design section. Design Task is about designing something.
Projects
3 participants