Product design · Logistics
Shipora
Ordering, tracking and on-time delivery in one mobile app, with the research and persona work behind it.
View case studyLogistics product design and build, from Dhaka
Logistics app design for dispatchers, drivers and the customer at the door
I'm Maniruzzaman Jubayer. With the senior team I lead, I design and build logistics products: delivery and courier apps, fleet and dispatch dashboards, driver apps and the tracking pages customers check while they wait. The goal is a status people believe, screens that work in a cab or a warehouse aisle, and exceptions that reach someone who can fix them.
2 logistics case studies on this site · Apps in React Native and Flutter · Web in React and Next.js
Founders who trusted me with their product, in logistics and beyond
- Years building logistics products
- 6+
- Products shipped
- 50+
- Behance gallery features
- 22
Design engineer and product design lead, with a senior team behind me
04 problems
The problems logistics founders bring me
Four things I hear on intro calls with delivery, courier and fleet teams, and what I do about each.
Problem 1: Customers keep asking where their parcel is
When the app says "in transit" for a day, people call support or stop trusting the estimate. I design status as a timeline of real events with times beside them, an arrival window instead of a false-precise minute, and a plain message when something slips, so the customer knows before they have to ask. It's the thinking behind Shipora, a delivery app built around live tracking that my team designed.
Problem 2: Drivers fight the app instead of driving
Drivers use a phone in a cradle, in glare, often in gloves, with one hand and patchy signal. I design for that: large targets on the main action, high contrast, scanning before typing, as few taps per stop as the job allows, and an offline queue that shows clearly what has synced and what has not.
Problem 3: Dispatchers drown in alerts and lose the late ones
A dashboard that treats every vehicle the same hides the three that need help. I put exceptions first and keep normal operations quiet: late vehicles, route deviations and failed stops at the top, each with a time, an owner and a next step. It's how I approach screens like FleetPulse, a fleet management dashboard my team designed.
Problem 4: The back office lives in five tools and a spreadsheet
Orders, pricing, refunds and support tickets sit in different places, so a failed delivery bounces between people. I map the order from booking to proof of delivery, then design one admin view where counts by status, a live map and queues to approve or reject sit together, and every problem has somewhere to go.
Logistics products I have designed with my team
Shipora, a delivery app built around live tracking, and FleetPulse, a fleet management dashboard, both designed by my team.
Product design · Logistics
FleetPulse
Real-time control over vehicle networks: tracking, scheduling and performance in one dashboard.
View case studyHave a delivery app or fleet dashboard that people only half trust? Let's look at the status model together.
Start a projectLogistics products I design and build
Most logistics businesses need several of these, and they all read from the same status, so I design them as one system.
Delivery and courier apps
Booking in steps, service and pickup options, a tracking timeline, checkout and order history for the customer, with an admin side for orders, zone pricing, support and refunds.
Fleet management dashboards
KPIs against last week, a live map, an alert feed, route suggestions, driver comparison and maintenance, laid out so a fleet manager sees what is going wrong in seconds.
Driver apps
The day's stops in order, navigation handed to the map app the driver prefers, barcode scanning, proof of delivery, failed-stop reasons and an offline queue, all usable with one hand.
Warehouse and inventory tools
Receiving, picking and stock views for tablets and handheld scanners, with capacity planning for the coming days and clear states for short picks, damaged goods and returns.
Tracking pages and notifications
A tracking page that opens from a text message without an app or a login, with the arrival window, the next event and a way to change the delivery, plus the messages that point to it.
B2B shipping platforms
Portals where business customers book in bulk, upload manifests, print labels, follow many shipments at once and download invoices, with roles for the warehouse, finance and the account owner.
Rules and standards I design logistics products around
These shape screens, copy and flows. This is design guidance, not legal advice: your own counsel and compliance team confirm which rules apply to your operation and market.
EU driving time and rest periods
European Commission, Mobility and Transport: Driving time and rest periods (read 14 October 2026)Regulation (EC) No 561/2006 sets EU limits for drivers of road haulage and passenger vehicles: daily driving of no more than 9 hours (10 hours twice a week), and a break of at least 45 minutes after 4½ hours at the latest. For a driver app, that means showing the time left before the next break, and for dispatch, not offering a run that cannot be finished inside it. The tachograph stays the legal record; the app only reflects it.
GS1 SSCC for parcels and pallets
GS1, Serial Shipping Container Code (SSCC) (read 14 October 2026)GS1's Serial Shipping Container Code identifies a logistic unit, such as a case, pallet or parcel. On screens, I design scanning first, show the human-readable code after every scan, confirm with sound and vibration as well as colour, and keep a typed entry with check digit validation for labels that will not scan.
Location permission on iOS
Apple Developer, Requesting authorization to use location services (read 14 October 2026)Apple calls When in Use authorisation the preferred choice for its privacy and battery life, asks apps to request Always only when necessary, and advises asking when someone engages the part of the app that needs location. So a customer app asks when they set an address or start tracking, a driver app asks at the start of a shift, and both have a working state for "no".
Background location on Google Play
Google, Play Console Help: Understanding location in the background permissions (read 14 October 2026)Google Play allows background location only when it is core to the app, approved through a Permissions Declaration Form with a short video that shows the prominent disclosure. Its list of features that could use foreground location instead includes delivery tracking for users, not drivers. I design customer tracking to work in the foreground and draw the disclosure screen a driver app needs for review.
WCAG 2.2 target size
W3C, Understanding Success Criterion 2.5.8: Target Size (Minimum) (read 14 October 2026)Success criterion 2.5.8 asks for pointer targets of at least 24 by 24 CSS pixels, with listed exceptions. That is a floor, not a goal. In a moving van, in gloves or in a cold store, I make the main action of each driver and warehouse screen far larger than that, and space the rest so a slip does not mark the wrong stop as delivered.
Proof of delivery and data retention
ICO, UK GDPR guidance: Principle (e) Storage limitation (read 14 October 2026)Photos at the door, signatures and a driver's location trail are personal data. The UK regulator's guidance on storage limitation says you must not keep personal data longer than you need it, and should set standard retention periods. I design proof-of-delivery capture that frames the parcel, and admin screens that show how long each record is kept and when it is deleted.
How I run a logistics app design project
The same four steps as every project, with the checks a delivery or fleet product needs added in.
- 01
Free 30 minute intro call
We talk through one parcel or one vehicle's day: who books, who dispatches, who drives, who answers the phone when it goes wrong. No slides and no sales pitch, just an honest view of whether I can help.
- 02
Written scope and one fixed quote
The scope lists each role (customer, driver, dispatcher, admin), each platform, the systems the product talks to and the full list of statuses. You get one fixed quote for the whole project before any work starts. No retainer.
- 03
Design sprints with field checks
Weekly sprints in Figma, an update every 48 hours in Slack and a review call each week in your time zone. Driver and warehouse screens are checked at arm's length, outdoors and one-handed, and every permission has a refused state drawn.
- 04
Handoff and build
A design system, a state table for every status and exception, and a walkthrough with your engineers. If you want it, my team builds the apps in React Native or Flutter and the dashboards in React and Next.js.
What you get from a logistics app design project
Everything your team needs to build the product, or to let mine build it, from the status model to the last empty state.
A status model and event map
Every status an order or vehicle can be in, what moves it on, who sees it, and the words each audience reads. This is the document the rest of the design hangs on.
Customer app and tracking page
Booking, tracking, changing a delivery and getting help, on iOS, Android and a tracking page that opens from a text message without an app.
A driver app built for one hand
Stops, scanning, proof of delivery and failed-stop reasons, with large targets, high contrast and offline states for basements and rural roads.
Dispatch and fleet dashboard
Exceptions first, a live map, KPIs with their comparison, and queues where each alert has an owner and an action, on desktop and tablet.
Admin and back office screens
Orders by status, pricing by zone, support tickets by priority and refunds to approve or reject, in one place.
Permission, offline and error states
Location, camera and notification prompts with their priming and refused screens on both platforms, plus sync, retry and stale-data states.
A design system in Figma
Components, tokens and usage rules, in light and dark, ready for more than one language, so the customer, driver and admin sides stay consistent.
The build, if you want it
Apps in React Native or Flutter and web in React and Next.js, by the team that designed them. See development.
Services that logistics teams hire me for
Pick one, or combine them: most logistics products need a mobile side and a web side.
The logistics market in official numbers
From statistics offices, quoted as published, with the year each figure covers.
- Total road freight transport in the EU in 2025, nearly 13.3 billion tonnes of goods.
- 1 886 billion tonne-kilometres
- Eurostat, Road freight transport statistics, data extracted July 2026 (read 14 October 2026)
- Share of EU internet users who bought or ordered goods or services online in 2025, up from 62% in 2015.
- 78%
- Eurostat, E-commerce statistics for individuals, data extracted February 2026 (read 14 October 2026)
- E-commerce's share of total US retail sales in the second quarter of 2026, seasonally adjusted.
- 17.1 percent
- US Census Bureau, Quarterly Retail E-Commerce Sales Report, 2nd quarter 2026 (read 14 October 2026)
- Van traffic on Great Britain's roads in 2025, 10.0% higher than in 2019.
- 58.8 billion vehicle miles
- Department for Transport, Road traffic estimates in Great Britain: 2025, published 20 May 2026 (read 14 October 2026)
My team, a large agency or a freelancer for your logistics product
An honest comparison, including the rows where the other two win.
| What you get | My team | Large agency | Freelancer |
|---|---|---|---|
| Senior people doing the work, not just selling it | Yes | Sometimes | Yes |
| You talk directly to the people designing | Yes | Usually via an account manager | Yes |
| Customer app, driver app and dashboard as one system | Yes | Yes | Often too much for one person |
| Design and build by the same team | Yes | Often | No |
| Cover when someone is ill or away | Yes | Yes | No |
| One fixed quote for the agreed scope | Yes | Sometimes | Sometimes |
| Workshops on site at your depot | No | Often | Sometimes |
| Many large workstreams at once | No | Yes | No |
What founders say about working with me
Working with Jubayer and the team has been a blast. Their creativity has honestly taken our platform to new heights. Incredibly professional and so proud to work with, we’re over the moon with their results, and we can’t wait to team up with them again.
I highly recommend Jubayer for any design project. He quickly grasps complex concepts, excels in standard design practices, and responds promptly.
Guides for logistics product teams
Writing on the dashboards, permission flows and app reviews that delivery and fleet products depend on.
SaaS dashboard design: best practices for daily use
SaaS dashboard design best practices for a product people open daily: start from the morning decision, then pick metrics, charts, states, alerts and colour.
App Store rejection reasons: 10 design fixes before review
App Store rejection reasons I design around: account deletion, Sign in with Apple, permission prompts, in-app purchase, privacy labels and demo accounts.
WCAG 2.2 in React: the accessibility checklist we ship with
A WCAG 2.2 React checklist for level AA: what changed in 2.2, the components that fail most, short TypeScript fixes and the tests that keep them fixed.
Logistics app design: questions buyers ask
Straight answers to what delivery, courier and fleet founders ask before they start.
How much does logistics app design cost?
It depends on how many roles the product serves (customer, driver, dispatcher, admin), how many platforms, which systems it connects to, such as telematics, carrier or payment APIs, and whether drivers need offline work or more than one language. After a free 30 minute intro call I write a scope and give you one fixed quote for the whole project, so you know the cost before you commit. There is no retainer and no hourly billing.
How long does it take to design a delivery app?
It depends on how many roles and flows the first version needs. A customer app with booking and tracking is a smaller job than customer, driver and admin sides together, and offline work or a second language adds time. A focused first version is usually a matter of weeks, not months. The written scope after our intro call sets out the timeline flow by flow, so you can plan a launch on a real schedule.
Can you design a fleet management dashboard?
Yes. My team designed FleetPulse, a fleet management dashboard. I start from the decision a fleet manager makes in the next hour, then put exceptions first: late vehicles, route deviations and maintenance that is due, each with a time and a next step. Routine numbers stay calm, every headline figure has a comparison beside it, and the same screens work on a tablet in the yard.
Does a delivery app need background location?
The customer side usually does not. Google Play lists delivery tracking for users, not drivers, among features that could use foreground location, and Apple prefers When in Use access. A driver app that tracks a route with the screen off may need more, which on Google Play means a declaration and a video of the disclosure screen. I design both paths, and your developers confirm what the build needs.
Can the driver app work without signal?
It should, because basements, lifts and rural roads drop signal every day. I design an offline queue: scans, photos and signatures are saved on the phone, the screen shows what is waiting to sync, and nothing is lost if the app closes. My team builds driver apps in React Native or Flutter, and we agree the sync rules with your backend team during the scope.
Can you work with our existing dispatch or warehouse software?
Yes. Most logistics products sit on top of systems that already exist, so I map what your current software holds and which screens read from it before designing. My team builds the front end against your APIs, or hands your developers a design system and a state table for every status. I do not need to replace your backend to improve what drivers, dispatchers and customers see.
Do you design for drivers' hours rules?
Yes, as design guidance. Under EU rules a driver takes a break of at least 45 minutes after 4½ hours of driving at the latest, so a driver app can show the time left before the next break, and dispatch can avoid offering a run that does not fit. The tachograph stays the legal record. Your compliance team confirms how the rules apply to your fleet and market.
Will I own the designs and code?
Yes, everything. Every Figma file, the design system with its components and tokens, the prototypes, the status model, the handoff notes and any code my team wrote are yours, with no licence fees and no lock-in. Your developers can carry on without me the day the project ends, and I'm happy to sign your NDA before you share anything.
Sources and references (10)
- European Commission, Mobility and Transport: Driving time and rest periods (read 14 October 2026), read 14 October 2026: transport.ec.europa.eu
- GS1, Serial Shipping Container Code (SSCC) (read 14 October 2026), read 14 October 2026: gs1.org
- Apple Developer, Requesting authorization to use location services (read 14 October 2026), read 14 October 2026: developer.apple.com
- Google, Play Console Help: Understanding location in the background permissions (read 14 October 2026), read 14 October 2026: support.google.com
- W3C, Understanding Success Criterion 2.5.8: Target Size (Minimum) (read 14 October 2026), read 14 October 2026: w3.org
- ICO, UK GDPR guidance: Principle (e) Storage limitation (read 14 October 2026), read 14 October 2026: ico.org.uk
- Eurostat, Road freight transport statistics, data extracted July 2026 (read 14 October 2026), read 14 October 2026: ec.europa.eu
- Eurostat, E-commerce statistics for individuals, data extracted February 2026 (read 14 October 2026), read 14 October 2026: ec.europa.eu
- US Census Bureau, Quarterly Retail E-Commerce Sales Report, 2nd quarter 2026 (read 14 October 2026), read 14 October 2026: census.gov
- Department for Transport, Road traffic estimates in Great Britain: 2025, published 20 May 2026 (read 14 October 2026), read 14 October 2026: gov.uk