Skip to content

Mobile app reopens the last-used screen after the app is killed instead of starting at Home #94209

Closed

Description

@Julesssss

Problem

When the app is killed (by the user or OS) and reopened while user is set to NewDot, the app reopens at the last-used screen instead of starting fresh at the home page. This is notably different from mobile native apps. As a user I have to navigate back from nested pages in order to land at the home page to get to our landing home page, it adds extra steps to our main workflows and is confusing to users. This affects both iOS and Android.

Added here originally. I raised this for discussion in #product.

1. User's last used page is Agents, user closes app, simulate OS killing app in background (I cut off capture early for privacy)

killed-open-1.mp4

2. User opens cold app, lands at last used page instead of home page

killed-open-2.mp4

Solution

On cold launch the shared OldDot handoff (TryNewDotManager.navigateToNewDot()) passes a null deeplink, and native ReactNativeManager (.kt/.swift) skips updating on null so getInitialURL() returns nothing. A targeted fix is to hand NewDot an explicit Home URL on the cold-launch handoff (mirroring the existing "Try New Expensify" behaviour) rather than changing the shared last-visited-path restore that in-session reloads depend on.

Activity

  1. self-assigned this
    on Jun 22, 2026
  2. changed the title [-]NewDot reopens the last-used screen after the app is killed instead of starting at Home[/-] [+]Mobile app reopens the last-used screen after the app is killed instead of starting at Home[/+] on Jun 22, 2026
  3. Julesssss commented on Jun 23, 2026

    @Julesssss
    ContributorAuthor

    Wrote up a P/S for this so we can properly discuss this as a team:


    Proposal: The NewDot Mobile app should open to the Home page when cold launched

    The Home tab is the landing page for New Expensify and is a great place for users to see what needs attention, whether it's expenses needed to be dealt with or a broken connection.

    iOS and Android applications are automatically killed by the operating system (or user) to free up device resources after they have been closed/backgrounded for a short period of time. When users return to that app after it was killed, a cold launch occurs and users will be taken to the app homepage.

    In many apps including ours, the splash screen typically indicates a cold launch.

    Problem

    When a NewDot user opens the mobile app, if it was been killed in the background by the user or OS, then they land at their last viewed page instead of the home page.

    Solution

    We should remove this behaviour and consistently take users to the Home page when the app is launched from cold start.

    Users should be linked deeper into our navigation for specific cases: for example when tapping a push notification from a chat, tapping a deep link, or when the app is already open but running in the background.

  4. Julesssss commented on Jun 24, 2026

    @Julesssss
    ContributorAuthor

    Shared the proposal here.

  5. Julesssss commented on Jun 27, 2026

    @Julesssss
    ContributorAuthor

    Discussing still

  6. Julesssss commented on Jul 13, 2026

    @Julesssss
    ContributorAuthor

    Discussion held. Need to find a moment to respond.

  7. Julesssss commented on Aug 19, 2026

    @Julesssss
    ContributorAuthor

    Not a priority, will return later if customer data shows this to be a problem.

  8. Julesssss commented on Sep 1, 2026

    @Julesssss
    ContributorAuthor

    Thread here discussing importance of highlighting urgency for outstanding reports.

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

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions