Facebook engineers talk about React.js and problems the company faced going mobile first
Facebook engineers: Going mobile-first is not as easy as it looks — Going mobile-first is not as easy as making such a declaration to the world. It requires a lot of organizational changes (and money), according to Facebook engineers.
Context & Ripple Effects
This interview lands five months after Facebook open-sourced React Native for iOS with Android support promised, and it is effectively the engineering post-mortem behind that release: the mobile-first declaration was cheap, the reorganization and money behind it were not.
The arc since then validates the pain — React grew into a widely adopted UI library still run by a small full-time team at Facebook, and by 2020 the company was finishing a redesigned desktop site that brought web back in line with its mobile-first rebuild.
First-order effects
- Facebook's own engineering organization bore the direct cost: teams had to be restructured and funded around mobile development rather than treating apps as a port of the web codebase.
Second-order effects
- Open-sourcing React Native converts that internal remediation into an ecosystem asset — third-party developers absorb the framework's maintenance burden while Facebook sets the standard its rivals' mobile teams now measure against.
Third-order effects
- If the pattern holds, front-end platform work consolidates around a few company-backed JavaScript frameworks, making hiring and headcount planning for those skill sets a strategic variable — something Facebook's later struggles with engineering recruitment targets made concrete.
The trend: Mobile-first transitions are turning internal framework fixes into open-source platforms that shape the wider industry's tooling.