Change 894048 had a related patch set uploaded (by Kosta Harlan; author: Kosta Harlan):

[mediawiki/extensions/GrowthExperiments@master] levelingup: Keep going notification

https://gerrit.wikimedia.org/r/894048

Change 894043 had a related patch set uploaded (by Kosta Harlan; author: Kosta Harlan):

[mediawiki/extensions/GrowthExperiments@master] levelingup: Keep going notification

https://gerrit.wikimedia.org/r/894043

Change 894048 abandoned by Kosta Harlan:

[mediawiki/extensions/GrowthExperiments@master] levelingup: Keep going notification

Reason:

squashed into I72c1840414fd67dd7c92b05c29eac9c0a0577e9b

https://gerrit.wikimedia.org/r/894048

Apps shouldn't be checked

That sounds fine, but...

or available to adjust.

... would be extra work; do we need to do this? If a user decides they want these notices available in app, why not allow them?

In T331076#8668589, @kostajh wrote:

Apps shouldn't be checked

That sounds fine, but...

or available to adjust.

... would be extra work; do we need to do this? If a user decides they want these notices available in app, why not allow them?

OK, I'll remove that requirement.
I was just worried that the link to suggested edits would break in the app... but maybe that's not the case. Would those links just open outside of the app?

On an aside, the current description of the Growth notification group is "Notify me about newcomer tasks and other Growth team features designed to improve new editor retention." which doesn't seem very meaningful to a new user.

Apps is now checked by default (as it copies the web default settings). Maybe we could wait and see in beta how the notification works in the app (I don't think there's a way to set up the app to use a local developer machine)? I'd expect it to open special pages in a web browser or an embedded browser.

Change 894043 merged by jenkins-bot:

[mediawiki/extensions/GrowthExperiments@master] levelingup: Keep going notification

https://gerrit.wikimedia.org/r/894043

On an aside, the current description of the Growth notification group is "Notify me about newcomer tasks and other Growth team features designed to improve new editor retention." which doesn't seem very meaningful to a new user.

@Tgr good point. I was trying to ensure the description provided enough information for experienced users to help them connect the notifications to the Growth team (if they have questions or concerns), while also being generic enough that this notification type could potentially be used for other Growth team notifications in the future. I'm definitely open to improved language if you have any suggestions!

@RHo & @Trizek-WMF - this task was added just recently, so didn't go through the standard Positive Reinforcement Copy review yet. Please feel free to suggest alternate copy.

I'm not sure to understand what was decided for Apps. Apps should be a greyed option, as our features aren't available on Apps. Wouldn't it be counter-productive to send a notification on Apps for a feature that is not present there?

Regarding the copy, I'm reluctant to add a new term but the best description of our features to a newcomer is "Onboarding features". But we should go with "Growth features" for branding consistency and future evolutions (that might require to have separated notification options).

Also, for newcomers, Growht features are part of their normal environment, so as matching notifications. Notifications preferences are here for advanced users, mostly.

I'm not sure to understand what was decided for Apps. Apps should be a greyed option, as our features aren't available on Apps. Wouldn't it be counter-productive to send a notification on Apps for a feature that is not present there?

As of now, the plan is to not show this notification by default in the apps.
What's still debatable is if it's OK to leave that notification option available or if we should grey out that option for Apps / not allow this notification to ever appear within the apps. As you mentioned, very few newcomers adjust their preferences, so it's an edge case I'm not too worried about, but I'll also check in with @JTannerWMF about this to get an app team perspective.

In T331076#8673434, @KStoller-WMF wrote:

I'm not sure to understand what was decided for Apps. Apps should be a greyed option, as our features aren't available on Apps. Wouldn't it be counter-productive to send a notification on Apps for a feature that is not present there?

As of now, the plan is to not show this notification by default in the apps.
What's still debatable is if it's OK to leave that notification option available or if we should grey out that option for Apps / not allow this notification to ever appear within the apps. As you mentioned, very few newcomers adjust their preferences, so it's an edge case I'm not too worried about, but I'll also check in with @JTannerWMF about this to get an app team perspective.

