Tailor in-app pre-boarding (before sign-up) experience

[Adal3n3]

Problem to solve

Description

Targeting to new customers, the problem starts from when the pre-release customers come to the Codecov app to sign-up, and they have to go to the Code coverage onboarding flow which will be confusing to them as it's not very obvious that code coverage and pre-release features are not related. For the first time users, they might not know where the pre-release features are located in the app.

Steps to Reproduce / Current UX

Draft some visual mocks to review

Possible solution

Marketing team has core 4 pages which is blogs, pricing page, docs and the features page. Potentially, the pre-release features will live on the Sentry marketing site. @cassie-codecov shows us there might be a new section named "Pre-release" and show 1/ BA 2/Test ingestion 3/Flaky tests.

We can tailor the in-app onboarding experience based on the link. For example,

1. url/xxx/xxx ----> show Coverage intro
2. url/xxx/xxx ----> show BA intro
3. url/xxx/xxx ----> show Test ingestion intro
4. url/xxx/xxx ----> show Everything combined intro

Action Checklist for Issue Creation

• Add the design project (to the right under "projects" > settings icon > select "design team")
• Share in relevant Slack channel (#discuss-codecov-product-design) for visiblity
• Add targeted launch date/delivery date as/if needed

Additional Information

Figma: link

[codecovdesign]

@Adal3n3 @rohan-at-sentry @aj-codecov

• This is really helpful to share with user and helps set expectations
• Where it lives is another question; it'd be great to leverage this on the respective feature section (empty state?) or after gh installation etc.
  • Concern is with location in current flow is that it's repeats what's already seen on marketing site (unless there is new information?) and shown at a time where higher priorities exist (GitHub app installation + org/repo selection). It is not immediately actionable in it's current placement in the flow and doesn't help with those priority selections.
• In terms of breaking to smaller iterations and prioritization: if the problem is around improving their flow to the respective feature of their interest; I'd recommend improving re-directs and navigation (shouldn't rely on a visual to show them how to get somewhere, it should be apparent in the navigation flow - if it's not that should be fixed)
  • Since pre-release isn't fully baked + only BA has it's temporary location; this may be a bit premature as an onboarding flow item.