-
Notifications
You must be signed in to change notification settings - Fork 10.7k
Add: mobile app welcome modal and magic link #34637
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
Conversation
Test Results SummaryCommit SHA: 0e6fe2a
To view the full E2E test report, click here. To view all test reports, visit the WooCommerce Test Reports Dashboard. |
...ocommerce-admin/client/homescreen/mobile-app-modal/components/JetpackInstallationStepper.tsx
Outdated
Show resolved
Hide resolved
...ocommerce-admin/client/homescreen/mobile-app-modal/components/JetpackInstallationStepper.tsx
Outdated
Show resolved
Hide resolved
...ocommerce-admin/client/homescreen/mobile-app-modal/components/JetpackInstallationStepper.tsx
Outdated
Show resolved
Hide resolved
...ocommerce-admin/client/homescreen/mobile-app-modal/components/JetpackInstallationStepper.tsx
Outdated
Show resolved
Hide resolved
...ins/woocommerce-admin/client/homescreen/mobile-app-modal/layouts/ModalIllustrationLayout.tsx
Outdated
Show resolved
Hide resolved
plugins/woocommerce-admin/client/homescreen/mobile-app-modal/index.tsx
Outdated
Show resolved
Hide resolved
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.
Note: This isn't a full review yet, I'm sending earlier so they can be addressed first.
- Nitpicky, but the email part isn't centered vertically:
- The design looks tad different after I'm connected & refreshed the page (i.e: The stepper numbers on the side, the step #1 for connected user), I'm not sure if this is intentional?
-
It seems when successfully sending an email, there was no toast message saying "Magic link sent!"
-
Tracks were not implemented, but I think it's better to create an issue and implement as a follow-up
|
4de4137 to
24f7021
Compare
|
@rjchow Thanks for addressing!
|
|
@rjchow Tracks issue has been created 76-gh-woocommerce/team-ghidorah |
Add backend and demo flow added jetpack installation and activation logic Added resolver for jetpack connection data Add request for magic link Switch to XMLRPC for magic link request Instead of dealing with the OAuth request, which requires a client ID and a public "secret", which can take a page from the Jetpack playbook for requesting the magic login email. This changeset is lifted almost entirely from here: https://github.com/Automattic/jetpack/blob/ea3bde0e92c6953578745d6cd026f62ecf35b17b/projects/plugins/jetpack/_inc/lib/class.core-rest-api-endpoints.php#L4074-L4105 Note the only difference from the Jetpack version is that we're adding an `app` parameter to the request and specifying `woocommerce`. This won't actually do anything until some changes get made on the wpcom side to accommodate this new parameter (I'm still working on that). Once those changes are in place, though, the email that gets sent will be Woo-branded and may even be able to include a QR code. add: moved feature to woo mobile app welcome page wip wip wip wip
2953a65 to
af22254
Compare
|
@rjchow I couldn't get the email on my JN site with the error Screen.Recording.2022-09-14.at.14.14.38.movAnd I also found some small design mismatches, but I think it's okay if you want to update them in a follow-up PR. |
I just printed out the error message.
|
|
@chihsuan Thanks for the re-review! Some of the font differences are because the font-family itself is different so I picked values which looked closer to the design instead of the exact same ones. I think the sparkle icon depends on your OS actually, it's a copy paste from the Figma and it's an emoji 🤣 Things I missed:
|
Sounds good! |
chihsuan
left a comment
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.
@rjchow Thanks for working on this. Excellent work! 🚀
|
Everything looks good! I do agree that the send email part should be centered vertically in the white space. In the Figma file, I duplicated the bottom part ( Other than that, is it expected for Jetpack to install this long? It took almost 30 seconds to display the connection screen in your video. If that's how it always is, I think we should add one more sentence at the end of the step description. I marked it in bold below.
|
New hook, template, or database changes in this PRTemplate changes:
|
|
Hi @rjchow, thanks for merging this pull request. Please take a look at these follow-up tasks you may need to perform:
|







All Submissions:
Changes proposed in this Pull Request:
Figma Design: G9vi4e286yjdzyIdg8hBb1-fi-2002%3A142047
Project Thread: pdibGW-LI-p2
How to test the changes in this Pull Request:
There are two general flows in this feature:
To test this PR, you will first need to set up a WooCommerce environment which can be reached by Jetpack and complete a full Jetpack installation.
Jurassic ninja will suffice, or using ngrok or some other form of tunnelling if you are running it locally.
Guided Jetpack Installation flow
NVIDIA_Share_lIDHVbIGE0.mp4
Jetpack already fulfilled flow
firefox_FDTrGTjUeQ.mp4
Other testing notes:
Jetpack can have a variety of partial installations, such as a plugin that is installed but not activated, or a plugin that is installed and activate but not connected to a WordPress.com account.
These flows should be tested if possible, they can be created by simply exiting the Jetpack installation flow at various points without completing.
These partial flows should result in the dialog showing the first flow with the guided Jetpack installation, and completing the setup.
It might also be worth testing this feature with non-admin users.
Other information:
pnpm changelog add --filter=<project>?FOR PR REVIEWER ONLY: