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