Skip to content

[BT-149] Migrate Onboarding (Part 2) #83871

Closed

Description

@mjasikowski

Description

Current State:

  • 5 routes for onboarding features and work email
  • These routes use backTo parameter for return navigation

Implementation:

  • Replace getRoute(..., backTo) with createDynamicRoute()
  • Add source screens to entryScreens array
  • Remove backTo parameter from route definitions
  • Test forward/back navigation

Scope

Routes (5):

Route Constant Path
ONBOARDING_INTERESTED_FEATURES onboarding/interested-features
ONBOARDING_PURPOSE onboarding/purpose
ONBOARDING_WORKSPACES onboarding/join-workspaces
ONBOARDING_WORK_EMAIL onboarding/work-email
ONBOARDING_WORK_EMAIL_VALIDATION onboarding/work-email-validation

Usages

ONBOARDING_INTERESTED_FEATURES:

  • Search for usages in features selection flow

ONBOARDING_PURPOSE:

  • Search for usages in purpose selection flow

ONBOARDING_WORKSPACES:

  • Search for usages in workspaces join flow

ONBOARDING_WORK_EMAIL:

  • Search for usages in work email flow

ONBOARDING_WORK_EMAIL_VALIDATION:

  • Search for usages in work email validation flow

Files to modify:

  • src/ROUTES.ts - Update route definitions
  • src/libs/Navigation/types.ts - Remove backTo from params
  • Components listed above

Migration Progress

  • ONBOARDING_INTERESTED_FEATURES
  • ONBOARDING_PURPOSE
  • ONBOARDING_WORKSPACES
  • ONBOARDING_WORK_EMAIL
  • ONBOARDING_WORK_EMAIL_VALIDATION
Issue OwnerCurrent Issue Owner: @suneox

Activity

  1. added
    InternalRequires API changes or must be handled by Expensify staff
    on Mar 2, 2026
  2. 5 remaining items

  3. melvin-bot commented on Jun 8, 2026

    @melvin-bot

    This issue has not been updated in over 15 days. @mananjadhav, @mjasikowski, @huult eroding to Monthly issue.

    P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!

  4. added
    Skip PaymentSkips all the payment process steps for an issue. Use it for fixed-price projects.
    on Jun 24, 2026
  5. huult commented on Jul 29, 2026

    @huult
    Contributor

    Only two routes that use backTo need to be migrated: ONBOARDING_PURPOSE and ONBOARDING_WORKSPACES.

  6. huult commented on Aug 14, 2026

    @huult
    Contributor

    ONBOARDING_WORKSPACES and ONBOARDING_PURPOSE don't fit the dynamic-route mechanism because they are fixed onboarding wizard steps with state-driven navigation, backTo passed through the flow, and custom forceReplace/refresh handling. I recommend skipping the remaining ONBOARDING_* routes and treating onboarding navigation as a separate refactor.

  7. huult commented on Aug 14, 2026

    @huult
    Contributor

    @mjasikowski Per #83870 (comment), I think we can close this ticket since there's nothing we need to do here.

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

Metadata

Metadata

Labels

InternalRequires API changes or must be handled by Expensify staffMonthlyKSv2Skip PaymentSkips all the payment process steps for an issue. Use it for fixed-price projects.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions