Skip to content
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

[HOLD for payment 2023-05-29] Implement UI changes for managing 2FA in newdot #18080

Closed
MonilBhavsar opened this issue Apr 27, 2023 · 51 comments
Closed
Assignees
Labels
Awaiting Payment Auto-added when associated PR is deployed to production NewFeature Something to build that is a new item. Reviewing Has a PR in review Weekly KSv2

Comments

@MonilBhavsar MonilBhavsar added the NewFeature Something to build that is a new item. label Apr 27, 2023
@MelvinBot
Copy link

@melvin-bot melvin-bot bot added the Weekly KSv2 label Apr 27, 2023
@MonilBhavsar MonilBhavsar self-assigned this Apr 27, 2023
@MonilBhavsar
Copy link
Contributor Author

@thiagobrez sorry looks like I assigned you to the wrong issue.
Could you please comment here so that I can assign you here

@thiagobrez
Copy link
Contributor

No worries @MonilBhavsar !

@MonilBhavsar
Copy link
Contributor Author

MonilBhavsar commented Apr 27, 2023

Thanks! We're almost unblocked. Feel free to go through the document and you can start working on it. Always here to help if you have any questions. Thank you!

@thiagobrez
Copy link
Contributor

@MonilBhavsar Awesome, thank you very much 🙇🏻 Could you give me permissions to access the doc?

@bfitzexpensify
Copy link
Contributor

Internal handling happening via #15215, so don't think I'm needed here. Unassigning myself

@bfitzexpensify bfitzexpensify removed their assignment Apr 27, 2023
@MonilBhavsar
Copy link
Contributor Author

@thiagobrez could you please check. We have shared the doc with you.

@thiagobrez
Copy link
Contributor

@MonilBhavsar Yes! It worked and I'm already on it, thank you very much! Also, I see that the figma designs are in the works and expected to be done by Monday. Can I have access to that also when it's done? Thank you :)

@MonilBhavsar
Copy link
Contributor Author

We have finalized the design and final designs are updated in the doc. Is that fine, or you need designs exported directly from Figma?

@thiagobrez
Copy link
Contributor

I think I was expecting to have access to the actual design file so I could measure and do everything pixel-perfect. But if that is not possible no worries, I guess with the pre-made components and detailed implementation in the doc it is already possible

@thiagobrez
Copy link
Contributor

Update: Good progress on UI. Enabled, Disabled and Codes pages are done, Verify page is almost. After that, Success page should be quick.

@thiagobrez
Copy link
Contributor

Update: UI is done and connected to API. Next up is testing on all platforms and writing tests.

@MonilBhavsar
Copy link
Contributor Author

@shawnborton, @thiagobrez is working on implementation of 2FA settings and requires a SVG/animation file

We have this svg/animation on the success page of the 2FA settings.

Screenshot 2023-05-08 at 3 49 35 PM

This looks fireworks and we also have fireworks in the success page of Bank Accounts page. That looks like this (plugged in 2FA settings page) -

Screen.Recording.2023-05-08.at.11.27.29.mov

Do we want to use the same fireworks animation or different one as proposed in Figma?
Also when exporting that SVG from Figma, it shows colorless in App and looks like we export from Adobe. If so could you please help us to export that file. Thanks! 🙏

@melvin-bot melvin-bot bot added the Reviewing Has a PR in review label May 8, 2023
@shawnborton
Copy link
Contributor

Can you show me what is proposed in Figma that might be different from the animation you linked above?

Personally I think we should just use the same fireworks animation we're using elsewhere.

@MonilBhavsar
Copy link
Contributor Author

This is what is proposed in Figma

https://user-images.githubusercontent.com/32012005/236802117-ece0bbda-e94d-43c0-9a71-915007b7bda7.png

Personally I think we should just use the same fireworks animation we're using elsewhere.

I agree 👍

@shawnborton
Copy link
Contributor

Oh, the screenshot you shared is basically the same as the animation so we're all good.

@MonilBhavsar
Copy link
Contributor Author

Awesome, thanks for clarifying. So we use the fireworks animation we currently have. cc @thiagobrez

@thiagobrez
Copy link
Contributor

Perfect, thank you both @shawnborton @MonilBhavsar !

@thiagobrez
Copy link
Contributor

Update: Draft PR is being reviewed internally

@thiagobrez
Copy link
Contributor

