Mission Report · MapMyIndia [Gtropy]Project case study

Intouch

Built for ten thousand vehicles, architected for fifty thousand, because the second number is the one that arrives without warning.

Status
Shipped
Owned
Frontend · performance
Active vehicles
10,000+
Headroom
Scaling to 50,000
Distribution
Live on Play Store
Stack
  • React
  • Ionic
  • TypeScript
  • RxJS

ResultsMeasured

10,000+
Active vehicles
50,000
Designed headroom
Live
On the Play Store
101001K10K100K1M
  • 10,000+ active vehicles
  • 50,000 designed headroom
Log scale · faint markers are this site’s other measured figures
Brief

A cross-platform logistics management app for fleet operators.

Context

Logistics teams run on their phones. The app had to hold up under high-frequency data on Android and iOS, and it had to be built for a fleet larger than the one it launched with.

Users

Logistics and fleet operations teams.

Discovery

Operators segment fleets constantly (by status, region, customer, vehicle type) and they replay trips to understand what happened. Those two behaviours shaped the product more than any dashboard request.

Problem

Optimising for the fleet you have today produces an app that breaks on the fleet you have next quarter.

Hypothesis

If filtering is instant and trip history is visual, most of the questions that would otherwise become a call to someone get answered inside the app.

Strategy

One Ionic and Angular codebase with a modular NgModule architecture, so features could be added without re-testing the whole app, and the same components could serve both platforms.

Prioritization

Real-time tracking first, then quick filters, then animated trip playback, then the dashboards. Each stage had to stay smooth at 10,000 active vehicles before the next one started.

UX

Quick filters for instant segmentation, animated trip history for journey analysis, and dashboards that lead with the operational read rather than the chart.

Design

Responsive layouts across device sizes; dense fleet lists with clear status; playback controls that feel like a media player because that is what people already know.

Technology

Cross-platform build, optimised for 10,000+ active vehicles with a path to 50,000.

Build

Ionic and Angular in TypeScript, REST integration tuned for mobile consumption, and rendering optimised for high-frequency live updates. In production at 10,000+ active vehicles, architected for 50,000.

Outcome

Live on the Play Store.

Learnings

Designing for the fleet you will have, not the one you have, is cheaper than it sounds, provided the architecture decision is made before the first screen, not after the first outage.

Next missionLocate — Manufacturer BackendTwenty thousand vehicles across one state, watched from both a desk and a phone. The two screens needed the same truth, not the same layout.