[No QA] Update help site pages for Add primary receipt scan option on mobile by heyjennahay · Pull Request #75671 · Expensify/App

heyjennahay · 2025-11-20T14:09:30Z

Explanation of Change

Product change GH #72030

Updated instructions to refer to the new add receipt flow on mobile and desktop

Specifically:

Green camera / add receipt button to immediately open scanning/file import
Create button changed to grey

@jamesdeanexpensify can you please confirm you're happy with the new button names I've used?

Fixed Issues

$ #72030

Tests

Verify that no errors appear in the JS console

Offline tests

QA Steps

No QA

…bile Product change GH #72030 Updated instructions to refer to the new add receipt flow on mobile and desktop

github-actions · 2025-11-20T14:09:42Z

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

OSBotify · 2025-11-20T14:13:42Z

A preview of your ExpensifyHelp changes have been deployed to https://5f8881ad.helpdot.pages.dev ⚡️

Updated articles:

melvin-bot · 2025-11-20T15:08:42Z

melvin-bot · 2025-11-20T15:08:45Z

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

github-actions · 2025-11-20T15:10:22Z

HelpDot Documentation Review

Overall Assessment

This PR updates three documentation files to reflect the new primary receipt scan option introduced on mobile and desktop platforms. The changes streamline the expense creation flow by emphasizing the new green camera button on mobile and green add receipt button on desktop, replacing the previous multi-step process through the generic "+" button. The documentation updates are clear, concise, and improve the user experience by simplifying instructions.

Scores Summary

Readability: 9/10 - Instructions are clear and well-structured with logical flow. The platform-specific guidance (mobile vs. desktop) makes it easy for users to find relevant steps. Minor improvements could be made to ensure consistency in button descriptions.
AI Readiness: 8/10 - Good use of descriptive headings and structured content. YAML metadata is properly formatted. Some sections could benefit from more explicit context about what the "green camera button" and "green add receipt button" refer to for AI comprehension.
Style Compliance: 8/10 - Generally follows Expensify voice and tone. Uses proper terminology and formatting. Some inconsistencies in button naming conventions (e.g., "Choose File" vs "Choose files") should be standardized.

Key Findings

Strengths:

Clear platform differentiation (mobile vs. desktop) improves usability
Simplified step-by-step instructions reduce cognitive load
Consistent removal of outdated "Create expense" menu selection process
Added helpful cross-references between related documentation pages
Proper use of emoji icons (💡) for notes enhances scannability
Maintained existing helpful alternative methods (email, SMS)

Areas for Improvement:

Button naming consistency: Mix of "Choose File" vs "Choose files" (Track-Personal-Expenses.md uses "Choose files" while Track-Expenses.md uses "Choose File")
Color consistency: Distance expense section changed from "green +" to "grey +" button - ensure this accurately reflects the UI
Step numbering: Option 4 in Create-an-Expense.md has a formatting issue (missing step 4, jumps from 3 to 5)
Context clarity: The term "green camera button" and "green add receipt button" could be more descriptive for first-time users who may not immediately recognize these UI elements

Recommendations

Priority Actions:

Standardize "Choose File" vs "Choose files" across all three documents
Fix the step numbering in Create-an-Expense.md, Option 4 (currently missing step 4)
Verify that the grey "+" button reference is correct for distance tracking and chat creation

Suggestions for Enhancement:

Consider adding a brief clarification when first mentioning new buttons (e.g., "tap the green camera button (located at the bottom of the screen)")
Ensure the "grey +" button color is accurate or if it should remain "green +" for consistency
Minor formatting: "push notification" could be formatted as "push notifications" for consistency with other plural forms in the same sentence

Files Reviewed

Track-Personal-Expenses.md - Successfully updated with new flow, good addition of cross-reference link
Create-an-Expense.md - Comprehensive updates across all expense creation options, minor step numbering issue to fix
Track-Expenses.md - Clear simplification of instructions, button naming needs minor standardization

Overall Score: 8.3/10 - Solid documentation update that successfully communicates the product changes. With minor fixes to consistency issues, this will be excellent documentation.

🤖 Generated with Claude Code

github-actions · 2025-11-20T15:10:56Z

+1. On desktop, go to the Reports page.
+2. Drag up to 30 PDF or image files (under 10MB each) into Expensify.
 3. Follow the prompts to assign workspaces, recipients, and coding.
+4. Click **Create expenses**. 


Readability violation: Step 4 says "Click Create expenses" but there's no clear indication of when/where this button appears. Add context like "Once you've assigned workspaces and coding, click Create expenses."

heyjennahay · 2025-11-20T15:33:53Z

@kadiealexander FYI the previews created here #75671 (comment) don't seem to have the updates, these took me a while and the PR was in draft for a while so it maybe was created before I finalised the PR. Not sure if they update or not 😅

heyjennahay · 2025-11-20T15:54:10Z

Actually ignore that last comment, I just checked the links again now and they have updated 🥳

jamesdeanexpensify · 2025-11-24T21:00:07Z

Reviewed via Slack and left a comment!

kadiealexander · 2025-11-26T22:22:36Z

Left a quick comment about the layout of the steps, everything else is looking solid!

heyjennahay · 2025-12-08T17:33:00Z

Slack thread https://expensify.slack.com/archives/C07NMDKEFMH/p1765215162371749?thread_ts=1764013958.554589&cid=C07NMDKEFMH

kadiealexander

LGTM, thanks for incorporating that feedback!

kadiealexander · 2025-12-08T21:31:08Z

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
- MacOS: Desktop
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 there are no new alerts related to the canBeMissing param for useOnyx
I verified proper code patterns were followed (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 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)
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
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a /** comment above it */
- The file is named correctly
- 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
- For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
- Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
- All JSX used for rendering exists in the render method
- 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 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 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.
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

Android: mWeb Chrome

iOS: HybridApp

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

OSBotify · 2025-12-09T15:29:03Z

🚀 Deployed to staging by https://github.com/kadiealexander in version: 9.2.74-0 🚀

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

OSBotify · 2025-12-10T21:38:12Z

🚀 Deployed to production by https://github.com/yuwenmemon in version: 9.2.74-12 🚀

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

OSBotify · 2025-12-10T21:54:27Z

🚀 Deployed to production by https://github.com/yuwenmemon in version: 9.2.74-12 🚀

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

OSBotify · 2025-12-10T22:58:51Z

🚀 Deployed to production by https://github.com/yuwenmemon in version: 9.2.74-12 🚀

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

Update Create-an-Expense.md for Add primary receipt scan option on mo…

f73be9d

…bile Product change GH #72030 Updated instructions to refer to the new add receipt flow on mobile and desktop

heyjennahay self-assigned this Nov 20, 2025

Update Create-an-Expense.md

5eafc3b

heyjennahay added 8 commits November 20, 2025 15:22

Update Create-an-Expense.md

94ca50b

Update Track-Expenses.md

afcf778

Update Track-Expenses.md

b156ff2

Update Create-an-Expense.md

3708598

Update Create-an-Expense.md

6aa7c73

Update Create-an-Expense.md

78a73a6

Update Track-Expenses.md

9b44fc1

Update Track-Personal-Expenses.md

c07e342

heyjennahay marked this pull request as ready for review November 20, 2025 15:08

heyjennahay requested a review from a team as a code owner November 20, 2025 15:08

melvin-bot Bot requested review from kadiealexander and removed request for a team November 20, 2025 15:08