Skip to content

Logistics · Mobile app and PWA

DikkiConnect

Intercity parcels in the empty boot of cars already making the trip

DikkiConnect product screen
Screens built across the app
59Screens built across the app
Roles: sender, traveller, hub, passenger, ops
5Roles: sender, traveller, hub, passenger, ops
Platforms: web, Android, iOS
3Platforms: web, Android, iOS

Context

Cars travel between cities every day with an empty boot. Parcel senders pay for dedicated couriers that make the same trip.

The problem

One product had to serve five very different users — senders, travellers, hubs, passengers and an operations team — without becoming five apps to maintain.

Decisions we made

  • One codebase with role-based flows, packaged for web, Android and iOS.
  • Every hand-off is confirmed with a one-time code, so it's always clear who holds a parcel.
  • Real loading and empty states on every screen, so the product can be demoed and piloted as-is.

What shipped

  • Sender flow: book a parcel, choose route and hub, pay, track
  • Traveller flow: create trips, accept jobs, scan, OTP hand-off, identity verification screens
  • Hub flow: intake, inventory, scanning and receiver pickup
  • Passenger carpooling: search, book, board with OTP, ride tracking
  • Wallet, plus a desktop operations console

Evidence

The complete front end is built: 59 routes across five roles. The public site is the sign-up entry point.

Next case studyFreelancerOS

Next step

Building something like DikkiConnect? Let's talk it through.

Book a 30-minute call with the founders. If we're not the right studio for it, we'll tell you.

  • 30 minutes
  • Free, no obligation
  • Times shown in your time zone