Skip to content

[Due for payment 2025-10-23] [Due for payment 2025-10-22] [CFI] Add primary receipt scan option on mobile and web #72030

@danielrvidal

Description

@danielrvidal

Proposal: Add primary receipt scan option on mobile and web

Background: Taking a photo of a receipt and allowing us to do the rest has been the most well known pain point we solve for a long time. We’ve always strived to be the most simple way for employees to submit their expenses. Enter New Expensify and we do so much more now.

  • When building New Expensify, we built the platform to try and be platform agnostic as much as possible. This led to decisions in us having one Global create button to rule them all.
  • Early on we got feedback that we made our flagship receipt capture flow (scanning receipts from mobile) harder to do.
  • We tried to shore this up with the quick action button, but that largely has not been that successful at getting people to use. And as we put more #migrate users in the platform, we’re fighting a lot of inertia of a product they love and flows they know well.

Problem: When users with New Expensify want to scan a receipt on the go, if they use Global Create, then they must tap four times instead of three, causing them like Classic more than New Expensify.

Solution: On mobile, update the bottom nav to have a deemphasized Create button and add a primary receipt button for fast receipt scanning. Here are the changes.

  • Mobile - Introduce a primary Camera button that use the default workspace and skips the confirmation screen if coding isn’t required as we do in the QAB flow and Classic.
  • Mobile - Update the Create button to no longer be primary (green) and be more aligned with other formatting of the bottom nav.
  • Web - Introduce a primary Receipt button which opens the receipt scanning option.
  • Web - Update the Create button to be a + and not primary (green). It would open the normal Global create options.

Here is the mock the @Expensify/design helped us align on:
Image
Internal design thread
Original internal issue

Issue OwnerCurrent Issue Owner: @ZhenjaHorbach

Sub-issues

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionDailyKSv2InternalRequires API changes or must be handled by Expensify staffNewFeatureSomething to build that is a new item.PlanningChanges still in the thought process

Type

No type

Projects

Status

CRITICAL

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions