-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider moving 2FA confirm card #186
Comments
We can dose information not by breaking it into separate screens but by adding animated transitions (example https://dribbble.com/shots/6372790-Coffee-Ordering-Animation-Starbucks). |
Thanks for the examples. The collapse/react to scroll, would still mean the user would have to scroll to see all content. Also it would hide the 2FA confirmation dialog (at least partially). I like the examples you showed, but not convinced they're solving the initially reported challenge. Otherwise we can iterate on ideas with mockups, as that's probably the best way to test the look and feel of it. |
I would revisit this topic as part of the 2FA Integration when we tackle the Send flow screens. Do you agree @tschubotz? If yes, should we close this ticket? |
Hmm. I would not do this as part of the 2FA ticket to keep complexity low tbh. I would leave it in this design backlog. Or we move it to "Not now" if you think it clutters it. |
Challenge/problem:
Proposed solution:
In general a lot of information is shown in the review screen. The review screen I consider a good practice in itself, allowing the user to oversee what they're about to send/confirm. Instead of showing the 2FA confirm card upfront, we could break down the flow by showing the review first, have the user tap on 'Submit' and then show a bottom action sheet/card with the 2FA request.
In my opinion this doses the amount of information, especially on the review screen.
The text was updated successfully, but these errors were encountered: