[HOLD for payment 2024-08-14] [$250] Feature Request: When uploading, automatically reduce the size of receipt image if greater than 24mb

[m-natarajan]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @AndrewGable
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1718830152208309

Problem:

Unable to upload an image taken from the camera because it’s larger than 24MB

Solution:

Option to reduce the size on device before uploading

When uploading, automatically reduce the size of receipt image if greater than 24mb
This would mean there would be no change in the UI. The user likely wouldn't even know we did it—but their receipt image would be uploaded smoothly with no issues.

Note

I think this would only apply to receipt image uploads—NOT images uploaded as attachments in chats

Context/Examples/Screenshots/Notes:

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01b098d2eb27081851
• Upwork Job ID: 1805353003843890323
• Last Price Increase: 2024-07-15
• Automatic offers:
• shubham1206agra | Reviewer | 103127270
• nkdengineer | Contributor | 103127271

Issue Owner

Current Issue Owner: @OfstadC

[melvin-bot]

Triggered auto assignment to @OfstadC (NewFeature), see https://stackoverflowteams.com/c/expensify/questions/14418#:~:text=BugZero%20process%20steps%20for%20feature%20requests for more details. Please add this Feature request to a GH project, as outlined in the SO.

[melvin-bot]

⚠️ It looks like this issue is labelled as a New Feature but not tied to any GitHub Project. Keep in mind that all new features should be tied to GitHub Projects in order to properly track external CAP software time ⚠️

[melvin-bot]

Triggered auto assignment to Design team member for new feature review - @dannymcclain (NewFeature)

[dannymcclain]

Is this a suggestion to implement a feature where our app reduces the file size of a local image before uploading? 🤔

Either way, I don't think we should do this. File size limits are SUPER common amongst all the apps I use daily, and I've never once seen any of them try to reduce a file's size for me (also, 24mb is a pretty generous size limit). I think we should leave this responsibility on the user personally. cc @Expensify/design for thoughts.

[AndrewGable]

Just for reference- This is step backwards from what OldApp does. I can upload a picture from my camera no problem on OldApp, I have to resize it myself on NewDot.

I thought as a user this is a UX oddity.

[dannymcclain]

@AndrewGable are the normal photos your phone takes more than 24mb? I only ask because that seems reaaaaally big. Most of the photos on my phone (that I've taken) are around 1–3mb.

[AndrewGable]

Yes, new iPhones take really big pictures 😄 Looks like this receipt was ~30MB

[shawnborton]

How does OldDot handle this? Does it automatically resize the photo?

[AndrewGable]

Yes, it will allow the user to upload this receipt and OldApp will resize it for the user to allow upload.

[dannymcclain]

Yes, new iPhones take really big pictures 😄 Looks like this receipt was ~30MB

Oh I see, it's because you're shooting in Raw. But anyhoo! That's neither here nor there I suppose.

How does OldDot handle this? Does it automatically resize the photo?

Yes, it will allow the user to upload this receipt and OldApp will resize it for the user to allow upload.

Thinking about it more, Figma does do something similar if you try to drop in a super mega image: it resizes it in the background, adds the resized image, and gives you a little message that tells you Figma resized the image.

I think I'd be open to an approach like that where we just do it behind the scenes automatically (and maybe provide some indication that we've done it?) but I'd like to avoid this becoming like a whole user-flow centered around resizing an image before upload. That's what I though was originally being proposed, which is why I was not into it at first.