Case Study · Porter (Logistics & Last-Mile Fleet)

Intra-City Logistics Dispatch and Driver Matching Engines

Re-architecting driver vehicle apps and payment systems for one of India’s largest intra-city logistics networks.

CompanyPorter
RoleTeam Lead, Android & Systems
TimelineMar 2020 – Nov 2021
LocationBengaluru / Noida, India

The Context

The initial technical situation.

Porter powers on-demand logistics for intra-city truck and two-wheeler freight across major Indian metros. Real-time matching between shippers and nearby drivers is latency and battery critical.

Identified Bottlenecks

What was broken or failing to scale.

Legacy MVP code in React Native suffered from memory leaks, UI jank during navigation, and aggressive battery drain from unoptimized GPS polling.

Driver payment settlements and trip training platforms were fragmented across external tools with no direct reconciliation against the supply-chain matching core.

Frequent offline periods in dense urban corridors caused driver status desync and dropped booking dispatches.

Technical Leadership

Key architectural decisions and rationale.

Migrated driver and owner apps to native Kotlin with RIBs architecture

Decoupled state management from view hierarchies, enabling continuous feature delivery, zero background memory leaks, and resilient offline state sync.

Engineered backend payment and training platforms in Java / Spring Boot

Created idempotent billing and payout microservices integrated directly with the core supply-chain dispatch engine.

Implemented battery-efficient geofencing and GPS telemetry filtering

Replaced continuous GPS streaming with velocity-based adaptive polling, preserving driver device battery throughout 10-hour shifts.

Measured Impact

Verifiable results delivered to the business.

< 0.05%Driver App Crash RateSource: Measured post-migration to Kotlin RIBs architecture
Real-timePayment Payout ReconciliationSource: Integrated Spring Boot payment services with supply chain core
ContinuousFeature Delivery VelocitySource: Standardized release trains and decoupled architecture
For your engineers: Technical architecture & telemetry▼

Lessons for Startup Founders

  • In driver and field apps, battery life is your retention metric. If your app kills the driver phone battery before 2 PM, they will turn off location tracking.
  • Decouple business logic from UI routing using RIBs or clean architecture. It prevents mobile rewrites when product teams re-imagine onboarding.
  • Build idempotent payment settlement endpoints from Day 1. Unhandled retries in mobile networks will cause duplicate payouts or angry drivers.

Key Technologies Deployed

KotlinRIBs ArchitectureJavaSpring BootHibernateGeospatial TelemetryREST APIs

Work with Umesh Gupta

Scale your architecture without trial and error.

Book a 20-minute call or send a direct message on WhatsApp. I respond the same business day.