Engineering explained
The best engineering blog posts, explained for frontend architects: what problem they solved, how the architecture works, which trade-offs they made, and what it means for your own frontend. Every explainer links to the original.
- Figma·original post Oct 2019
How Figma's multiplayer editing works
Why Figma skipped operational transformation, how a server-authoritative, CRDT-inspired model keeps everyone in sync, and the clever tricks behind reparenting, ordering, and undo.
9 min readRead explainer - Meta·original post May 2020
How Meta rebuilt facebook.com for speed
Atomic CSS that shrank homepage CSS by 80%, JavaScript loaded in tiers, code chosen by the data it renders, and data fetched in parallel with code: the architecture behind the 2020 facebook.com redesign.
10 min readRead explainer - Airbnb·original post Jun 2021
Airbnb's server-driven UI: the Ghost Platform
How Airbnb lets one backend response decide a screen's layout, sections, data, and actions across web, iOS, and Android, and what server-driven UI costs in return.
8 min readRead explainer - Slack·original post Jul 2019
How Slack rebuilt its desktop app without a big-bang rewrite
Slack modernized a 2012 jQuery codebase into React and Redux by growing a new app inside the old one, shipping piece by piece, a textbook strangler-fig migration.
8 min readRead explainer - Figma·original post Jun 2017
How WebAssembly cut Figma's load time by more than 3x
Figma's editor is C++ compiled for the browser. Switching from asm.js to WebAssembly made loading more than 3x faster, mostly by removing parse and compile work, not download size.
6 min readRead explainer
Bloom isn't affiliated with the companies featured. Explainers are our own analysis of publicly available posts.