Messaging Sync: Scaling Mobile Messaging at Airbnb
Article Summary
Zhiyao Wang and the Airbnb team tackled a massive problem: their mobile inbox was loading like a 2001 webmail client. With 100k+ messages per hour, every tap meant a network request, killing UX on slow connections.
Airbnb's Hosts and Homes team rebuilt their mobile messaging architecture from the ground up with Messaging Sync. The old system fetched data on every screen change, creating slow loads, data inconsistencies, and zero offline capability for their most-used feature.
Key Takeaways
- Cut API latency in half with delta syncing instead of full fetches
- Enabled offline message reading by storing locally with sequence IDs
- Increased mobile messages sent by 3.8% (Android) and 5.3% (iOS)
- Reduced response payload size dramatically through incremental updates
- Built dual-API validation to catch regressions during migration
By switching from fetch-on-every-tap to delta syncing with local storage, Airbnb doubled inbox speed and drove daily visits up 200% on Android and 96% on iOS.
About This Article
Airbnb's messaging system needed server subscriptions to every object that affected the inbox, including reviews, bookings, and listings. This made it hard to track which changes should actually update when a thread was last modified.
The team decided to subscribe only to review changes and update thread timestamps when data was written. This was faster than checking timestamps every time someone read a message.
The Messaging Sync API became more stable. Request duration no longer spiked unpredictably like it did before. Users could now read messages even when offline or on poor connections.