You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Navigating from the Camera FAB to the "Create expense w/ Scan" page feels sluggish. The rendering of the Scan page itself is a bottleneck in the overall create-expense-via-scan flow.
Goal
Profile and optimize the rendering of the Scan page to reduce the transition time from tapping the Camera FAB to the scan page being fully interactive (camera initialized and ready).
Plan:
Add sentry tracking spans for the flow
Build sentry dashboard
Deep investigation into problematic areas and anywhere we can reduce rendering time and improve app performence on web and mobile platforms
But it does not tell us what the origin is e.g. did we get here from the Global Create? Or the Camera FAB? Not sure if that makes a huge difference in practice - but something that came to mind.
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.31-0 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.31-0 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
Activity
Julesssss commentedon Feb 25, 2026
Note from marc that the permissions check could possibly be cached. It was taking ~100ms on iOS dev.
Context: https://expensify.slack.com/archives/C03TBKRSB/p1772060029356039?thread_ts=1771887714.131779&cid=C03TBKRSB
marcaaron commentedon Feb 26, 2026
Might be helpful to know that we do have a metric for this one:
Query:
span.op:ManualOpenCreateExpense iou_request_type:scan (os.name:iOS OR os.name:Android )But it does not tell us what the origin is e.g. did we get here from the Global Create? Or the Camera FAB? Not sure if that makes a huge difference in practice - but something that came to mind.
Julesssss commentedon Feb 27, 2026
Created an issue here to add a tracking param for the source of the Create Expense flow.
@rinej may be helping with improving this 👋 🎉
134 remaining items
[-][HOLD][Metrics] Optimize "Scan" page rendering (Camera FAB → Create expense w/ Scan)[/-][+][Due for payment 2026-07-16] [HOLD][Metrics] Optimize "Scan" page rendering (Camera FAB → Create expense w/ Scan)[/+]melvin-bot commentedon Jul 9, 2026
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Jul 9, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.31-0 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2026-07-16. 🎊
For reference, here are some details about the assignees on this issue:
[-][Due for payment 2026-07-16] [HOLD][Metrics] Optimize "Scan" page rendering (Camera FAB → Create expense w/ Scan)[/-][+][HOLD][Metrics] Optimize "Scan" page rendering (Camera FAB → Create expense w/ Scan)[/+]cristipaval commentedon Jul 9, 2026
I've created this subissue for handling the payment for this PR
Julesssss commentedon Jul 13, 2026
@cristipaval can we close this? your payment issue seems like the only thing remaining here
cristipaval commentedon Jul 14, 2026
yes, let's close it Thanks!