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

Onboarding - Security Check #16287

Open
PeKne opened this issue Jan 9, 2025 · 0 comments
Open

Onboarding - Security Check #16287

PeKne opened this issue Jan 9, 2025 · 0 comments
Labels
mobile Suite Lite issues and PRs

Comments

@PeKne
Copy link
Contributor

PeKne commented Jan 9, 2025

FIGMA

Acceptance criteria

  • As a user that is on the Unlock screen and clicks on CTA [Start], I would like to see Security check screen with three section stepper (1) Trusted source, (2) Holographic seal, (3) Packaging
    • CTAs available in each stepper
      • [Yes] to continue
      • [I am not sure]
    • Conditionals
    • If the user clicks on [Yes] they will continue to the next stepper
    • If the user is on (1) Trusted source, they can check resellers at URL: https://trezor.io/resellers
    • If the user is on (2) Holographic sea, they can check it click on the hyperlink that opens the Holographic seal overlay
  • holographic seal:** As a user on the Holographic seal overlay, I would like to be informed how to verify the seal and how to proceed if it was damaged.
    • CTAs available
    • Conditionals
    • If the user clicks outside of the overlay, they will go back to the Security check screen on the second stepper (2) Holographic seal
@PeKne PeKne added the mobile Suite Lite issues and PRs label Jan 9, 2025
@PeKne PeKne added this to the Mobile - Onboarding (Part 2) milestone Jan 9, 2025
@github-project-automation github-project-automation bot moved this to 🎯 To do in Suite Mobile Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
mobile Suite Lite issues and PRs
Projects
Status: 🎯 To do
Development

No branches or pull requests

1 participant