-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Show the "Verify Your Email" view on no sites view #24211
Conversation
|
App Name | ![]() |
|
Configuration | Release-Alpha | |
Build Number | pr24211-af9c13b | |
Version | 25.8 | |
Bundle ID | com.jetpack.alpha | |
Commit | af9c13b | |
App Center Build | jetpack-installable-builds #10781 |
|
App Name | ![]() |
|
Configuration | Release-Alpha | |
Build Number | pr24211-af9c13b | |
Version | 25.8 | |
Bundle ID | org.wordpress.alpha | |
Commit | af9c13b | |
App Center Build | WPiOS - One-Offs #11755 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the spirit of nudging customers to verify their email, we can show the "Verify Your Email" view on the newly created account. Since the "Create WordPress.com site" flow is broken, we can disable the button, which echos the description in "Verify Your Email": "Verify your email to [...] access more features".
If verification is required to create a site and there are no other ways to address it, the app should show a "Verify Your Email" step when you tap the "Create WordPress.com Site" button. The new step can be fullscreen like we used to have in WordPressAuthentificator
. Showing both the disabled button and the notice sends a confusing message.
@kean Good point! Do you think showing the "Verify Your Email" on the "no site view" is still necessary, if we will show it in a modal? |
Maybe we can keep the UI change in this PR and add a simple alert to ask the user to verify their email? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kean Good point! Do you think showing the "Verify Your Email" on the "no site view" is still necessary, if we will show it in a modal?
I think "Verify Your Email" is not needed and looks off on the "No Sites" view. It's the first thing you will see after creating an account. It sends a confusing message: should I "Create Account" now or "Verify", what do I do first?
User scenarios:
- If you want to create an account, you'd tap "Create Account" and be prompted to verify.
- If you want to explore Reader, you don't need to verify account.
- If you go to Me, you're the the "Verify" prompt
There is no reason for it to exist on the "No Sites View".
"Verify Your Email" (assuming it's not critical to access Reader, update your profile, etc) should be in one place – "Me" tab. If we want to lead users there, there needs to be a badge on the tab bar icon. If "Verify Your Email" is so important, it has to be done as one of the account creation steps.
The "Verify your email" banner appears on the user's dashboard (where you see a list of your sites). I thought we should do the same in the app to nudge users to verify their email. They probably don't need to verify their email, but I think we want them to do that as soon as possible. Many checks in the WordPress.com login process require the user to verify their email, which is the technical reason why we can't get auth cookies using an unverified account token. We want app users to verify their email even more because some features (post preview, themes, domains, etc) won't work without auth cookies. |
That's fair, but I would recommend to do that via the existing "Verify" view on the "Me" tab by using a red badge on the tab bar to guide the user there. There isn't a need for a separate entry point on the "No Site" view. |
Fixes #24205. See the issue description and comments for details.
Simulator.Screen.Recording.-.iPhone.16.Pro.-.2025-03-13.at.22.03.57.mp4
To test:
Regression Notes
Potential unintended areas of impact
What I did to test those areas of impact (or what existing automated tests I relied on)
What automated tests I added (or what prevented me from doing so)
PR submission checklist:
RELEASE-NOTES.txt
if necessary.Testing checklist: