[Home] Quick creation actions by WojtekBoman · Pull Request #85427 · Expensify/App

WojtekBoman · 2026-03-16T15:55:11Z

Explanation of Change

Added new QuickActionsBar component to the Home page with quick creation buttons: Expense, Report, Distance, and Book travel
Added new SVG icons: car-plus.svg and document-plus.svg, and registered them in Expensicons and the lazy-loaded expensify-icons chunk
Integrated the QuickActionsBar into HomePage, rendering it only on desktop/wide layouts (!shouldUseNarrowLayout)
Book travel button is conditionally visible — only shown when the user is a member of at least one workspace with travel enabled
Book travel handler checks travel provisioning status: opens Spotnana directly when ready, otherwise navigates to the Travel My Trips onboarding page

Fixed Issues

$ #85084
PROPOSAL:

Tests

Verify that no errors appear in the JS console

1. QuickActionsBar visibility (desktop only)

Open the app in a wide/desktop browser layout
Navigate to the Home page
Verify the QuickActionsBar is visible at the top of the page content with the Expense, Report, and Distance buttons
Resize the browser to a narrow/mobile layout
Verify the QuickActionsBar is not visible

2. Expense button

Click the "Expense" button
Verify it starts the money request creation flow
Verify the button displays the receipt-plus icon and "Expense" label

3. Report button

Click the "Report" button
Verify it creates a new report (or navigates to workspace selection / upgrade path as appropriate for the account)
Verify the button displays the document-plus icon and "Report" label

4. Distance button

Click the "Distance" button
Verify it starts the distance request creation flow
Verify the button displays the car-plus icon and "Distance" label

5. Book Travel button visibility

Log in with an account that is a member of at least one workspace with travel enabled
Navigate to the Home page
Verify the "Book travel" button is visible alongside the other quick action buttons, displaying the luggage-with-lines icon and "Book travel" label
Log in with an account that has no workspaces with travel enabled
Navigate to the Home page
Verify the "Book travel" button is not visible — only Expense, Report, and Distance should appear

6. Book Travel button action

Using an account with a fully provisioned travel workspace (terms accepted, Spotnana configured), click "Book travel"
Verify it opens the Spotnana travel link directly
Using an account where travel is enabled but onboarding is not completed (terms not accepted or policy not provisioned), click "Book travel"
Verify it navigates to the Travel My Trips page (/travel) for the onboarding flow

Offline tests

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

WojtekBoman · 2026-03-16T16:29:12Z

@Expensify/design Should we add padding-top to add some space between the quick actions button and loading bar?

codecov · 2026-03-16T16:32:37Z

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 Δ
...rc/components/Icon/chunks/expensify-icons.chunk.ts	`0.00% <ø> (ø)`
src/pages/home/HomePage.tsx	`100.00% <100.00%> (ø)`
...s/inbox/sidebar/FloatingActionButtonAndPopover.tsx	`51.28% <100.00%> (-0.18%)`	⬇️
src/styles/index.ts	`47.42% <ø> (ø)`
...nents/Navigation/QuickCreationActionsBar/index.tsx	`0.00% <0.00%> (ø)`
... and 164 files with indirect coverage changes

dannymcclain · 2026-03-16T16:33:09Z

Should we add padding-top to add some space between the quick actions button and loading bar?

I'm honestly tempted to say no so that we don't muck up the spacing when the page is "at rest". Curious for the other designers' takes though.

shawnborton · 2026-03-16T16:37:17Z

Hmm that's a fair point... I think I'd be curious to see like 4px of extra space there to see if that helps, as I think it doesn't look great when the green line runs over the buttons like that.

melvin-bot · 2026-03-16T16:37:31Z

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

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: b0837916f5

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

chatgpt-codex-connector · 2026-03-16T16:50:57Z

src/components/Navigation/QuickCreationActionsBar/index.tsx

+
+    const shouldRedirectToExpensifyClassic = useMemo(() => areAllGroupPoliciesExpenseChatDisabled((allPolicies as OnyxCollection<OnyxTypes.Policy>) ?? {}), [allPolicies]);
+
+    const shouldShowBookTravel = useMemo(() => Object.values(allPolicies ?? {}).some((policy) => !!policy?.isTravelEnabled), [allPolicies]);


Use a travel-enabled policy for Book travel action

The button visibility is based on any policy having isTravelEnabled, but the click handler always uses activePolicy?.id; when a user has a travel-enabled workspace but their active policy is personal/non-travel, the CTA is shown yet routes to My Trips with the wrong policy and booking is blocked (BookTravelButton rejects non-paid/default workspaces). This creates a user-facing dead end for a common account state (travel enabled somewhere, different active policy).

Useful? React with 👍 / 👎.

ZhenjaHorbach · 2026-03-16T16:56:58Z

src/components/Navigation/QuickCreationActionsBar/index.tsx

+    );
+}
+
+QuickCreationActionsBar.displayName = 'QuickCreationActionsBar';


