You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 14, 2021. It is now read-only.
issues which users run into during Kin wallet backup/restore with respect to QR code:
1/ user needs to have an email account on the device, in order to save the backup QR code. e.g. Sometimes user has Gmail app installed, but do not have an "account" added to the device (so they can't use the "email QR code" function in backup).
2/ user cannot screenshot the QR code, it needs to be the literal file which backup currently sends via email-only. This defeats the purpose of QR code encoding the data.
3/ due to (2), user needs to have the literal QR code file emailed, when restoring. Some users are confused that "restore" opens Gallery, and they can't find the QR code file they emailed themselves.
my suggested ideas/workarounds/updates, in priority order:
A/ for (2), add ability to restore from screenshots -- e.g. restore should be able to take the emailed file, or a sufficiently-detailed screenshot as well. the data is encoded in the screenshot. If adding this as part of restore, should be able to either choose a screenshot file, OR turn on camera/QR code reader and scan an image. i.e. QR code reading functionality should be included, and just like many QR code readers, should be able to take input via "camera" mode or "file" mode.
B/ for (1), use "native share" -- makes it easier for user to save QR image to their local device via any other share method they choose. Then even if user only has "Gmail" or "WhatsApp" installed, they will be able to share the QR code backup file to themselves.
C/ for (3), add a small text string as guidance for user before they restore, along the lines of: "First save your QR code file to your device's photos gallery, then click restore and choose the file." This will be somewhat moot if (A) is implemented. However, I know of certain disabled users who do not have (and are not able to use) a laptop, and they only have a mobile phone device, so this small improvement may still help certain users.