MissionsProjects

Every one started as somebody's bad afternoon

Enterprise fleet and telematics platforms, mostly. The interesting part is rarely the technology — it is deciding what the system should insist on.

10
Bays on the deck
3
Active
7
Shipped
2,00,000+
Users on the largest · Vahan Shakti

Index · 10

Filter the log

The deck as data
K-7

10 of 10 missions

01

Field operations run on people who are never at a desk. The app had to work the way a technician's day actually works.

Stage
Building end to end
MapMyIndia [Gtropy]Angular · Ionic · TypeScript · REST APIs
Read the brief
Problem
Coordination lived in messages and spreadsheets. Nobody could answer where a job stood without asking a person.
Context
Installation, replacement and rectification are three different jobs wearing the same uniform. Each has its own preconditions, its own proof-of-completion, and its own way of going wrong once someone is standing at a vehicle with a phone in one hand.
Users
Field technicians and the operations staff who dispatch and verify their work.
Full mission report ↗
02

Billing was done by hand. The interesting part was not automating the maths. It was finding every place a human was quietly making a decision.

Replaces
A fully manual billing process
Billing & accounts
80% more productive
MapMyIndia [Gtropy]Angular · TypeScript · Spring Boot · Odoo · Razorpay
Read the brief
Problem
Manual billing is slow, and it is inconsistent in ways that only surface at reconciliation time.
Context
A manual process is never only arithmetic. It carries exceptions, tolerances and judgement calls that were never written down anywhere, because the person doing them never needed them written down.
Users
Shop administrators, the billing team and the accounts team, plus the customers renewing a device subscription at shop.mappls.com.
Full mission report ↗
03

Thirty thousand routes is not a data problem you solve once. It is a pipeline you have to trust every time it runs.

Routes injected
30,000+
MapMyIndia [Gtropy]Geospatial data · Amazon S3 · TypeScript
Read the brief
Problem
Generate route data for 30,000+ routes into a form the platform can consume, at a quality the downstream products can trust, with a process that can be re-run when the inputs change.
Context
Indian Oil moves LPG by road across thousands of routes. Every one of those routes needs geospatial reference data (the GeoRTD) before tracking, geofencing and playback can work against it.
Users
The IOCL operations and telematics teams whose tracking products consume the route data, and the internal team maintaining the pipeline.
Full mission report ↗
04

The challenge was never drawing the vehicles. It was keeping the map useful once thousands of them were moving at the same time.

Users
200,000+
Distribution
Live on Play Store
Sector
Government
MapMyIndia [Gtropy]React · Mappls SDK · TypeScript · RxJS
Read the brief
Problem
Live location at national scale, rendered in a browser, without the interface collapsing into noise.
Context
A map that shows everything shows nothing. Past a certain density, every additional marker removes information rather than adding it.
Users
Government fleet operators and administrators, 200,000+ of them.
Full mission report ↗
05

Intouch

Shipped

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

Active vehicles
10,000+
Headroom
Scaling to 50,000
Distribution
Live on Play Store
MapMyIndia [Gtropy]React · Ionic · TypeScript · RxJS
Read the brief
Problem
Optimising for the fleet you have today produces an app that breaks on the fleet you have next quarter.
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.
Full mission report ↗
06

Twenty thousand vehicles across one state, watched from both a desk and a phone. The two screens needed the same truth, not the same layout.

Vehicles
20,000+
Coverage
Maharashtra
MapMyIndia [Gtropy]React · TypeScript · Mappls SDK
Read the brief
Problem
Give both surfaces the same truth without giving them the same layout, and keep everything responsive as live telemetry streams in.
Context
A vehicle manufacturer wanted to see its fleet in the field: live location, engine health, journeys, driver behaviour and driver test scores, across 20,000+ vehicles in Maharashtra, from a desk and from a phone.
Users
Manufacturer operations teams monitoring 20,000+ vehicles across Maharashtra.
Full mission report ↗
07

The system knew everything. It just didn't know what mattered first.

Domain
Alerts & ticketing
MapMyIndia [Gtropy]React · TypeScript · RxJS · Mappls SDK
Read the brief
Problem
Turning a continuous stream of vehicle events into a queue a human can actually work through.
Context
An alert that fires constantly stops being an alert. It becomes background noise with a red icon.
Users
Operations teams responsible for monitoring alerts, working tickets and investigating trips.
Full mission report ↗
08

When the cargo is LPG, a tracking product stops being a logistics tool and starts being a safety one.

Distribution
Live on Play Store
MapMyIndia [Gtropy] · for IOCLReact · Ionic · Mappls SDK · TypeScript
Read the brief
Problem
Live tracking with safety alarms, geofencing and route playback, delivered per role, on a mobile app that field staff would actually keep open.
Context
IOCL runs LPG tanker fleets. Tracking them is a safety programme as much as a logistics one: where each tanker is, whether it left its route, whether an alarm fired, and who is allowed to see which fleet.
Users
IOCL operations and safety staff across roles, each responsible for a defined slice of the fleet.
Full mission report ↗
09

Registration flows are where products lose people. Multi-vehicle registration is where they lose them twice.

Scope
Full stack
MapMyIndia [Gtropy]React · Node.js · REST APIs
Read the brief
Problem
Onboard users with OTP authentication, let them register and manage multiple vehicles, and keep the data in sync securely across the platform.
Context
FASTag registration is a form-heavy process that users do rarely and under mild stress. Owners with several vehicles have to do it several times, and every repetition is a chance to abandon.
Users
Vehicle owners registering and managing FASTags, including fleet owners with many vehicles, and the operators supporting them.
Full mission report ↗
10

Hermes

Shipped

Internal tools get judged by the people who have no choice but to use them. That is a harder audience, not an easier one.

Audience
Internal
MapMyIndia [Gtropy]React · TypeScript
Read the brief
Problem
A modular, consistent, accessible interface for daily internal operations and data management.
Context
An internal logistics and data management tool. Its users could not choose another product, which makes them the most honest audience there is.
Users
Internal operations staff.
Full mission report ↗
Next · Mission historyThe log, in orderRoles, dates, and what each one actually involved. The resume, without the resume formatting.