Showing 9 of 29 articles (Page 2 of 2)
When Lyft was first developed, it was built using a monolithic server architecture. Within this architecture, all mobile clients relied on a single endpoint for fetching all data pertaining to the user and their ride (the “state of the world”):
Uber tapped the QUIC protocol to cut latency and make their app feel snappier.
Square speeds up Caviar’s mobile web app for happier users.
Netflix swapped their Android backend quietly, keeping streams uninterrupted.
Meta rethinks server-side rendering to fit today’s React-driven world.
A common complaint we’ve heard from our shoppers is that when they’re deep in the aisles of a grocery store, the app is frequently held hostage to spotty network connectivity.
LinkedIn’s Android data flow keeps their app humming with fresh info.
Dropbox made their networked app feel snappy, like it’s all local.
Twitch overhauled their video system and added Prague servers for speed.