[adamgrzybowski]

Explanation of Change

• The empty "For You" section was shown to newly onboarded users with no workspace (new-vs-old detection relied on the free-trial date, which only exists after a workspace is created). Now we fall back to the onboarding record: NewDot-onboarded accounts are treated as new (section hidden), old/migrated accounts keep it.
• Not ideal: the onboarding NVP has no timestamp, so a NewDot user who onboarded before the cutoff but never created a workspace is also treated as new. A proper fix needs a backend account-creation-date signal; this is a pragmatic client-side fix for the deploy blocker.

Fixed Issues

$ #95865
PROPOSAL:

Tests

1. Create a brand-new account and complete onboarding with the "Something else" intent (do not create a workspace).
2. Go to Home.
3. Verify the "For You" section is hidden (not shown empty).
4. Create a workspace, return to Home, and verify the section still behaves correctly (hidden while empty, shown once there is an actionable to-do).
5. Verify that no errors appear in the JS console.

• Verify that no errors appear in the JS console

Offline tests

Same as Tests.

QA Steps

1. On staging, sign up with a new account and complete onboarding with the "Something else" intent, without creating a workspace.
2. Navigate to Home and verify the empty "For You" section is hidden.
3. Create a workspace, go back to Home, and verify the section behaves as expected (hidden while empty).

• 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)
  • 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).
• I included screenshots or videos for tests on all platforms
• I ran the tests on all platforms & verified they passed on:
  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • 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 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 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)
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I followed the guidelines as stated in the Review Guidelines
• I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• 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 new assets were added or existing ones were modified, I verified that:
  • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
  • The assets load correctly across all supported platforms.
• 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.
• 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 and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

Screen.Recording.2026-07-13.at.16.55.07.mov

[melvin-bot]

@ZhenjaHorbach 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]

[ZhenjaHorbach]

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 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 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)
• 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)
• If a new component is created I verified that:
  • A similar component doesn't exist in the codebase
  • All props are defined accurately
  • 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
  • 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 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.
• 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

2026-07-14.14.42.47.mov

Android: mWeb Chrome

2026-07-14.14.37.36.mov

iOS: HybridApp

2026-07-14.14.42.47.mov

iOS: mWeb Safari

2026-07-14.14.37.36.mov

MacOS: Chrome / Safari

2026-07-14.14.35.24.mov

[adamgrzybowski]

@grgia Let's merge this

[github-actions]

🚧 grgia has triggered a test Expensify/App build. You can view the workflow run here.

[github-actions]

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #95969.

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-2f055605f52-84c49dd-5a021d4fe9ae75735fc026dfacf05fe588cf13ca/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-2f05560-84c49dd-f065827895cb9a08ccfa6514c3f5a916c67a361d/index.html

Web 🕸️
https://95969.pr-testing.expensify.com

---

👀 View the workflow run that generated this build 👀

[OSBotify]

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

[OSBotify]

🚀 Deployed to staging by https://github.com/grgia in version: 9.4.36-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

[MelvinBot]

🤖 I reviewed this change against the help site articles under docs/articles and applied the naming conventions, authoring guidelines, and template.

Conclusion: no help site changes are required — no draft PR created.

This PR is an internal visibility-logic bug fix (the deploy blocker in #95865). It changes when an empty For you section is hidden — NewDot-onboarded accounts with no workspace now have the empty section hidden, while old/migrated accounts keep it — but it does not change any documented, user-facing capability of the feature.

The one article that covers this feature, Understanding-the-For-you-Section.md, already describes the section as one that "may appear empty" when nothing needs your attention (see its "Who sees the For you section" and "What it means when the For you section is empty" sections). That statement remains accurate after this change, and the new/old-account classification driving the hide behavior is an implementation detail (and, per the PR description, a deliberately imperfect heuristic pending a backend signal) that isn't — and shouldn't be — surfaced in the help docs.

@adamgrzybowski, please confirm you agree no help site update is needed here. If you'd like the "For you" article to explicitly call out that a brand-new account won't see the section until it has a to-do, let me know and I'll open a draft PR for that copy.

[OSBotify]

🚀 Deployed to staging by https://github.com/grgia in version: 9.4.38-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	cancelled 🔪
🍎 iOS 🍎	cancelled 🔪

[MelvinBot]

🤖 I reviewed the changes in this PR against the help site files under docs/articles.

Conclusion: No help site changes are required. I did not create a draft PR.

Why

This PR is a client-side deploy-blocker fix for the internal logic that decides whether the empty For you section on Home is hidden vs. shown empty. It falls back to the onboarding NVP so newly onboarded users with no workspace (and therefore no free-trial date) are correctly treated as new and the empty section is hidden.

It does not add, rename, or remove any user-facing feature, section, button, or workflow.

I checked the two articles that cover this area:

• new-expensify/getting-started/Understanding-the-For-you-Section.md
• new-expensify/getting-started/Expensify-Home-Overview.md

Both describe the For you section conceptually — it surfaces items needing your attention and "may appear empty" when you're caught up. That description remains accurate. The new-vs-old-user detail this PR corrects is a transitional, onboarding-era implementation detail that the help articles were never meant to document, and surfacing it would only confuse readers.

If you'd like the articles to explicitly explain when the empty section is hidden vs. shown for new users, let me know and I'll draft the doc updates.

[OSBotify]

🚀 Deployed to staging by https://github.com/grgia in version: 9.4.40-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

[MelvinBot]

🤖 I reviewed the changes in this PR against the help site files under docs/articles.

No help site changes are required.

This PR is an internal bug fix that changes when the empty For you section is hidden on Home — falling back to the onboarding NVP so newly onboarded users with no workspace don't see an empty section, while old/migrated accounts keep it. This is a nuanced client-side detection change (free-trial date vs. onboarding origin); it doesn't rename a feature, tab, setting, or button, and the new-vs-migrated distinction isn't user-facing terminology.

The two existing articles that cover this section already describe the behavior accurately:

• Understanding-the-For-you-Section.md — "If nothing requires your attention, the section may appear empty."
• Expensify-Home-Overview.md — "If there's nothing that needs action, the For you section may appear empty."

The "may appear empty" phrasing already covers both outcomes (shown-but-empty for old/migrated accounts, hidden for new accounts), so no wording is contradicted by this change. Documenting the underlying account-type signal would add internal detail that isn't meaningful to end users.

Because no help site changes are needed, I haven't opened a docs draft PR. adamgrzybowski, please confirm you agree with this assessment — if you think the articles should call out that the empty section is hidden for newly onboarded users, let me know and I'll draft the update.

[OSBotify]

🚀 Deployed to production by https://github.com/yuwenmemon in version: 9.4.40-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

Bundle Size Analysis (Sentry):

• Android