How to Go from a Quick Idea to an Essential Feature in Four Steps

Summary

Grab engineered an in-app messaging platform, GrabChat, to help drivers and passengers coordinate pickups across Southeast Asian markets characterized by weak 2G connectivity and high packet loss. The team developed an in-house TCP messaging architecture consisting of a TCP gateway named Gundam and a message dispatcher named Hermes connected to internal backend services over HTTPS. To protect backend server resources from resend loops during poor connection states, the communication protocol adopts a "server only push once" model that delegates retry handling to the client. Data science evaluations using a pre-trained cancellation prediction model confirmed that GrabChat adoption correlated with reduced booking cancellations. Following early usage feedback, the team further iterated on the feature by introducing pre-written message templates to reduce driver distraction on the road.

Takeaways

1. 1

   Implementing a "server only push once" protocol delegates message-loss retries and heartbeat monitoring to clients, preventing server exhaustion caused by endless resend loops on poor networks.

2. 2

   GrabChat separates concerns by handling client connections through dedicated TCP gateways and dispatchers while exposing HTTPS interfaces for internal service integration.

3. 3

   Data scientists evaluated the feature's business impact by using a baseline machine learning cancellation prediction model trained on pre-launch data to compare predicted against actual post-launch cancellations.