Skip to content

feat: Enable Insights and comparisons on desktop web - #104591

Merged
luacmartins merged 3 commits into
mainfrom
cmartins-insights-web-first
Oct 21, 2026
Merged

luacmartins merged 3 commits into
mainfrom
cmartins-insights-web-first

Conversation

@luacmartins

@luacmartins luacmartins commented Oct 21, 2026 •

Copy link
Copy Markdown
Contributor

Explanation of Change

Enable Insights and its comparison controls by default on desktop web only. Mobile web, iOS and Android continue to require the existing insightsPage and insightsCompare betas, so desktop can launch without waiting for the native navigation fixes and app-store rollout.

Keep both betas off globally until the mobile rollout is ready. Local beta overrides still take precedence outside production.

Related native PRs: #104368 and https://github.com/Expensify/Mobile-Expensify/pull/14193.

Fixed Issues

N/A

Tests

  1. Sign in on desktop web with an account that is not enrolled in insightsPage or insightsCompare and has no local beta overrides; confirm the Insights tab is visible.
  2. Open the same account in mobile web and iOS and Android native apps; confirm Insights remains hidden and Account remains in the tab bar.

Offline tests

N/A

QA Steps

Same as tests

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 verified any copy / text that was added to the app 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 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 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.
  • If the PR adds or modifies the UI:
    • I asked an AI agent to review the changes for accessibility issues and addressed its findings.
    • I tested with a screen reader (VoiceOver on macOS) and verified all new/changed elements are reachable with a logical focus order.
    • I verified all new/changed elements have meaningful accessible names and roles.
    • I verified state changes are announced (e.g. checked/unchecked, expanded/collapsed, selected).
  • 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

@luacmartins
luacmartins requested a review from a team October 21, 2026 16:30
@luacmartins luacmartins changed the title feat: Enable Insights on web ahead of native rollout feat: Enable Insights and comparisons on desktop web Oct 21, 2026
@luacmartins
luacmartins marked this pull request as ready for review October 21, 2026 16:41
@luacmartins
luacmartins requested a review from a team as a code owner October 21, 2026 16:41
@melvin-bot
melvin-bot Bot requested review from garrettmknight and removed request for a team October 21, 2026 16:41
@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review 🔄 Running since 2026-10-21T16:45:21.053910Z 8517d44 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@melvin-bot
melvin-bot Bot requested review from mjasikowski and removed request for a team October 21, 2026 16:45
@melvin-bot

melvin-bot Bot commented Oct 21, 2026

Copy link
Copy Markdown

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

@JS00001 JS00001 left a comment

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.

lgtm, why do this in isBetaEnabled though, why not at the level where we check if the beta is enabled?

@codecov

codecov Bot commented Oct 21, 2026 •

Copy link
Copy Markdown

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines Coverage Δ
src/libs/Permissions.ts 95.45% <50.00%> (-4.55%) ⬇️
... and 51 files with indirect coverage changes

@luacmartins
luacmartins removed the request for review from mjasikowski October 21, 2026 16:50
@luacmartins luacmartins changed the title feat: Enable Insights and comparisons on desktop web [HOLD] feat: Enable Insights and comparisons on desktop web Oct 21, 2026
@luacmartins luacmartins changed the title [HOLD] feat: Enable Insights and comparisons on desktop web [HOLD product approval] feat: Enable Insights and comparisons on desktop web Oct 21, 2026
@luacmartins luacmartins changed the title [HOLD product approval] feat: Enable Insights and comparisons on desktop web feat: Enable Insights and comparisons on desktop web Oct 21, 2026
@luacmartins
luacmartins merged commit 6b318fc into main Oct 21, 2026
55 of 56 checks passed
@luacmartins
luacmartins deleted the cmartins-insights-web-first branch October 21, 2026 17:20
@github-actions

Copy link
Copy Markdown
Contributor

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

OSBotify pushed a commit that referenced this pull request Oct 21, 2026
feat: Enable Insights and comparisons on desktop web
(cherry picked from commit 6b318fc)

(cherry-picked to staging by luacmartins)
@OSBotify OSBotify added the CP Staging marks PRs that have been CP'd to staging label Oct 21, 2026
@OSBotify

Copy link
Copy Markdown
Contributor

✋ 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

Copy link
Copy Markdown
Contributor

🚀 Cherry-picked to staging by https://github.com/luacmartins in version: 9.5.15-3 🚀

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

@MelvinBot

MelvinBot commented Oct 21, 2026 •

Copy link
Copy Markdown
Contributor

Help site update needed. I opened a draft docs PR: Docs updates for E/A#104591 Point web Insights steps to new Insights tab

This PR gives every desktop web user the new Insights tab. It also removes the Insights section from Spend on web. That made these web steps wrong:

  • How to Use Insights in Expensify: "Click Spend in the navigation tabs … Scroll to Insights."
  • The Top spenders, Top merchants and Top categories articles: "select Spend, then click Top … under the Insights section."
  • Expensify Home Overview: View "takes you to that insight on the Spend page." On web, it now opens the Insights page.

Each fix is a one-sentence edit for web. Mobile steps are unchanged.

I didn't change the Violations by submitter article. On web it's no longer under Spend, and it isn't on the new Insights page either. I couldn't confirm the new web path, so please check that article.

@luacmartins, please review the linked help site PR and confirm it reflects the current behavior. Then mark the linked help site PR Ready for review


view run · no recording available

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/grgia in version: 9.5.15-3 🚀

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

Bundle Size Analysis (Sentry):

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Cherry-picked to staging by https://github.com/luacmartins in version: 9.5.16-0 🚀

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

@MelvinBot

Copy link
Copy Markdown
Contributor

A help site update is needed, and the draft docs PR already exists: [No QA] Docs updates for E/A#104591 Point web Insights steps to new Insights tab. It's still open, labeled HelpDot, and assigned to luacmartins, so I didn't open a duplicate.

This PR's diff hasn't changed since I opened it. On desktop web, Insights now has its own Insights tab and is no longer under Spend. The docs PR updates the web steps that still said to select Spend and then Insights.

One open item: I didn't edit the Violations by submitter article. On web it's no longer under Spend, and I couldn't verify its new location.

@luacmartins, please review the linked help site PR and confirm it reflects the current behavior. Then mark the linked help site PR Ready for review


view run

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Cherry-picked to staging by https://github.com/luacmartins in version: 9.5.18-0 🚀

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

@MelvinBot

MelvinBot commented Oct 22, 2026 •

Copy link
Copy Markdown
Contributor

A help site update is needed. I opened a draft PR: Docs updates for E/A#104591 Add Compare filter to How to Use Insights.

This PR turns on the insightsCompare beta for all desktop web users. That adds a Compare filter (Previous period / Average) to Insights. It makes this sentence in How to Use Insights wrong:

You can adjust the data shown across Insights using three shared filters:

The docs PR changes "three" to "these" and adds one Compare bullet marked web-only.

Why nothing else changes
  • The Insights tab itself is already documented as web-only in Navigating New Expensify and How to Use Insights. That already matches this PR.
  • Mobile web and native still need the beta, so the mobile instructions stay as they are.
  • I confirmed the Compare label and options in the live web UI.

@luacmartins, please review the linked help site PR and confirm it reflects the current behavior. Then mark the linked help site PR Ready for review


view run · view recording

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/grgia in version: 9.5.18-1 🚀

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

Bundle Size Analysis (Sentry):

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

Labels

CP Staging marks PRs that have been CP'd to staging

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants