explaingit

andrew--r/frontend-case-studies

7,416AstroAudience · developerComplexity · 1/5Setup · easy

TLDR

A curated reading list of real engineering blog posts and talks where well-known companies like Airbnb, Discord, Netflix, and Stripe explain how they built or reworked their frontend systems to handle real production challenges.

Mindmap

mindmap
  root((Frontend Case Studies))
    What it is
      Curated reading list
      Engineering blog posts
      Conference talks
    Topics covered
      Framework migrations
      Design systems
      Performance optimization
      Large codebases
    Companies included
      Airbnb Discord Netflix
      Stripe GitHub Spotify
    Format
      Links only
      No code to run
      Website at frontendcs.com
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Things people build with this

USE CASE 1

Find real-world accounts of how large companies migrated from one frontend framework to another and what problems they encountered.

USE CASE 2

Research how engineering teams at companies like Netflix or Pinterest approached page load performance improvements at scale.

USE CASE 3

Prepare talking points for a tech interview or architecture discussion using documented decisions from industry leaders.

Tech stack

Astro

Getting it running

Difficulty · easy Time to first run · 5min

No code to run, this is a reading list. Visit frontendcs.com for a better browsing experience, the README is no longer updated as of January 2025.

In plain English

This repository is a curated collection of links to technical articles and talks where real companies describe how they built or reworked their frontend systems. The premise is that tutorial projects ("build a todo app with React") do not show how these technologies hold up under the complexity of large, live products. This list gathers the opposite: engineering blog posts and conference talk transcripts from companies that went through real production challenges and wrote about it. The list is organized alphabetically by company name and covers well-known organizations including Airbnb, BBC, Discord, Dropbox, Facebook, GitHub, Google, LinkedIn, Netflix, Pinterest, Spotify, Stripe, Twitter, Uber, and many others. A separate section covers Russian-language case studies from companies including Avito, Yandex, Mail.ru, and others. Topics span a wide range: migrating from one framework to another, building shared component libraries, improving page load performance, making design systems, handling very large JavaScript codebases, and more. As of January 2025, a companion website at frontendcs.com was launched with a better browsing experience. The README notes that the site is now the primary place for new entries, and the README itself will no longer be updated. This is a reading list, not a software tool. There is no code to run. It is useful for frontend developers who want to understand how large companies approach architectural decisions, and for anyone curious about the engineering challenges behind well-known products. The repository is built with a static site generator called Astro, which powers the website version. The full README is longer than what was shown.

Copy-paste prompts

Prompt 1
I'm preparing a talk on frontend performance. Help me find 3-5 case studies from the frontend-case-studies list that cover real-world page load optimization at companies like Netflix, Pinterest, or Spotify.
Prompt 2
I want to learn how large companies migrated from older frameworks to React or modern alternatives. Which entries in this list cover framework migrations and what were the main tradeoffs they described?
Prompt 3
Help me use the frontend-case-studies list to research how Stripe or GitHub approached building and scaling their design systems, including what engineering challenges they highlighted.
Open on GitHub → Explain another repo

← andrew--r on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.