Replace the launchpad-first flag with the goals-first cumulative experiment

[p-jackson]

Fixes #99879

Proposed Changes

I thought I would simply take the hook approach we've usually taken for experiments: replacing the shouldShowLaunchpadFirst() function with a useShouldShowLaunchpadFirst(). And it'd even be able to share logic with the useGoalsFirstCumulativeExperience() hook 👍.

The difference with this experiment though is that we need access to experiment assignment in the My Home control, and we can't use hooks there. So instead, this PR uses a promise-based approach to loading the experiment assignment, and wraps it in a hook when it needs to be used in React components.

• Convert shouldShowLaunchpadFirst() into an async function
• Replace the feature flag check with an experiment assignment
• Add logic to ensure we only give users the launchpad first experience when their site was created after the goals-first experiment started
  • Otherwise we'll be treating them as if they were in the cumulative experience when they never created their site with the goals-first experiment at all
• Create useGoalsFirstCumulativeExperience() hook for wrapping the shouldShowLaunchpadFirst()

With Experiment

CleanShot.2025-02-18.at.21.58.22.mp4

Control
(excuse the debugger 🙂)

CleanShot.2025-02-18.at.22.23.51.mp4

Why are these changes being made?

• Switching from a feature flag to an experiment allows us to actually launch to customers.

Testing Instructions

• Assign yourself to an experiment cohort here: 22180-explat-experiment
• Test on a site you created a while ago (you should not get the focused launchpad)
• Test on a fresh site (you should get the focused launchpad if you were in the cumulative variant)
• Test with Big Sky, you should not see the launchpad

Pre-merge Checklist

• Has the general commit checklist been followed? (PCYsg-hS-p2)
• Have you written new tests for your changes?
• Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
• Have you checked for TypeScript, React or other console errors?
• Have you used memoizing on expensive computations? More info in Memoizing with create-selector and Using memoizing selectors and Our Approach to Data
• Have we added the "[Status] String Freeze" label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?
  • For UI changes, have we tested the change in various languages (for example, ES, PT, FR, or DE)? The length of text and words vary significantly between languages.
• For changes affecting Jetpack: Have we added the "[Status] Needs Privacy Updates" label if this pull request changes what data or activity we track or use (p4TIVU-aUh-p2)?

[github-actions]

Calypso Live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-133744

Jetpack Cloud live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-133744&env=jetpack

Automattic for Agencies live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-133744&env=a8c-for-agencies

[matticbot]

This PR modifies the release build for the following Calypso Apps:

For info about this notification, see here: PCYsg-OT6-p2

• blaze-dashboard
• odyssey-stats

To test WordPress.com changes, run install-plugin.sh $pluginSlug feature-flag-to-experiment on your sandbox.

[matticbot]

Here is how your PR affects size of JS and CSS bundles shipped to the user's browser:

Sections (~450 bytes added 📈 [gzipped])

name                  parsed_size           gzip_size
home                       +473 B  (+0.0%)     +247 B  (+0.0%)
write-flow                 +446 B  (+0.0%)     +203 B  (+0.0%)
link-in-bio-tld-flow       +446 B  (+0.0%)     +203 B  (+0.0%)
build-flow                 +446 B  (+0.0%)     +203 B  (+0.1%)

Sections contain code specific for a given set of routes. Is downloaded and parsed only when a particular route is navigated to.

Legend

What is parsed and gzip size?

Parsed Size: Uncompressed size of the JS and CSS files. This much code needs to be parsed and stored in memory.
Gzip Size: Compressed size of the JS and CSS files. This much data needs to be downloaded over network.

Generated by performance advisor bot at iscalypsofastyet.com.

[candy02058912]

✅ Test on a site you created a while ago (you should not get the focused launchpad)
✅ Test on a fresh site (you should get the focused launchpad if you were in the cumulative variant)
✅ Test with Big Sky, you should not see the launchpad

Might circle back to check the code more in detail tomorrow, but tested all the scenarios and it's working 👍

[paulopmt1]

It's working as expected, thanks @p-jackson!

Let's release it tomorrow morning :)

[paulopmt1]

Nice improvement!