Skip to content

Add primary receipt scan option on mobile and web#72236

Merged
mountiny merged 17 commits into
Expensify:mainfrom
callstack-internal:JKobrynski/72030-add-primary-receipt-scan-option
Oct 14, 2025
Merged

Add primary receipt scan option on mobile and web#72236
mountiny merged 17 commits into
Expensify:mainfrom
callstack-internal:JKobrynski/72030-add-primary-receipt-scan-option

Conversation

@JKobrynski

@JKobrynski JKobrynski commented Oct 9, 2025

Copy link
Copy Markdown
Contributor

Explanation of Change

Fixed Issues

$ #72030
PROPOSAL: N/A

Tests

  1. Log into the app on web/desktop
  2. Look at the bottom left of the window and make sure you can see two buttons
  3. The one with "+" should work just like it used to, it should also be gray now instead of green
  4. Above it you should see a green button with receipt icon that upon clicking triggers a scan receipt workflow
  5. Log into the app on mobile
  6. Look at the bottom of the window, in the middle of the bottom navigation bar you should see a new gray button that says "create", it should work just like it used to, is should be gray instead of green
  7. Right above the bottom navigation bar on the right you should see a new green button with a camera icon, it allow for a quick scanning workflow, using default workspace (if available) and skipping the confirmation step (if coding is not required)
  8. The new floating button (with the camera icon) should always be visible if the bottom nav is visible
  • Verify that no errors appear in the JS console

Offline tests

N/A

QA Steps

Same as Tests section above.

  • 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
    • MacOS: Desktop
  • 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 there are no new alerts related to the canBeMissing param for useOnyx
  • 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 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 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)
  • 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
  • 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 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 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.
  • 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-compressed.webm
Android: mWeb Chrome
chrome-compressed.webm
iOS: Native
ios-compressed.mp4
iOS: mWeb Safari
safari-compressed.mp4
MacOS: Chrome / Safari
web-compressed.mov
MacOS: Desktop
desktop-compressed.mov

Comment thread src/components/FloatingReceiptButton.tsx
Comment thread src/components/FloatingCameraButton.tsx Outdated
@JKobrynski JKobrynski marked this pull request as ready for review October 10, 2025 13:19
@JKobrynski JKobrynski requested review from a team as code owners October 10, 2025 13:19
@melvin-bot melvin-bot Bot requested review from ZhenjaHorbach and mountiny and removed request for a team October 10, 2025 13:19
@melvin-bot

melvin-bot Bot commented Oct 10, 2025

Copy link
Copy Markdown

@ZhenjaHorbach @mountiny One of you needs to 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]

Comment thread src/components/FloatingCameraButton.tsx Outdated
@JKobrynski JKobrynski changed the title [WIP] Add primary receipt scan option on mobile and web Add primary receipt scan option on mobile and web Oct 10, 2025
@github-actions

Copy link
Copy Markdown
Contributor

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

Comment thread src/components/FloatingCameraButton.tsx Outdated
const [activePolicyID] = useOnyx(ONYXKEYS.NVP_ACTIVE_POLICY_ID, {canBeMissing: true});
const [activePolicy] = useOnyx(`${ONYXKEYS.COLLECTION.POLICY}${activePolicyID}`, {canBeMissing: true});
const [session] = useOnyx(ONYXKEYS.SESSION, {canBeMissing: false, selector: sessionSelector});
const [allReports] = useOnyx(ONYXKEYS.COLLECTION.REPORT, {canBeMissing: true});

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.

We need the allReports to load policyChats - I think it might be better to already have a selector that loads all the policyExpenseChats you own and then getWorkspaceChats would only have those in the useMemo

Or even better, can we put the full policyChatForActivePolicy logic into the useOnyx selector?

We should try as hard as possible not to useOnyx on a full collection

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

On it

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Done

@codecov

codecov Bot commented Oct 10, 2025

Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 70.37037% with 16 lines in your changes missing coverage. Please review.

Files with missing lines Patch % Lines
src/components/FloatingReceiptButton.tsx 11.11% 8 Missing ⚠️
src/components/Search/SearchPageFooter.tsx 0.00% 4 Missing ⚠️
src/components/FloatingActionButton.tsx 94.11% 1 Missing ⚠️
src/components/FloatingCameraButton.tsx 94.11% 1 Missing ⚠️
...c/components/Navigation/NavigationTabBar/index.tsx 0.00% 1 Missing ⚠️
...es/home/sidebar/FloatingActionButtonAndPopover.tsx 66.66% 1 Missing ⚠️
Files with missing lines Coverage Δ
...ents/Navigation/TopLevelNavigationTabBar/index.tsx 93.75% <100.00%> (+0.89%) ⬆️
.../Search/SearchPageHeader/SearchTypeMenuPopover.tsx 0.00% <ø> (ø)
src/styles/index.ts 45.10% <100.00%> (-0.25%) ⬇️
src/components/FloatingActionButton.tsx 96.42% <94.11%> (-3.58%) ⬇️
src/components/FloatingCameraButton.tsx 94.11% <94.11%> (ø)
...c/components/Navigation/NavigationTabBar/index.tsx 59.74% <0.00%> (ø)
...es/home/sidebar/FloatingActionButtonAndPopover.tsx 51.46% <66.66%> (+0.19%) ⬆️
src/components/Search/SearchPageFooter.tsx 0.00% <0.00%> (ø)
src/components/FloatingReceiptButton.tsx 11.11% <11.11%> (ø)

... and 14 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@ZhenjaHorbach