FWIW I agree that it may be confusing and would suggest greying out the apps notification option until we revise and improve the UX of the homepage and suggested edits when it is shown in the apps. @Etonkovidova did some initial testing of Growth features on apps a while back on T299172 which shows that it is not really so usable at present.

In T331076#8673030, @KStoller-WMF wrote:

I was trying to ensure the description provided enough information for experienced users to help them connect the notifications to the Growth team (if they have questions or concerns), while also being generic enough that this notification type could potentially be used for other Growth team notifications in the future. I'm definitely open to improved language if you have any suggestions!

I think as long as it's clearly marked to be about new users, experienced users won't really care about it. It's not trivial to connect individual notifications to notification categories in any case. If I had to do it, I'd probably have to use uselang=qqx and try to figure out the extension name from the messages it uses.

(The Echo preferences UI could use some improvement. The related tasks seem to be T158756 and T132977.)

I'd go with something like Notify me about tasks for newcomers and other features designed to help new users.

In T331076#8673151, @Trizek-WMF wrote:

I'm not sure to understand what was decided for Apps. Apps should be a greyed option, as our features aren't available on Apps. Wouldn't it be counter-productive to send a notification on Apps for a feature that is not present there?

No apps option is currently greyed out; I'm sure there are other notifications which link to places which don't work well in the apps. So probably it's not so easy to do? (The app/push notification type was added later than the other two, and in a somewhat hacky way, I think.)

Thanks for the info and copy suggestions. So we have:

Notification category: Growth features

Information: Notify me about tasks for newcomers and other features designed to help new users.

@kostajh Does that sound OK to you? Sorry for shifting copy requirements!

Change 896100 had a related patch set uploaded (by Kosta Harlan; author: Kosta Harlan):

[mediawiki/extensions/GrowthExperiments@master] i18n: Adjust wording for Growth features notifications

https://gerrit.wikimedia.org/r/896100

In T331076#8678307, @KStoller-WMF wrote:

Thanks for the info and copy suggestions. So we have:

Notification category: Growth features

Information: Notify me about tasks for newcomers and other features designed to help new users.

@kostajh Does that sound OK to you? Sorry for shifting copy requirements!

LGTM!

Change 896100 merged by jenkins-bot:

[mediawiki/extensions/GrowthExperiments@master] i18n: Adjust wording for Growth features notifications

https://gerrit.wikimedia.org/r/896100

Change 897422 had a related patch set uploaded (by Gergő Tisza; author: Gergő Tisza):

[mediawiki/extensions/GrowthExperiments@master] Leveling up: Disable push notifications by default

https://gerrit.wikimedia.org/r/897422

Change 897431 had a related patch set uploaded (by Gergő Tisza; author: Gergő Tisza):

[mediawiki/extensions/GrowthExperiments@master] Leveling up: Disallow push notifications

https://gerrit.wikimedia.org/r/897431

Change 897422 merged by jenkins-bot:

[mediawiki/extensions/GrowthExperiments@master] Leveling up: Disable push notifications by default

https://gerrit.wikimedia.org/r/897422

Change 897431 merged by jenkins-bot:

[mediawiki/extensions/GrowthExperiments@master] Leveling up: Disallow push notifications

https://gerrit.wikimedia.org/r/897431

In T331076#8678307, @KStoller-WMF wrote:

Notification category: Growth features

Information: Notify me about tasks for newcomers and other features designed to help new users.

Sorry for the very slow followup on this, but I'm a bit skeptical about using the team name for branding. Do we know what fraction of editors are aware there is a Growth team (or a foundation, for that matter)? I feel without that context the category name is hard to interpret (growth of what?).

@Tgr - "Growth features" wasn't my initial suggestion, but suggested by @Trizek-WMF:

In T331076#8673151, @Trizek-WMF wrote:

Regarding the copy, I'm reluctant to add a new term but the best description of our features to a newcomer is "Onboarding features". But we should go with "Growth features" for branding consistency and future evolutions (that might require to have separated notification options).

I'm still fine with "Newcomer onboarding" or something more general, but I also appreciate Trizek-WMF's point that it's generally more advanced users updating these notification settings, so perhaps it's good to connect them to the Growth team?