I just want to remind us that we should bear in mind to keep the flow simple and not overcomplicate the UI,
We can run remote user tests on usertesting.com to check how people get it. One participant is around $39, we can set their location, income etc.
Absolutely we should test. I was taught good lessons back in the bank where tests reveals what I couldn't have predicted.
Speaking of project management, the backup/restore feature can't wait as it is already 3 weeks into the end of the sprint. Let's finalize the implementation of what is already designed and have tests done in the meanwhile, and have Green team to implement the needed changes from the learning of the tests.
If you are speaking of the "set-up fingerprint authentication" screen (which happens when the user change from a key not requiring user-presence to an encryption key that requires user-presence), I have the following info:
- it's needed by Android since it can't be set up without user-interaction. So we can do all sorts of simplification except leaving that one out
- but the same can't be said of iOS. @Tomek, @hboon just told me in today's weekly meeting that iOS doesn't technically require a set-up phrase for swapping the key to an encryption key that requires user-presence, so do we add the set-up screen anyway despite iOS doesn't need it, making it more complicated?
I subscribe to a view much influenced by my early days in GIZ/AHK (German) that "simple" means "consistent" and "clear", not "fewer steps". "Swapping key to an encryption key requiring user-presence" marks a point of no return: before that, the user will not lose the key unless he does it in settings or he deletes the app; after this point, if the user disables screenlock in the OS, the key is lost and the user will have to use backup.
@hboon is of the opinion that the point of no return was blurry at the outset - if a user would cry a river when he lost his key as he disables screenlock in the OS, then a user would cry a river too when he deleted the app and re-installed it (and finding 0Ξ), as his experience was deleting an app has nothing to do with deleting money or identity. My view: even crypto users who knows they can't delete their app without backup their money can't reasonably anticipate disabling screen lock would cause loss of money, therefore to hide the change is not a simplification but a complication, from the view that "simplicity is consistence and clarity".
I also think consistence between iOS and Android is highly desirable.