Repository navigation
Description
DESIGN DOC ➡️
Slack Room: #migrate
Proposal
Background: We are nearing the finish of feature parity on New Expensify, the Start GPS functionality on Expensify Classic iOS/Android is one feature that is missing. GPS tracking for distance is a popular way to track exactly how far a user has driven to be reimbursed precisely. This is important for users who need even more precise measurements than an odometer or map created distance expense.
Problem: When users track distance expenses via GPS in Classic, if they are migrated to NewDot, then they must either manually calculate total distance (losing GPS proof) or abandon NewDot to stay in classic or switch to a competing application.
Solution: Introduce GPS mileage as a distance tracking method in NewDot on iOS/Android with feature parity to Classic. Users will be able to:
- Start a GPS distance expense
- After the user starts GPS tracking and closes the app, notify them that the GPS is running so they remember to stop it at their destination
- Stop the GPS when they arrive at their destination
- A GPS map will be included as the receipt image on the expense
For compatibility and parity, the GPS feature will start as a clone of Classic and we can add additional functionality later. 🏁
Tasks
- Post Proposal (full Problem/Solution statement) in
#expensify-open-source - Wait at least one full business day, and until the post has a majority (2/3) of positive reactions (👍)
- Paste Proposal in the space above with a link to the Slack thread
- Email
strategy@expensify.comand paste in the Proposal - Fill out the High-level overview of the problem, Timeline, and Terminology sections of the Design Doc
- Email
strategy@expensify.com(continue the same email chain as before) with the link to your Design Doc - Host a pre-design meeting (example) in
#expensify-open-sourceto discuss any necessary details in public before filling out the High-level of proposed solution section. - Fill out the High-level of proposed solution section
- Email
stategy@expensify.comagain with links to the doc and pre-design conversation in Slack - Add the
DesignDocReviewlabel to get the High-level of proposed solution section reviewed - Respond to any questions or concerns and bring up blockers in Slack to get a consensus if necessary
- Confirm that the doc has the minimum necessary number of reviews before proceeding
- Host another pre-design meeting in
#expensify-open-sourceto ask for engineering feedback on the technical solution. - Fill out the Detailed implementation of the solution and related sections.
- Re-add the
DesignDocReviewlabel to this issue - Respond to any questions or concerns and bring up blockers in Slack to get consensus if necessary
- Confirm that the doc has the minimum necessary number of reviews before proceeding
- Email
strategy@expensify.comone last time to let them know the Design Doc is moving into the implementation phase - Implement the changes
- Add regression tests so that QA can test your feature with every deploy (instructions)
- Send out a follow up email to
strategy@expensify.comonce everything has been implemented and do a Project Wrap-Up retrospective that provides:- Summary of what we accomplished with this project
- What went well?
- What could we have done better?
- What did we learn?
Metadata
Metadata
Labels
Type
Projects
- StatusShow more project fieldsDone
Activity
melvin-bot commentedon Oct 22, 2025
Triggered auto assignment to @NicMendonca (
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. Remember to draft any necessary HelpDot updates by following the instructions here.melvin-bot commentedon Oct 22, 2025
melvin-bot commentedon Oct 22, 2025
Triggered auto assignment to Design team member for new feature review - @dubielzyk-expensify (
NewFeature)AndrewGable commentedon Oct 22, 2025
Working with @GCyganek to get the high level design doc section filled out 📝
dubielzyk-expensify commentedon Oct 23, 2025
Happy to help out 👍 You got the mocks needed or want some help?
AndrewGable commentedon Oct 23, 2025
Mocks would be awesome!
dubielzyk-expensify commentedon Oct 27, 2025
Explorations started in this Figma. I'll let y'all leave feedback in Figma, but a few thoughts:
cc @Expensify/design @Expensify/product-pr
106 remaining items
melvin-bot commentedon Mar 6, 2026
This issue has not been updated in over 15 days. @AndrewGable, @GCyganek, @jnowakow, @dukenv0307, @dubielzyk-expensify eroding to Monthly issue.
P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!
GCyganek commentedon Mar 9, 2026
GPS live activity and android notification update are merged and deployed to staging
AndrewGable commentedon Mar 23, 2026
Sent out project wrap up ✅
Opened CapSW update ✅
We will have some lingering improvements and tweaks, but this project is done!
@dukenv0307 can you make a payment issue for all your reviews? Thanks!
dukenv0307 commentedon Mar 24, 2026
@AndrewGable I've just created the payment issue, please let me know if I need to do sth else