ZhenjaHorbach commented Oct 10, 2025

Copy link
Copy Markdown
Contributor

Minor issue
But we have slightly different borders when selecting menu items using the keyboard
I suppose Create should have the same border as other menu items

2025-10-10.15.40.54.mov

@ZhenjaHorbach

Copy link
Copy Markdown
Contributor

Actually interesting
This is a bit of an edge case
But when we have a web desktop app with a small screen
We see the camera icon
And when we click on the icon
Restricted screen opens

Maybe we just need to hide this icon for small desktop screens?
Or is it okay?

CC: @mountiny

2025-10-10.15.46.35.mov

@mountiny

Copy link
Copy Markdown
Contributor

Maybe we just need to hide this icon for small desktop screens?
Or is it okay?

I assume we would only want the button on mobile (devices with camera, no?) @Expensify/design

@JKobrynski

Copy link
Copy Markdown
Contributor Author

@shawnborton I tried reproducing that misalignment on desktop caused by odd pixels and I couldn't. Are you using some specific setup/window size?

Screenshot 2025-10-14 at 15 07 23

@shawnborton

Copy link
Copy Markdown
Contributor

Are you zoomed in at all? I am just using Chrome web on a MacBook at 100% zoom.

@JKobrynski

Copy link
Copy Markdown
Contributor Author

Are you zoomed in at all? I am just using Chrome web on a MacBook at 100% zoom.

Oh you mentioned it's desktop so I was checking the desktop app. I just checked on web with 100% zoom and everything is fine too.

@github-actions

Copy link
Copy Markdown
Contributor

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

@github-actions

Copy link
Copy Markdown
Contributor

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

Android 🤖 iOS 🍎
https://ad-hoc-expensify-cash.s3.amazonaws.com/android/72236/index.html https://ad-hoc-expensify-cash.s3.amazonaws.com/ios/72236/index.html
Android iOS
Desktop 💻 Web 🕸️
https://ad-hoc-expensify-cash.s3.amazonaws.com/desktop/72236/NewExpensify.dmg https://72236.pr-testing.expensify.com
Desktop Web

👀 View the workflow run that generated this build 👀

@github-actions

Copy link
Copy Markdown
Contributor

Performance Rule Violations Found

I found several performance violations in the code that need to be addressed:

Rule PERF-4 violations: Objects and functions passed as props should be properly memoized to prevent unnecessary re-renders.

Rule PERF-6 violations: Hook dependencies should specify individual properties instead of entire objects to create more granular dependency tracking.

Please see the inline comments for specific fixes.

@github-actions

Copy link
Copy Markdown
Contributor

LGTM :feelsgood:. Thank you for your hard work!

@github-actions

Copy link
Copy Markdown
Contributor

HelpDot Documentation Review - Not Applicable

Assessment

This PR (#72236) does not contain HelpDot documentation changes. The PR is focused on adding a primary receipt scan option on mobile and web platforms and includes only code, assets, and localization files.

Changed Files Analysis

The 23 changed files consist of:

  • UI components (FloatingActionButton, FloatingCameraButton, etc.)
  • SVG assets (camera.svg, plus-circle.svg)
  • Language files for internationalization
  • TypeScript components and styling
  • Test files

Recommendation

No HelpDot documentation review is needed for this PR. If documentation updates are required for this new feature, they should be submitted as a separate PR to the docs/ directory following the HelpDot documentation standards.


This assessment was automatically generated by the HelpDot Documentation Review system.

@mountiny mountiny 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.

Some minor comments to address in the follow ups

import {Camera} from './Icon/Expensicons';
import {PressableWithoutFeedback} from './Pressable';

const sessionSelector = (session: OnyxEntry<OnyxTypes.Session>) => ({email: session?.email, accountID: session?.accountID});

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.

Does this not exist in the shared selectors? I would think it must exist

Comment on lines +39 to +45
selector: (reports) => {
if (isEmptyObject(activePolicy) || !activePolicy?.isPolicyExpenseChatEnabled) {
return undefined;
}
const policyChatsForActivePolicy = getWorkspaceChats(activePolicyID, [session?.accountID ?? CONST.DEFAULT_NUMBER_ID], reports);
return policyChatsForActivePolicy.at(0);
},

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.

The selectors should not be inline, can you refactor this to use stable reference to selector?

style={[
styles.navigationTabBarFABItem,
styles.ph0,
// Prevent text selection on touch devices (e.g. on long press)

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.

Suggested change
// Prevent text selection on touch devices (e.g. on long press)
// Prevent text selection on touch devices (e.g. on long press)

const shouldDisplayLHB = !shouldUseNarrowLayout;

const platform = getPlatform(true);
// We want to display the floating camera button on mobile devices (both web and native)

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.

Suggested change
// We want to display the floating camera button on mobile devices (both web and native)
// We want to display the floating camera button on mobile devices (both web and native)

@mountiny mountiny merged commit eb90f11 into Expensify:main Oct 14, 2025
27 checks passed
@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.

@jamesdeanexpensify

Copy link
Copy Markdown
Contributor

@dubielzyk-expensify do you need any follow-ups on this? Let me know. The comments took off after that, so I'm not sure where we landed.

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/mountiny in version: 9.2.31-0 🚀

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

@dubielzyk-expensify

Copy link
Copy Markdown
Contributor

@jamesdeanexpensify looks like it merged already. Let's see when it hits prod and we can change from there 👍

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/mountiny in version: 9.2.31-2 🚀

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

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.