Migrating from PHP legacy code to React & Best Practices in React
summary
BookMyShow moves its PHP site into React, builds a PWA with Add to Home screen, and claims concrete wins: page load and first paint drop from ~12–13s to about 4s and subpage loads ~2.94s, and a large conversion uplift (uploader: drastic in 4 weeks; transcript cites ~80%). Migration uses React + Redux, tree‑shaking, smaller libs (replaced moment), a shared component library, Redux‑first‑router, and fixes UC‑browser quirks; SEO and SSR tradeoffs require hybrid deployment.
AI-written summary · about
chapters (37)
- 0:00Intro
- 0:28Problems we faced
- 1:07Same code base
- 1:40Problems
- 2:02Fight against legacy code
- 3:01Goals
- 3:47Why React
- 4:37What React gives you
- 5:09What PHP didnt give you
- 7:13Show Times
- 7:53Direct Manipulation
- 8:57Rendering Speed
- 10:20Single Store
- 11:05State Updates
- 11:28Redux Architecture
- 12:26Redux
- 13:23Migration Process
- 14:33First Website
- 17:06UC Browser
- 18:16JavaScript Issues
- 19:26Chrome Dev Summit
- 19:50Tree Shaking
- 20:49MapReduce
- 21:55Engage Library
- 23:00Experiment
- 23:23Thin vs Immutable
- 26:38Why React first
- 28:13World update blocking
- 28:34Redux first router
- 29:30Holden approach
- 30:35Architectural decisions
- 31:45Design Framework Style Guide
- 32:29Importing Components
- 33:20Prop Types
- 34:15Current
- 34:40Optimizing
- 37:18Key takeaways
related talks
32mThe How, What and Why of Migrating to ReactJS
21mMigrating critical apps to React
10mHow to migrate 50,000 lines of code to React Server Components
25mThe first two seconds: Faster page loads with React
59mBring Your PHP Application to the Next Level with React.JS
19mPivoting to React, at scale
32mPractical Performance Tips Building Progressive Web Apps
42mIntegrating React Into Legacy Projects