[wp-trac] [WordPress Trac] #56277: Widget to Dashboard to offer Mobile App to users
WordPress Trac
noreply at wordpress.org
Fri Jul 28 02:00:35 UTC 2023
#56277: Widget to Dashboard to offer Mobile App to users
-------------------------------------------------+-------------------------
Reporter: oglekler | Owner: (none)
Type: enhancement | Status: new
Priority: normal | Milestone: Future
| Release
Component: Administration | Version:
Severity: normal | Resolution:
Keywords: has-patch needs-testing has- | Focuses:
screenshots has-testing-info close |
-------------------------------------------------+-------------------------
Changes (by peterwilsoncc):
* keywords: has-patch needs-testing has-screenshots has-testing-info =>
has-patch needs-testing has-screenshots has-testing-info close
Comment:
Replying to [comment:25 hypest]:
Honestly, all this is really telling me is that the WordPress app is being
treated as part of the marketing funnel to get people to use the Jetpack
app:
* A/B testing to see what gets more people to switch to Jetpack
* the WordPress app is full of redirects to the Jetpack app
Having just reinstalled the app and logged in to my personal site, I have
the following experience:
1. 1Password reports the login screen is wordpress.com (alerts it's
unclear wordpress.com should have access to my peterwilson.cc password)
1. Full screen promotion to switch to Jetpack app
2. Select continue without Jetpack
3. Primary call to action: install the Jetpack app
4. Plugins screen fails, only works via wp.com
When logging in via WP.com (remains the primary call to action)
1. Additional screens for reader and notifications, promotes Jetpack app
2. Additional menu items on site pages:
- stats: promotes jetpack app
- activity log: promotes jetpack app
- backup: promotes jetpack app
- themes: promotes jetpack app
- people: "jetpack powered"
> I want to also note that, new work that gets added to the codebase is
surfaced only to the relevant users. For example, Blaze is only available
to WordPress.com users on the Jetpack app, and there's no attempt to
"advertise" it to non-WPCOM users. Similarly, the "Jetpack is detected on
our site, try the Jetpack app" messaging is there for Jetpack-the-plugin
users, to help them enjoy the best companion-app experience.
These are still very Automattic centered promotions within the WordPress
app. If a user chooses to use the WordPress app, Blaze should not be
promoted to them in any circumstances if it's genuinely intended to be a
product for WordPress.org users.
You've got multiple core committers who perceive this as too tied to
Automattic, in it's current form, for it to be promoted in WP.org. I'm
inclined to close this as `maybelater` until the following happens:
* primary call to action for wp.com removed
* Jetpack and WP application code bases split up
* all "useful" redirects to Jetpack removed
* all marketing material to "unlock your site's full potential" removed
* data sharing with the Jetpack app removed
--
Ticket URL: <https://core.trac.wordpress.org/ticket/56277#comment:27>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list