Add polish to the start/stop GPS mileage experience

[JmillsExpensify]

Our initial focus for GPS mileage was Classic feature parity, though now that that's officially done, let's focus on polish and improve the overall employee experience. The end result will look like this.

Product and design details:

• If we don't have location permissions, we'll default to San Francisco, just like we do for map mileage.
• If we don't have location permissions and a user taps Start, we'll show the existing location permission errors.
• We'll update the map as a user moves.
• Stop always displays "Tracking distance" as long as we're actively tracking
• When a user taps Stop, we'll display total Distance, the Start address, and the Stop address.
• We'll also include the ability to edit (pencil icon) the trip, which opens the edit flow we built in Add stop address editing for GPS mileage #85802.
• Resume and Save work just like they do today.

Issue Owner

Current Issue Owner: @dukenv0307

[melvin-bot]

Current assignee @shawnborton is eligible for the NewFeature assigner, not assigning anyone new.

[GCyganek]

Resume and Save work just like they do today.

@shawnborton I'm curious, because we do not have Resume and Save buttons. Does Save mean what we currently have as Next? And do we want to add pause/resume functionality here to the GPS trip? Resume suggests that and we currently only let the user start and stop and here it replaces Discard button

[GCyganek]

This screen also has the GPS disclaimer we removed a month ago, I guess we don't want to restore it?

[shawnborton]

I guess we don't want to restore it?

Correct, that's just my bad from Figma. No need to restore it.

[shawnborton]

I'm curious, because we do not have Resume and Save buttons. Does Save mean what we currently have as Next? And do we want to add pause/resume functionality here to the GPS trip? Resume suggests that and we currently only let the user start and stop and here it replaces Discard button

Yes, that is exactly what I was thinking.

Does Save mean what we currently have as Next?

Yup, basically once you stop the trip, you have two choices: start it again to keep going, or save the expense.

And do we want to add pause/resume functionality here to the GPS trip?

Yeah that was my thinking. This way in case you accidentally stopped it or stopped it for a bit and then wanted to pick up later, you could.

Let me know if all of that is making sense.

[JmillsExpensify]

For what it's worth, I found myself wanting to pause/resume in my recent testing. A common example was a pitstop for gas and then going to a restaurant next door. There wasn't a need to keep tracking "extra kms" in that scenario.

[dubielzyk-expensify]

Just jumping in to say that I explored pause/resume in the initial mocks and would love to see it added here as well. A lot smoother for the user experience as a mistake doesn't cause complete deletion or creating the expense