By Zhiyao Wang, Michelle Leon, Jason Goodman, Nick Reynolds, Julia Fu, Jeff Hodnett, Manuel Deschamps, John Pottebaum, Charlie Jiang

Old Inbox vs New Inbox with slow network

With more than 100k messages being sent on mobile per hour, messaging is the most engaged with feature on the Airbnb App. However, with the old inbox fetch method on mobile, the inbox was slow to load, suffered from data inconsistency, and required a network connection to read messages. All of this results in a poor experience for hosts and guests using the mobile inbox. In order to make the inbox faster, more reliable, and more consistent, the Hosts and Homes team at Airbnb built Messaging Sync.

The old inbox fetch was implemented similar to a turn-of-the-century webmail client, doing a network fetch for a screenful of information at every user tap. With messaging sync, new messages and thread updates are fetched only when data change, which greatly reduces the number of network requests. This means navigation between the inbox and message thread screens is much faster, hitting the local mobile storage most of the time, instead of issuing a network request with each screen change. Messaging sync also reduces the response size for each network fetch, which results in a 2x improvement in terms of API latency. These user experience gains are magnified in areas with slow networks.

Here’s how Messaging Sync works, broken into 3 scenarios:

Scenario 1: Full Delta Update

This is the most common scenario:

Mobile client calls the sync API with a sequence_id stored locally (e.g. 1490000000), which denotes the last time the client synced with the server. API server only returns all modified thread objects and new messages after that sequence_id, together with a new sequence_id (e.g. 1491111111). Mobile client merges those updated threads and messages with its local datastore. Mobile client also stores the new sequenced_id to be used next time.

Scenario 2: Initial Sync

This is when there are too many threads and/or messages updates to return. For example, when a user first downloads the App, the server needs to send 10 thread objects and 30 messages for a full delta sync. The full delta sync response payload would be huge, which would result in longer load times and subpar user experience. Instead, we only return a full screen of threads.

Mobile client calls the sync API with a sequence_id stored locally API server estimates the size of the response for a full delta sync, and decides it’s too big. API server sends down only the N most recent thread objects without any messages to have the client render at least a full screen of threads in the inbox view. Client clears its local datastore. Client stores the most recent thread objects and sequence_id. When a user opens a thread, the client requests all messages in the thread from the server. When a user scrolls historically in the inbox, the client sends paginated requests to fetch threads.

Scenario 3: Threads Removal

Threads sometimes need to be removed from the mobile App. For example, when a cohost is no longer managing the listing for the host, the server removes the threads between the cohost and the guest. In this case, the API sends down an array of thread ids deleted after last sync.

Catching Regressions

While migrating to the new messaging sync API, there were couple caveats to watch out for:

Airbnb’s messaging system is closely integrated with its core booking flow and other product logic. The server needs to listen to all changes that affect the data displayed on the inbox screen. For example, after a trip is finished, the App needs to render a “Leave Review” button in the thread. There are two solutions to this. One is to check the review object in read time to see if it has been modified. The other solution is to subscribe to review object changes and update the notion of when the corresponding thread object is last modified. We chose the second solution as it is much cheaper on read time. However, the challenge is to capture relevant changes for all objects that can affect what’s being rendered on the UI. Updated threads could be in a different order from the threads stored locally. We need to make sure that after merging the data, the UI is refreshed correctly.

In order to catch any discrepancies between the data returned by the old messaging API and the messaging sync API, a small percentage of mobile Apps run both the old and the new API at the same time to spot check. It logs all attribute values and the thread order returned from the two APIs. This allows us to catch regressions with the new API and iterate quickly. Whenever a bug is caught, the server marks corresponding thread objects as modified so that it would correct the discrepancy in the next sync.

Conclusions

Messaging Sync API reduced API request latency by 2x. It also results in a much more stable request duration than the old messaging API (spiky blue line below).

2. Messaging Sync makes it possible for users to read messages under airplane mode and bad network conditions.

After rolling out Messaging Sync together with other messaging improvements, we see more messages are being sent from mobile (+3.8% and +5.3% for Android and iOS), fewer messages are being sent from web (-4.6% and -4.2%). And daily inbox visits are way up (+200% and +96%) as it is now the main screen on the hosting mode. The launch is a big win for our hosting community as messaging is the most used feature by hosts on Airbnb.

Last but not least, if you are interested in creating a thriving community of engaged hosts who provide amazing hospitality everywhere in the world, the Hosts and Homes engineering team is always looking for talented people to join!