We don't need displayName

ZhenjaHorbach · 2026-03-16T16:57:47Z

src/components/Navigation/QuickCreationActionsBar/index.tsx

+
+    return (
+        <>
+            {CreateReportConfirmationModal}


Can we use <CreateReportConfirmationModal/> ? 😅

I believe it would require to refactor a bit useCreateEmptyReportConfirmation, we get from this hook React.ReactNode instead of the component function, so that's why it's passed this way.
This notation can also be found in other files

github-actions · 2026-03-16T17:13:06Z

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

JmillsExpensify

Looks solid! I tested on web and mobile.

grgia · 2026-03-16T18:36:51Z

src/components/Navigation/QuickCreationActionsBar/index.tsx

+                if (
+                    !workspaceIDForReportCreation ||
+                    (shouldRestrictUserBillableActions(workspaceIDForReportCreation, undefined, undefined, ownerBillingGraceEndPeriod) && groupPoliciesWithChatEnabled.length > 1)
+                ) {
+                    Navigation.navigate(ROUTES.NEW_REPORT_WORKSPACE_SELECTION.getRoute());
+                    return;
+                }
+
+                if (!shouldRestrictUserBillableActions(workspaceIDForReportCreation, undefined, undefined, ownerBillingGraceEndPeriod)) {
+                    if (shouldShowEmptyReportConfirmationForDefaultChatEnabledPolicy) {
+                        openCreateReportConfirmation();
+                    } else {
+                        handleCreateWorkspaceReport(false);
+                    }
+                    return;
+                }


If there's a possibility this could be a dead button for a case (ie click and do nothing) should we hide it or show a disabled UI?

This shouldn't happen, handleCreateWorkspaceReport function calls navigate and openCreateReportConfirmation shows a modal window

dannymcclain · 2026-03-16T19:19:46Z

Hmm that's a fair point... I think I'd be curious to see like 4px of extra space there to see if that helps, as I think it doesn't look great when the green line runs over the buttons like that.

After using the ad hoc build, I'm also curious to see like 4px of space. I agree the line running over the buttons doesn't feel great. Otherwise testing really well for me!

joekaufmanexpensify · 2026-03-16T19:59:11Z

Removing my review as Jason already approved for product

… policy

WojtekBoman · 2026-03-17T07:04:45Z

Comments resolved!

@Expensify/design I added 4px paddingTop, this is how it looks:

ZhenjaHorbach · 2026-03-17T08:50:52Z

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 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

2026-03-17.10.01.32.mov

2026-03-17.10.04.24.mov

src/components/Navigation/QuickCreationActionsBar/index.tsx

ZhenjaHorbach · 2026-03-17T09:10:32Z

But overall changes look good!

github-actions · 2026-03-17T14:25:28Z

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

github-actions · 2026-03-17T14:30:25Z

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

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-c97d0c4-9897949-b02c639a30c2720b7ee00acaa38a1d7e6c22c0ff/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-c97d0c4-9897949-603c258d5b36abde9f5919fbb06309ee3f5d067a/index.html

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

👀 View the workflow run that generated this build 👀

OSBotify · 2026-03-17T14:32:31Z

✋ 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 · 2026-03-18T13:30:49Z

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

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

OSBotify · 2026-03-18T14:06:49Z

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

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

IuliiaHerets · 2026-03-19T06:47:30Z

Hi @WojtekBoman. Could this PR be implemented in the native apps?

сс @grgia

WojtekBoman · 2026-03-19T08:33:10Z

@IuliiaHerets
As far as I know, it's mainly desktop change,
it's the info from the issue description:

We're seeing that users still struggle find and locate our "global" create option on desktop. As a result, we've begun adding "local" create options in the main pages of the app, such as Reports. Home is the starting point, and expense/report creation is an especially important in giving sign-ups a reason to come back.

tl;dr we're adding quick create actions to Home (desktop only)

JmillsExpensify · 2026-03-19T09:43:03Z

Yes, not in scope for native apps. This is a desktop-only feature.

IuliiaHerets · 2026-03-19T11:37:33Z

@WojtekBoman and @joekaufmanexpensify Thanks

OSBotify · 2026-03-23T09:28:39Z

🚀 Deployed to production by https://github.com/cristipaval in version: 9.3.41-4 🚀

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

melvin-bot bot assigned WojtekBoman Mar 16, 2026

WojtekBoman force-pushed the home-page/quick-actions-bar branch 2 times, most recently from b32a55c to 9fb6971 Compare March 16, 2026 16:23

Add QuickActionsBar

b083791

WojtekBoman force-pushed the home-page/quick-actions-bar branch from 9fb6971 to b083791 Compare March 16, 2026 16:35

WojtekBoman marked this pull request as ready for review March 16, 2026 16:37

WojtekBoman requested review from a team as code owners March 16, 2026 16:37

melvin-bot bot requested a review from ZhenjaHorbach March 16, 2026 16:37

melvin-bot bot requested review from joekaufmanexpensify and removed request for a team March 16, 2026 16:37

chatgpt-codex-connector bot reviewed Mar 16, 2026

View reviewed changes

ZhenjaHorbach reviewed Mar 16, 2026

View reviewed changes

This comment has been minimized.

Sign in to view

JmillsExpensify previously approved these changes Mar 16, 2026

View reviewed changes

grgia reviewed Mar 16, 2026

View reviewed changes

joekaufmanexpensify removed their request for review March 16, 2026 19:59

Fix Book travel button to use travel-enabled policy instead of active…

2f5367b

… policy

WojtekBoman dismissed JmillsExpensify’s stale review via 2f5367b March 17, 2026 06:46

ZhenjaHorbach reviewed Mar 17, 2026

View reviewed changes

src/components/Navigation/QuickCreationActionsBar/index.tsx Outdated Show resolved Hide resolved

ZhenjaHorbach reviewed Mar 17, 2026

View reviewed changes

src/components/Navigation/QuickCreationActionsBar/index.tsx Outdated Show resolved Hide resolved

Add primaryLoginSelector

02bcacd

ZhenjaHorbach approved these changes Mar 17, 2026

View reviewed changes

melvin-bot bot requested a review from grgia March 17, 2026 11:51

grgia approved these changes Mar 17, 2026

View reviewed changes

grgia merged commit c97d0c4 into Expensify:main Mar 17, 2026
35 checks passed

aimane-chnaif mentioned this pull request Mar 17, 2026

FAB popover decomposition #83299

Merged

53 tasks

OSBotify mentioned this pull request Mar 18, 2026

Deploy Checklist: New Expensify 2026-03-18 #85646

Closed

100 tasks

This was referenced Mar 18, 2026

Reports - Delete option is not available for track expenses when created via "Home" #85697

Open

Home - Infinite loading on Reports>Expenses pg when creating expense from home QAB/FAB for first time #85698

Open

nlemma mentioned this pull request Mar 19, 2026

Travel - Not here page opens after member clicks on Travel button from Quick menu #85803

Open

7 tasks

melvin-bot bot mentioned this pull request Mar 23, 2026

[Due for payment 2026-03-30] [Home] Quick creation actions #85084

Open


		const shouldRedirectToExpensifyClassic = useMemo(() => areAllGroupPoliciesExpenseChatDisabled((allPolicies as OnyxCollection<OnyxTypes.Policy>) ?? {}), [allPolicies]);

		const shouldShowBookTravel = useMemo(() => Object.values(allPolicies ?? {}).some((policy) => !!policy?.isTravelEnabled), [allPolicies]);

Conversation

WojtekBoman commented Mar 16, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Explanation of Change

Fixed Issues

Tests

1. QuickActionsBar visibility (desktop only)

2. Expense button

3. Report button

4. Distance button

5. Book Travel button visibility

6. Book Travel button action

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

WojtekBoman commented Mar 16, 2026

Uh oh!

codecov bot commented Mar 16, 2026 • edited by github-actions bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

dannymcclain commented Mar 16, 2026

Uh oh!

shawnborton commented Mar 16, 2026

Uh oh!

melvin-bot bot commented Mar 16, 2026

Uh oh!

chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

chatgpt-codex-connector bot Mar 16, 2026

Choose a reason for hiding this comment

Uh oh!

ZhenjaHorbach Mar 16, 2026

Choose a reason for hiding this comment

Uh oh!

ZhenjaHorbach Mar 16, 2026

Choose a reason for hiding this comment

Uh oh!

WojtekBoman Mar 17, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot commented Mar 16, 2026

Uh oh!

This comment has been minimized.

JmillsExpensify left a comment

Choose a reason for hiding this comment

Uh oh!

grgia Mar 16, 2026

Choose a reason for hiding this comment

Uh oh!

WojtekBoman Mar 17, 2026

Choose a reason for hiding this comment

Uh oh!

dannymcclain commented Mar 16, 2026

Uh oh!

joekaufmanexpensify commented Mar 16, 2026

Uh oh!

WojtekBoman commented Mar 17, 2026

Uh oh!

ZhenjaHorbach commented Mar 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

Uh oh!

Uh oh!

ZhenjaHorbach commented Mar 17, 2026

Uh oh!

Uh oh!

github-actions bot commented Mar 17, 2026

Uh oh!

github-actions bot commented Mar 17, 2026

Uh oh!

OSBotify commented Mar 17, 2026

Uh oh!

OSBotify commented Mar 18, 2026

WojtekBoman commented Mar 16, 2026 •

edited

Loading

codecov bot commented Mar 16, 2026 •

edited by github-actions bot

Loading

ZhenjaHorbach commented Mar 17, 2026 •

edited

Loading

IuliiaHerets commented Mar 19, 2026 •

edited

Loading