One would think this is the case. I agree it should be.
> That’s bizarre.
Unfortunately, it's not. It's normal operation.
The whole point of app is to gather your info from the phone and to send you tons of notifications.
And don't forget mandatory updates, when you open an app and cannot use it without updating to the latest crappy version.
Plenty could exist as a web app.
The obvious answer is because asynchronous workflows are brittle, and require intervention from the end user to correct if they break
Then most end users aren't going to care to fix it when it breaks, or be able to fix it when it breaks for a variety of reasons
Recall the driver can’t continue without an address.
There's some strong "Seeing Like a State" vibes here. I'm pretty sure these apps are intentionally designed as tools to force the users (here, drivers) into a specific flow, a flow that minimizes complexity for the vendor, reality be damned.
Another way to look at it: the job of the driver side of a delivery (or taxi) app isn't to be useful to the driver; the job is to be a remote control with which the business can control the driver like they were an automaton.
I don’t see how this benefits anyone.
This is one reason that package delivery drivers often will say that they've attempted delivery when they at best drove past the delivery point. Marking the delivery as attempted gets them off the hook for that delivery, and they can finish their shift that much faster.
Having a broken app that forces the driver to 100% complete every delivery before moving to the next one thus costs the company relatively little, but saves some complexity, missing proof of delivery, etc.
In any case, if the network is down, a spinner is a lie. It's pretending to be working on something when it's not. It should show an error at least.
When a customer shows up saying something went wrong with the delivery, the CSRs will need evidence and if the driver did their job then they can be exonerated.
The logistics are a bit more complex than a restaurant where customers are eating at tables in the same building.
I'm not entirely sure what your point is at all
If you drive away from the delivery before that photo is uploaded, then you risk not having the proof that you delivered the package successfully
That is actually worse for the driver than having to wait for the upload so they can retry immediately
Because "[driver] doesn't know where to go till it confirms the upload"
Nobody cares about quality anymore.
They require a mobile phone number now. If I give them one, they'll enforce SMS as a login path.
I live in an area with excellent cell service, except for a few miles around my house. I'm not going to try to log in, while buying something, then drive down the road and wait for the SMS.
Sheer stupid.
Suppose you're doing gig delivery. You're delivering to two customers in the same neighborhood on the same run. You drop the first order, take your photo of the drop, and the app spins. It's waiting for the photo to be delivered before it moves on. You can't get directions to the next customer until the app moves along. Why can't it just take the photo, take the text description, and hold that until service is better? Just give the driver the map, and upload the other stuff when you can.
I have similar issues with every app. It seems like every user interaction, every button press requires a round-trip to the server before the app moves to the next step. There's no reason for this. I wager that every app can keep its UI and the user's data locally, and send and receive teensy data updates.
But all "the best" software development employees (that they claim their hiring process hires) in these companies can't seem to work that out.