Hey @shawnborton! Is this security settings page header expected to be implemented in this PR? Asking because I did not see any mention for it in the design doc:

Screenshot 2023-05-10 at 10 14 38

cc @MonilBhavsar

@MonilBhavsar
Copy link
Contributor Author

Good question! I don't think so. I guess this should be a part of another PR where we apply header images to all pages, so we have consistency in design. But yeah, @shawnborton would be knowing better.

@thiagobrez
Copy link
Contributor

Happy to help provide any specific images/svgs you might need, just let me know!

Thanks @shawnborton!

I need the Expensify logo, with dark background and light fill color, in 400x400px, so I can put it in the middle of the 2-factor authentication QR Code.

The INVERSE of this one ⬇️

image

@thiagobrez
Copy link
Contributor

For the email/login part, can we use our textSupporting color please? Thanks!

Maybe this should be addressed in #18636? This screenshot was just showing that there were no regressions in the Share Code feature. I haven't touched that in this issue.

But I know the Share Code PR is already closed, so if you want me to fix it in this PR anyway, I can do it easily. Just wanted to give the heads up :D

cc @MonilBhavsar

@shawnborton
Copy link
Contributor

@thiagobrez which format do you need? svg or png?

@MonilBhavsar
Copy link
Contributor Author

Agree with @thiagobrez here.
We need to open another issue and PR to address this concern.

@shawnborton
Copy link
Contributor

That works for me! Can you make sure to follow up on the respective issue (or create a new one) for that?

@MonilBhavsar
Copy link
Contributor Author

Sure, looks like there have been some bug reports for QR code already. If we can spin up a PR and polish them all? cc @robertjchen

@robertjchen
Copy link
Contributor

Yep! We're working on the bug reports for the QR code here: #18968

@MonilBhavsar
Copy link
Contributor Author

That's awesome! 🙌
It would be great to fix the issue Shawn mentioned here in that PR.

@thiagobrez
Copy link
Contributor

@thiagobrez which format do you need? svg or png?

@shawnborton PNG, please 🙌🏻

@shawnborton
Copy link
Contributor

Okay, curious how we'll handle this one for light mode too cc @grgia something to consider here.

Here is the png: appicon_qrcode.png.zip

@grgia
Copy link
Contributor

grgia commented May 16, 2023

Added to light mode doc to track, thanks!

@thiagobrez
Copy link
Contributor

Thank you! Sending updates in the PR: #18576

@thiagobrez
Copy link
Contributor

PR is merged 🏁

@melvin-bot melvin-bot bot added Weekly KSv2 Awaiting Payment Auto-added when associated PR is deployed to production and removed Weekly KSv2 labels May 22, 2023
@melvin-bot melvin-bot bot changed the title Implement UI changes for managing 2FA in newdot [HOLD for payment 2023-05-29] Implement UI changes for managing 2FA in newdot May 22, 2023
@melvin-bot
Copy link

melvin-bot bot commented May 22, 2023

Reviewing label has been removed, please complete the "BugZero Checklist".

@melvin-bot melvin-bot bot removed the Reviewing Has a PR in review label May 22, 2023
@melvin-bot
Copy link

melvin-bot bot commented May 22, 2023

The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.16-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

If no regressions arise, payment will be issued on 2023-05-29. 🎊

After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.

  • External issue reporter
  • Contributor that fixed the issue
  • Contributor+ that helped on the issue and/or PR

As a reminder, here are the bonuses/penalties that should be applied for any External issue:

  • Merged PR within 3 business days of assignment - 50% bonus
  • Merged PR more than 9 business days after assignment - 50% penalty

@melvin-bot melvin-bot bot added Daily KSv2 Overdue and removed Weekly KSv2 labels May 29, 2023
@MonilBhavsar
Copy link
Contributor Author

Not sure, why this wasn't closed by PR.
Closing this now. Thanks @thiagobrez!

@melvin-bot melvin-bot bot removed the Overdue label Jun 1, 2023
@melvin-bot melvin-bot bot added Reviewing Has a PR in review Weekly KSv2 and removed Daily KSv2 labels Oct 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Awaiting Payment Auto-added when associated PR is deployed to production NewFeature Something to build that is a new item. Reviewing Has a PR in review Weekly KSv2
Projects
None yet
Development

No branches or pull requests

7 participants