You’ve seen this before.
App says:
Delivery in 8 minutes
You get excited.
10 minutes pass.
20 minutes pass.
Then you check again…
Rider is nearby.
Still nearby.
Forever nearby.
So I turned this into a coding challenge.
And surprisingly…
This is a real system design problem.
The Problem
The logic looks simple:
- Take distance
- Add travel time
- Adjust for traffic
- Show ETA
Seems reasonable.
But real-world delivery is chaos.
⚠️ What Goes Wrong?
In real delivery systems:
• Traffic changes suddenly
• Restaurant prep takes longer
• Rider handles multiple orders
• Weather delays everything
• Routes change dynamically
And suddenly:
App says 8 minutes
Reality says 38 minutes
That’s how pizza starts teleporting.
What I Observed
When exploring this problem:
- Basic solutions used simple formulas
- Many ignored restaurant prep time
- Some ignored order batching
- Very few handled real-world uncertainty
The code works.
But the prediction lies.
The Real Issue
This is not just math.
It’s about:
• Prediction systems
• Real-time data
• Optimization
• Uncertainty handling
Because:
ETA is a prediction problem, not a multiplication problem.
What a Better System Needs
A smarter system should consider:
- Distance + live traffic
- Restaurant prep delays
- Rider route optimization
- Multi-order batching
- Prediction confidence buffer
This ensures:
Fewer fake ETAs
Better user trust
Less “where is my food?” panic
Try My Challenge
I turned this into a challenge on VibeCode Arena.
Because honestly…
“The pizza teleportation bug” needed investigation
Try it here:
https://vibecodearena.ai/duel/9f279df7-06d1-4420-8431-dc5b5c7ea216
Can you:
- Fix fake ETAs?
- Improve delivery prediction?
- Build a smarter system?
Final Thought
Some bugs crash systems.
Some bugs make users angry.
This one…
Makes people stare at the delivery map for 30 minutes.
So tell me
What’s the biggest lie:
“Delivery in 8 mins”
or
“Rider is nearby” ?
