-
Notifications
You must be signed in to change notification settings - Fork 107
📱 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
Comments
For these revision pages the images should also be generally updated:
|
We need to address multi-language recovery phrase backups as part of this issue: #753 |
@sbddesign you think it makes sense to split this issue into 4 separate ones? One for each of the pages? |
No -- content between the pages is somewhat dependent on the other pages. |
I've been doing more work on this for #856, focusing on the recovery flows this time. FigmaLooking for feedback on this work here. VideoHere'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
|
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. |
Update: I am ready for feedback on this document. |
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
The text was updated successfully, but these errors were encountered: