gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[taler-large-media] branch master updated: Feedback on backup process de


From: gnunet
Subject: [taler-large-media] branch master updated: Feedback on backup process design - version 1
Date: Tue, 03 Aug 2021 15:26:45 +0200

This is an automated email from the git hooks/post-receive script.

belen pushed a commit to branch master
in repository large-media.

The following commit(s) were added to refs/heads/master by this push:
     new 1a4a5b3  Feedback on backup process design - version 1
1a4a5b3 is described below

commit 1a4a5b313dc57984af1dbd3552fc09f1522b6731
Author: Belen <belenbarrospena@gmail.com>
AuthorDate: Tue Aug 3 14:24:25 2021 +0100

    Feedback on backup process design - version 1
    
    This is the feedback collected so far on version 1 of the design
    for the backup process of the Anastasis integration in the Android
    wallet.
    
    Signed-off-by: Belen <belenbarrospena@gmail.com>
---
 .../backup/backup_wallet_key_v1_feedback           | 43 ++++++++++++++++++++++
 1 file changed, 43 insertions(+)

diff --git a/anastasis_integration_wallet/backup/backup_wallet_key_v1_feedback 
b/anastasis_integration_wallet/backup/backup_wallet_key_v1_feedback
index e69de29..dbdb4b3 100644
--- a/anastasis_integration_wallet/backup/backup_wallet_key_v1_feedback
+++ b/anastasis_integration_wallet/backup/backup_wallet_key_v1_feedback
@@ -0,0 +1,43 @@
+FEEDBACK
+
+* The settings screens need changing. Backing up a key using Anastasis is the 
second stage of the wallet backup process. After backing up your wallet, you 
will see a QR code containing the backup encryption key you will need to 
restore your wallet backup. You can download and print that QR code to keep it 
safe yourself. You can also back it up using the Anastasis integration 
functionality.
+
+* Given the above, there are 4 use cases related to the wallet backup and the 
Anastasis integration:
+1. Configure your wallet backup and keep the QR code yourself.
+2. Configure your wallet backup and backup the key with Anastasis.
+3. Restore your wallet backup from a QR code.
+4. Restore your wallet backup through Anastasis.
+
+* This design piece for the Anastasis integration covers use cases 2 and 4, 
but in practice they need to play nicely with the wallet backup process. For 
that, I need to understand a bit more of the wallet backup process, and 
particularly its final step (i.e. showing the backup key QR code). Questions 
about the wallet backup process can be sent to Florian.
+
+* Remove currency selection and the "add currency" action: the Anastasis 
integration will use the currencies configured in the wallet.
+
+* Design country selection. Christian thinks it would be better to break it 
down by continent, then country. He argues this reduces the need to scroll, and 
helps in situations where a country is known by more than one name (e.g. Great 
Britain, United Kingdom). I still think it may be possible to design a good 
country selector where a search+filter interaction allows me to filter the list 
of countries; and where we cater for multiple country names by ensuring 
search+filter results include [...]
+
+* Once I have configured one or more authentication methods, I must be able to 
see the details for each of them (screens 5 and 6).
+
+* Add video identity verification to the list of authentication methods.
+
+* We need to design for the state where no Anastasis backup provider exists. 
This may happen if your wallet is configured with unusual currencies. As I 
understood, once you have entered your country, Anastasis will check whether 
providers are available, and which authentication methods they support. It does 
this while the user enters their personal details. Which means that, if no 
providers are available, you will see a message telling you so after entering 
your personal details. I need  [...]
+
+* I have complained about the fact that I won't be told no providers are 
available until I enter my personal details. At that point, I have already 
invested significant effort in the process. If I don't know of any providers 
that I can manually configure, I am effectively pushed out of the process after 
all that effort. I think a better approach would be to show a "searching 
providers" screen after the country stage, and notify users if no providers 
exist at that point, i.e. before enter [...]
+
+* Remove "add provider" action from the "Configure authentication methods" 
screen. We should show the option to add a provider only if
+1) no providers are found for the wallet currencies, or
+2) no provider was found for the chosen authentication method.
+
+* Consider visually indicating those authentication methods unsupported by 
available providers, and which therefore require users to configure a provider 
manually.
+
+* We will use the icons for the authentication methods in the Anastasis 
standalone application as well. The icons are available at 
https://git.taler.net/large-media.git/tree/anastasis_integration_wallet/icons. 
They are released under the Apache License version 2.0 
(https://github.com/google/material-design-icons).
+
+* Christian would like to see the backup expiry date on a single line (see 
screen 9).
+
+* The backup cost can be split into several currencies (e.g. 1 EUR and 1 CHF). 
Show this "mixed currency wallet" case in the design.
+
+* The payment page should provide a summary of what I am paying, broken down 
by provider.
+
+* Provide a way to exit the backup process in a single tap (a "cancel" button).
+
+* After some discussion, we concluded that we will forget all personal 
information entered if you exit the backup process either via the "cancel" 
button or by using the Android history-back button.
+
+* We discussed how the word "backup" is overloaded. We already use it to refer 
to the wallet backups, so we should find a different term to refer to this copy 
of the wallet backup encryption key.

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]