Deposit feature in web extension new iteration

* The "last activity" tab is now "pending activity"
* The exchange URI has been added to the KYC screen
* The deposit screen now displays the balance
* The deposit fields now add the fee to the deposit amount
* The deposit screen provides an "up to" amount that sets
the amount the maximum deposit
* The design includes an error message when the deposit
amount is too high
* The design includes an "enter URI" action

Signed-off-by: Belen <belenbarrospena@gmail.com>

1 files changed, 49 insertions, 0 deletions

diff --git a/anastasis_integration_wallet/backup/wallet_backup/feedback_on_iteration2.txt b/anastasis_integration_wallet/backup/wallet_backup/feedback_on_iteration2.txt
new file mode 100644
index 0000000..74485b4
--- /dev/null
+++ b/anastasis_integration_wallet/backup/wallet_backup/feedback_on_iteration2.txt
@@ -0,0 +1,49 @@
+0:59) Very minor:
+
+"Your backups are encrypted"
+
+-- well, not yet (if not yet enabled).
+What about using "Backups will be encrypted" if the backup is not yet set up?
+
+1:31) English: I think it should be "ending with a forward slash", not "ended".
+
+1:45) "recognize" suggests that we have a list of known providers. Maybe better
+to say "The service at this address does not support the Taler wallet backup
+protocol." or (depending on the internal evaluation) "The service at this address
+does not support the right version of the Taler wallet backup protocol."
+
+3:10) No idea, but probably may need to give user a way to change the file location,
+ideally using standard OS-specific dialogs. Not sure about the "back up with a
+cloud provider" option, I would have expected that action to be the normal "back"
+action --- it's not like backing up to a file will disable the cloud backup, right?
+So if the file is just an additional thing one can do manually, I think "back" is
+the right thing.
+
+4:00) Maybe good to explain about auto-renewal here, like "the wallet will automatically
+extend the service by another year unless you disable the backup before the expiration date"?
+
+6:06) Not "by other people", but "by malicious Apps on your phone".
+
+7:01) I guess we can show this information, but it is not really
+something we'd fetch from the provider at this time -- we can simply
+(even locally!) confirm that this is our *current* backup.
+Alternatively, I guess the wallet could really test the provider and
+download its current state from the provider -- but still this
+information is part of the wallet state, the sync protocol does not
+tell us what the fee paid, storage used or expiration date would be
+--- the wallet needs to remember this explicitly internally. What we
+might instead want to show is the *time* of the last synchronization
+with that provider.
+
+7:12) I think we should use backup (singluar) here, as there can only
+ever be one (the latest) backup per provider/credential.
+
+7:40) We should have the same security warning as at 6:06 because copying the
+text or the QR code to the clipboard have the same security issue with
+malicious apps on the phone.
+
+9:09) auto-renewal is not super discoverable. Maybe make the toggle
+already part of the original 'pay' dialog?
+
+10:15) Maybe make it clear that the existing backups will NOT be deleted
+by this?