Skip to content

Add granular signup qualifier values backwards-compatibly#90348

Open
neil-marcellini wants to merge 1 commit into
mainfrom
agent/granular-signup-qualifiers
Open

Add granular signup qualifier values backwards-compatibly#90348
neil-marcellini wants to merge 1 commit into
mainfrom
agent/granular-signup-qualifiers

Conversation

@neil-marcellini
Copy link
Copy Markdown
Contributor

(Neil's AI agent)

Explanation of Change

Adds two new signup qualifier values that the landing page can send without breaking older App clients, in preparation for splitting the landing page brackets from 1-9 / 10+ into 1-4 / 5+ (Web-Expensify #52332 and a follow-up landing page PR).

New qualifier values (in CONST.ONBOARDING_SIGNUP_QUALIFIERS):

  • VSB_1_4 → wire-format vsb-1-4 — landing page "1-4 employees"
  • SMB_5_PLUS → wire-format smb-5-plus — landing page "5+ employees"

Both fit the existing _SIMPLENAME WAF rule ([\w@., -]{1,64}) on Web-Expensify, so no input rule change is needed for them to pass signUp validation.

Why this approach is safe for old clients:
The App keys all behavior off exact string matches like signupQualifier === 'vsb' / === 'smb'. An old App build that hasn't picked up this PR will see vsb-1-4 / smb-5-plus, return false from every isVsb/isSmb check, and fall into the default onboarding flow that shows the full company-size list. Slightly more clicks for those users but no missing options, no wrong routing, no broken state.

Updated client behavior (this PR):

  • Introduces src/libs/SignupQualifierUtils.ts with isVsbQualifier() / isSmbQualifier() helpers that treat the legacy and granular values as members of the same family. Replaces 14 inline === VSB / === SMB checks across 8 onboarding files with the helpers so future qualifier additions don't fan out across the codebase.
  • OnboardingFlow.ts: pre-sets companySize = MICRO_SMALL ("1-4") for vsb-1-4 so the stored data matches what the user said on the landing page. Legacy vsb continues to map to MICRO ("1-10") for backwards compatibility.
  • BaseOnboardingEmployees.tsx: under smb-5-plus, only 1-4 is hidden — 5-10 stays visible because the user said "5+", not "10+". Legacy smb continues to hide both 1-4 and 5-10.
  • getOnboardingStepCounter.ts: adds the new qualifiers to the exhaustive qualifierSuffixes map so the step counter shows the right total for users on the new flow.

vsb / smb keep their historical meaning forever at the data layer — historical NVPs, marketing dashboards, and Meta SignUp event audiences keyed on them remain accurate.

Companion PRs (deploy in any order — each is independently safe):

  • Auth: optional (no validation change required; constants would only document the new values for parity)
  • Web-Expensify #52332: needs to be updated to send the new qualifier value attributes (vsb-1-4 / smb-5-plus) in addition to the new label text. As-is the PR only changes the visible labels and would break the in-app flow for users picking "5+".

Marketing/growth heads-up needed: the new strings will start appearing in the Meta SignUp conversion event (window.fbq('trackCustom', 'SignUp', {qualifier}) in homepage/js/signin.jsx) and in the introSelected.signupQualifier NVP. New analytics queries need to handle the four-value space (vsb, smb, vsb-1-4, smb-5-plus).

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/613539

Tests

(Neil's AI agent)

Automated tests (run with npx jest tests/unit/libs/SignupQualifierUtilsTest.ts tests/unit/libs/OnboardingFlowTest.ts tests/ui/OnboardingEmployees.tsx):

  • SignupQualifierUtilsTest.ts (12 tests) — verifies legacy and granular values are correctly grouped, INDIVIDUAL/null/undefined are not, and the wire-format strings match vsb-1-4 / smb-5-plus exactly.
  • OnboardingFlowTest.ts (5 tests) — verifies vsb-1-4 pre-sets companySize = "1-4", legacy vsb keeps pre-setting "1-10", smb-5-plus sets MANAGE_TEAM purpose without pre-setting a size, and routes to the employees step.
  • tests/ui/OnboardingEmployees.tsx (3 tests, 1 new) — adds a case verifying that smb-5-plus keeps 5-10 visible while hiding 1-4 and the legacy 1-10.

TDD verification was done by reverting the implementation, confirming the new tests fail (they did — 5 explicit failures plus compile errors on the new CONST keys), then reapplying the implementation and watching all 19 tests pass.

Manual dev testing (cannot exercise the new path end-to-end until the landing page is updated to send the new strings, since signUp is the only producer of signupQualifier). Verified existing legacy paths still work:

  1. Sign in as a brand-new user without a landing-page qualifier → default onboarding flow shows the full company-size list (1-4 through 1001+).
  2. Sign in as a brand-new user with signupQualifier=smb (legacy SMB path) → the employees step still hides 1-4, 5-10, and 1-10.
  3. Sign in as a brand-new user with signupQualifier=vsb (legacy VSB path) → still skips the employees step and pre-sets companySize=1-10, still routes to accounting.

Once the landing-page PR is up I'll add a follow-up dev video showing the new vsb-1-4 and smb-5-plus paths.

  • Verify that no errors appear in the JS console

Offline tests

No offline-specific behavior changes — signup qualifiers are written during online signup and read from the locally-cached onboarding NVP afterwards, which already works offline.

QA Steps

(Neil's AI agent)

This PR is a no-op until the landing page starts sending the new strings, so QA on the existing legacy paths is sufficient to confirm no regressions:

  1. Sign in as a brand-new user (no landing-page qualifier) and select "Manage my team's expenses".
  2. On the employees step, verify the available options are: 1-4, 5-10, 11-50, 51-100, 101-1000, 1001+ (no 1-10).
  3. Sign in as a brand-new user via the existing landing page "Manage expenses for 1-9 employees" option (legacy vsb).
  4. Verify the user is routed past the employees step directly to accounting — no regression vs. main.
  5. Sign in as a brand-new user via the existing landing page "Manage expenses for 10+ employees" option (legacy smb).
  6. Verify the employees step shows only 11-50, 51-100, 101-1000, 1001+ (no 1-4, 5-10, or 1-10) — no regression vs. main.
  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct) — N/A, no input validation changes
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability). — N/A, no API or large data fetches
  • I included screenshots or videos for tests on all platforms — covered by automated CI builds; no UI changes that differ across platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native (covered by CI)
    • Android: mWeb Chrome (covered by CI)
    • iOS: Native (covered by CI)
    • iOS: mWeb Safari (covered by CI)
    • MacOS: Chrome / Safari
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I followed proper code patterns (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text shown in the product is localized — N/A, no user-facing copy changes
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods — N/A
    • I verified any copy / text that was added to the app is grammatically correct in English — N/A, no copy changes
    • I verified proper file naming conventions were followed for any new files or renamed files
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers — isVsbQualifier / isSmbQualifier helpers replace duplicated inline string equality checks; same pattern as similar utility modules in src/libs/
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes — covered by the existing tests for OnboardingEmployees, OnboardingFlow, and the new helper unit tests
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
  • I verified that if a function's arguments changed that all usages have also been updated correctly — no signature changes
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that — N/A
  • If new assets were added or existing ones were modified — N/A
  • If the PR modifies code that runs when editing or sending messages — N/A
  • If the PR modifies a generic component — N/A
  • If the PR modifies a component related to any of the existing Storybook stories — N/A
  • If the PR modifies a component or page that can be accessed by a direct deeplink — onboarding pages can be deeplinked but the change is purely additive to the qualifier set; existing routes still work as before
  • If the PR modifies the UI — N/A, behavior change only
  • If a new page is added — N/A
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • If the main branch was merged into this PR after a review, I tested again — branch is up to date with main as of branch creation

Made with Cursor

Introduces two new signup qualifier values that the landing page can send
without breaking older App clients:

- vsb-1-4 — replaces the historical "1-9 employees" landing page bracket
- smb-5-plus — replaces the historical "10+ employees" landing page bracket

Old App clients string-match exclusively on `vsb` / `smb`, so unknown
values fall through to the default onboarding flow with the full company
size list. Updated clients recognize the new strings via shared
`isVsbQualifier` / `isSmbQualifier` helpers and:

- Pre-set `companySize=MICRO_SMALL` ("1-4") for `vsb-1-4` so stored data
  matches what the user said. Legacy `vsb` keeps mapping to `MICRO`.
- Show the employees step for `smb-5-plus` with `1-4` hidden but `5-10`
  still visible. Legacy `smb` continues to hide both small-team options.

Tests cover the helpers, the `OnboardingFlow` pre-set logic, and the
`OnboardingEmployees` filter behavior under each qualifier.

Co-authored-by: Cursor <cursoragent@cursor.com>
@neil-marcellini neil-marcellini requested review from a team as code owners May 12, 2026 15:01
@melvin-bot melvin-bot Bot requested review from a team and thelullabyy and removed request for a team May 12, 2026 15:01
@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented May 12, 2026

@thelullabyy Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@melvin-bot melvin-bot Bot requested review from JmillsExpensify and abzokhattab and removed request for a team May 12, 2026 15:01
@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented May 12, 2026

@abzokhattab Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

// VSB/SMB have fixed suffixes; individual (null) is handled via purposeSuffixes.
// VSB_1_4 follows the same flow as legacy VSB (the company size is pre-set so the
// employees step is skipped). SMB_5_PLUS follows the same flow as legacy SMB.
const qualifierSuffixes = {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❌ CONSISTENCY-3 (docs)

The suffix arrays for VSB and VSB_1_4 are identical, and the suffix arrays for SMB and SMB_5_PLUS are also identical. If the flow for either group changes, both entries must be updated in lockstep, which is error-prone.

Extract the shared arrays into named constants and reference them from both keys:

const VSB_SUFFIXES = [ONBOARDING.ACCOUNTING, ONBOARDING.INTERESTED_FEATURES];
const SMB_SUFFIXES = [ONBOARDING.EMPLOYEES, ONBOARDING.ACCOUNTING, ONBOARDING.INTERESTED_FEATURES];

const qualifierSuffixes = {
    [ONBOARDING_SIGNUP_QUALIFIERS.VSB]: VSB_SUFFIXES,
    [ONBOARDING_SIGNUP_QUALIFIERS.VSB_1_4]: VSB_SUFFIXES,
    [ONBOARDING_SIGNUP_QUALIFIERS.SMB]: SMB_SUFFIXES,
    [ONBOARDING_SIGNUP_QUALIFIERS.SMB_5_PLUS]: SMB_SUFFIXES,
    [ONBOARDING_SIGNUP_QUALIFIERS.INDIVIDUAL]: null,
} satisfies Record<ValueOf<typeof ONBOARDING_SIGNUP_QUALIFIERS>, OnboardingScreen[] | null>;

Reviewed at: ce78964 | Please rate this suggestion with 👍 or 👎 to help us improve! Reactions are used to monitor reviewer efficiency.

@codecov
Copy link
Copy Markdown

codecov Bot commented May 12, 2026

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines Coverage Δ
src/CONST/index.ts 92.30% <ø> (ø)
src/libs/SignupQualifierUtils.ts 100.00% <100.00%> (ø)
src/libs/actions/Welcome/OnboardingFlow.ts 76.85% <100.00%> (+0.43%) ⬆️
src/libs/getOnboardingStepCounter.ts 100.00% <ø> (ø)
...es/OnboardingEmployees/BaseOnboardingEmployees.tsx 95.12% <100.00%> (+1.18%) ⬆️
...gPersonalDetails/BaseOnboardingPersonalDetails.tsx 92.39% <100.00%> (ø)
...es/OnboardingWorkEmail/BaseOnboardingWorkEmail.tsx 82.53% <100.00%> (ø)
...ilValidation/BaseOnboardingWorkEmailValidation.tsx 93.18% <100.00%> (ø)
.../OnboardingWorkspaces/BaseOnboardingWorkspaces.tsx 97.46% <100.00%> (ø)
.../OnboardingAccounting/BaseOnboardingAccounting.tsx 1.72% <0.00%> (ø)
... and 1 more
... and 6 files with indirect coverage changes

@thelullabyy
Copy link
Copy Markdown
Contributor

thelullabyy commented May 12, 2026

Reviewer Checklist

  • I have verified the author checklist is complete (all boxes are checked off).
  • I verified the correct issue is linked in the ### Fixed Issues section above
  • I verified testing steps are clear and they cover the changes made in this PR
    • I verified the steps for local testing are in the Tests section
    • I verified the steps for Staging and/or Production testing are in the QA steps section
    • I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I checked that screenshots or videos are included for tests on all platforms
  • I included screenshots or videos for tests on all platforms
  • I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
  • I verified tests pass on all platforms & I tested again on:
    • Android: HybridApp
    • Android: mWeb Chrome
    • iOS: HybridApp
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
  • I verified proper code patterns were followed (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I verified that this PR follows the guidelines as stated in the Review Guidelines
  • I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately and each prop has a /** comment above it */
    • The file is named correctly
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
    • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
    • All JSX used for rendering exists in the render method
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp
Android: mWeb Chrome
iOS: HybridApp
iOS: mWeb Safari
MacOS: Chrome / Safari

@thelullabyy
Copy link
Copy Markdown
Contributor

@codex review

@chatgpt-codex-connector
Copy link
Copy Markdown

Codex Review: Didn't find any major issues. You're on a roll.

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

@thelullabyy
Copy link
Copy Markdown
Contributor

@neil-marcellini Kindly finish/tick all the checkbox in PR desc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants