Using Client-Side Ranking to Increase Relevance

Using Client-Side Ranking to Increase Relevance

Using Client-Side Ranking to Increase Relevance

In the previous News Feed architecture, the mobile client sent a request to the server for new stories, and the server returned a batch of ranked stories to be rendered in the UI. This loop would continue as long as someone kept scrolling through their feed. Any stories that were sent to the client but not yet seen remained on the device in a persistent cache, in the same ranked order in which they were sent from server. If a person was offline or on a slow network at app start up, client requests would pull stories from the cache until a new or better network connection was established.

While this enabled people to see News Feed stories even on poor networks, it didn’t guarantee that they were seeing the most relevant stories. For example, by the time an image fully loaded and rendered in feed, that story might be less relevant than a new story sent from the server. We wanted to determine which stories are most relevant to each person as frequently as possible.

In our new architecture, instead of waiting to show new stories until after you’ve seen the stories we already ranked, the next best story is selected from a pool of both new stories from the server and unseen stories from the persistent cache, and then rendered in feed. This happens each time you scroll down one story. Every time the server sends another story, we can rank the story on the client and insert it in the appropriate spot in your News Feed in real time, even on a poor connection.

By creating this pool of stories on the client, we are able to rely on the cache to consistently show people new stories during a session in the event that new stories from the server are slow to return to the pool. This client-side infrastructure leverages the computing power of mobile devices to dynamically rank stories on the client, giving everyone a better News Feed experience, regardless of their network connection.

Optimizing for connectivity

This architecture also enables us to surface stories that have been optimized for your connection at the time of your session. For example, slow-loading content gets temporarily down-ranked while it loads because, before we show a story in your News Feed, we check to see whether the media in the story — the image, the video, the link preview, etc. — has been loaded on your device. If it hasn’t, we re-rank the stories on the client and prioritize those that have fully-loaded media. In addition, videos might not play automatically when a user is offline or on a bad network. This change improves the consumption experience in emerging markets because people will see fewer gray boxes, spinners and incomplete stories.

While the impetus of this work comes from focusing on improving the News Feed experience for people in emerging markets, these updates also will benefit people who typically have strong internet connections, as we all experience less than ideal internet connections at times. This is just the beginning of making the most of this new architecture and, in the coming months, we’ll continue to iterate and build upon this foundational work and share updates with you on our progress.

Leave a Reply

Your email address will not be published. Required fields are marked *