Co-branding JP login screen with WP.com#22296
Conversation
…o feature/cobranding-welcome-screen # Conflicts: # WordPress/WordPress.xcodeproj/project.pbxproj
|
| App Name | WordPress Alpha |
|
| Configuration | Release-Alpha | |
| Build Number | pr22296-1d02d3b | |
| Version | 23.9 | |
| Bundle ID | org.wordpress.alpha | |
| Commit | 1d02d3b | |
| App Center Build | WPiOS - One-Offs #8317 |
|
| App Name | Jetpack Alpha |
|
| Configuration | Release-Alpha | |
| Build Number | pr22296-1d02d3b | |
| Version | 23.9 | |
| Bundle ID | com.jetpack.alpha | |
| Commit | 1d02d3b | |
| App Center Build | jetpack-installable-builds #7341 |
|
There's an issue on button view's background color on iPad. I'm trying to find a solution without modifying the |
|
|
||
| # pod 'WordPressAuthenticator', '~> 8.0' | ||
| pod 'WordPressAuthenticator', git: 'https://github.com/wordpress-mobile/WordPressAuthenticator-iOS.git', commit: 'b51b4b238103f7812db0aa1a265995e1c6d1e355' | ||
| pod 'WordPressAuthenticator', git: 'https://github.com/wordpress-mobile/WordPressAuthenticator-iOS.git', commit: '215c77f4dad18b67943bc46174050d8c668c597c' |
There was a problem hiding this comment.
This resolves the iPad issue. However I am not sure what the pod target here should be. It was targeting a specific commit before as well but this doesn't sounds great. @mokagio perhaps you would have more information about this? Is there a reason why this pod isn't targeting a specific release?
There was a problem hiding this comment.
This resolves the iPad issue.
That's great. Thanks!
I noticed there's not a PR for it yet but I assume one will be opened soon, right?
However I am not sure what the pod target here should be. It was targeting a specific commit before as well but this doesn't sounds great.
It's okay to target commits for the pods during development. That is, only release/ branches should always point to stable pods and other libraries. More info at paNNhX-K4-p2
The one thing to be aware when changing from one commit to another is to make sure that the new commit is after the original one, so that both changes are present. That is, of course, unless the second commit directly aims at fixing an issue in the orginal one, for example by switching for "experimental branch for feature X number 1" to "experimental branch for feature X number 2".
Is there a reason why this pod isn't targeting a specific release?
The procedure above should answer this question, too. For reference, the PR that changed it is #21904.
Hope this helps.
| "images" : [ | ||
| { | ||
| "filename" : "JPBackground.pdf", | ||
| "filename" : "background-light.pdf", |
There was a problem hiding this comment.
Have you considered using .webp images instead of .pdf? I see it's supported by Apple starting from iOS 14. The format drastically reduces image weight.
For instance, here is the result on Android:

There was a problem hiding this comment.
4mb is indeed plenty to add to the binary even though the PR reduces the binary due to the fact that the new image is smaller in size than the old one. I assume .webp wouldn't be very common in iOS but I don't know if there's any reason for that apart from that fact that it is rather newer. I'll take a look and update it as such if I can't find a reason not to do that. Thanks for the heads up!
| @@ -1,3 +1,7 @@ | |||
| 24.1 | |||
| ----- | |||
| * [**] Updated login screen's colors to highlight WordPress - Jetpack brand relationship | |||
There was a problem hiding this comment.
The next version is 24.0. Don't forget to move this release not to 24.0.
salimbraksa
left a comment
There was a problem hiding this comment.
I've tested the new UI on iPhone and iPad and LGTM! 👍
…o feature/cobranding-welcome-screen
…dc3954b80868b497b4531`



Fixes: https://github.com/Automattic/jetpack-mobile-roadmap/issues/96
PT: pcdRpT-58l-p2
This PR redesigns the Jetpack app’s welcome screen to include more references to the WordPress brand, such as colours and logo.
Testing Steps
Install & Launch Jetpack App and verify the colors match the designs in light and dark modes.
Regression Notes
Potential unintended areas of impact
N/A
What I did to test those areas of impact (or what existing automated tests I relied on)
N/A
What automated tests I added (or what prevented me from doing so)
Only UI related changes
PR submission checklist:
RELEASE-NOTES.txtif necessary.UI Changes testing checklist: