All BlueprintsLogistics
Doorstep delivery tracking
A customer watches the rider carrying their parcel approach on a map, the rider's phone reports where it is as they drive, the app works out that it has arrived without being told, and a photograph at the door settles what was left and where.
What you’ll build.
Live parcel tracking. Customers watch the rider carrying their parcel cross a map without refreshing, and the pin keeps its story straight when the phone comes out of a tunnel. A photo of the doorstep appears with nobody having pressed arrived. Nobody can watch somebody else's rider, or their own a minute after it lands.
What you’ll learn.
Each sprint is built around one skill. You show you have it in a pull request your team reviews, then explain it in a walkthrough.
Authentication
You can register and sign in a user, keep a request authenticated without asking for the password again, and explain where the credential lives in the browser and why there rather than somewhere else.
Assigning jobs to drivers
You can assign a job to a driver, prevent the same job being assigned twice, and show a driver only their own work.
Tracking a delivery
You can record location updates against a shipment and show a customer its current state and history without them refreshing.
Realtime updates
You can push a change from the server to an open page and have a second browser see it — and say what happens to a client that was disconnected while it changed.
Proof of delivery
You can capture proof at the point of delivery, store it against the shipment, and produce it later in a dispute.
Going live
Somebody who has never met you can open a URL and use the product — and you can say what is different about the copy running there, where its secrets come from, and what you do when a release turns out to be wrong.
The roadmap. 8 sprints, 39 tasks.
Every sprint has a goal and a set of tasks. Open a sprint to see the tasks you will pick up.
Signing on for a shift
A customer can make an account, a rider is issued one they could not have made themselves, and a phone stays signed in through a whole shift.
4 tasks
- A customer can register and come back to the same account
- A rider stays signed in for a whole shift
- Rider accounts are issued, never self-issued
- A phone left in a van can be signed out from somewhere else
A parcel with a name on it
A parcel exists, belongs to one customer and one rider, and two dispatchers handing it out at once produce one rider rather than two.
5 tasks
- A dispatcher can enter a parcel for a customer at an address
- A parcel goes to exactly one rider, even when two people hand it out at once
- A rider opens their phone and sees their own round, in driving order
- Starting a delivery is what makes a parcel the one that is out
- A customer has a page for their parcel that tells them something true
A phone that says where it is
A rider's phone reports where it is for the length of a delivery, every position is kept with the time it was taken, and the phone still has battery at the end of the shift.
5 tasks
- A rider's phone reports where it is while a parcel is out
- How often the phone speaks is a decision with the numbers written down
- A rider standing still stops producing news
- Nothing is reported when there is nothing to report
- A finished delivery keeps a route, not every heartbeat
Watching it move
A customer with a parcel out watches it cross a map with nobody pressing refresh, and the screen is not updated more often than a person can use.
5 tasks
- A customer watches the rider move without pressing anything
- A watching screen is not told more often than a person can use
- A screen that was in a pocket comes back to now, not to then
- The pin moves like a vehicle, not like a teleport
- A customer whose parcel is not out yet is told when, not shown an empty map
Four minutes in a tunnel
A phone that lost signal for four minutes sends everything at once, the trail comes out in the order it was driven, and the pin never moves backwards.
5 tasks
- A phone with no signal keeps the positions and sends them later
- A burst of positions comes out in the order it was driven
- A late position never moves the pin backwards
- The same position arriving twice is one position
- A phone that has gone quiet says so rather than freezing
At the door
The app works out that the rider has arrived from where they are rather than from a button, and the photograph taken at a doorstep with no signal still reaches the customer.
5 tasks
- The app works out that the rider has arrived, with nobody pressing arrived
- A rider the app has not noticed can still say they are there
- A rider photographs the doorstep where there is no signal at all
- The depot can see which deliveries have no evidence yet
- The customer sees the doorstep, and a delivery time they can rely on
Who may watch, and for how long
A customer can watch their own rider while their parcel is out, nobody else's and not a minute after it is delivered, and the server is what refuses.
5 tasks
- One rule decides who may see a rider, and every route asks it
- Six customers watching six riders each see one
- The map opens when the parcel leaves and closes when it arrives
- A rider who is off the round is on nobody's map
- What is kept about a rider's movements is deleted on a schedule
Out on real roads
It is on the internet at its own address, and the live map survives being there.
5 tasks
- A rider and a customer reach it from two different networks
- Nothing the product needs lives only on somebody's laptop
- A customer on one server watches a rider reporting to another
- A lift, and the map picks up where it left off
- Releasing it mid-round is a pause, not an outage
Read before you build. The best engineers do.
Senior engineers read the docs before they touch the code. Every Blueprint comes with short documents on the product and its world, the kind a team hands a new hire. Read them well and you ask sharper questions and walk into every review prepared.
What you are building
The product, the three people who use it, and what makes it harder than a map with a pin on it.
A position is a fact with a time on it
What a phone actually knows about where it is, why every position carries two clocks, and what a shift of them weighs.
More logistics Blueprints.
Tool and asset checkout
A tool store for a small builder's yard. Every drill, ladder and transformer is an individual thing with a tag, the store can say who is holding it and since when, and what has not come back is on one screen before somebody needs it.
Returns handling
The returns desk behind a small shop. A customer asks to send something back and says why, the warehouse answers, a parcel turns up that may not match either, and somebody has to decide what happens to the goods and to the money before either can end up in the wrong place.
Fleet maintenance log
A servicing log for a small fleet: every van's history in one place, the next service worked out from how fast that van is actually being driven, and what is due soon and what is already overdue on the front page.
Build doorstep delivery tracking.
Start your free week. Adaeze runs your kickoff, and Lars reviews every pull request.