The making of Twitter Lite
summary
A production Progressive Web App called Twitter Lite uses Node.js React Redux Service Workers and Webpack and ships a largely client rendered experience with no server side rendering the small Node.js server cuts compute costs dramatically and the app downloads are download under 1 MB most work happens after first tweet render Engagement lifts are concrete: 50% more monthly uniques 85% more home visits 80% more original tweets over 1M daily launches push totals exceed 10M a day images defer using requestIdleCallback
AI-written summary · about
chapters (24)
- 0:00The making of Twitter Lite
- 0:30Why Twitter Lite?
- 0:42Reach every person on the planet
- 0:56The internet is slow and expensive
- 4:33Reactions
- 5:04Availability and accessibility
- 5:32Recovering from network failure
- 6:00Progressive loading and rendering
- 7:02Data usage
- 8:17Measure in production
- 9:08Server-side rendering?
- 9:58Design systems
- 10:18Involving designers from the start
- 11:23Flexbox layout and better primitives
- 12:12Iteration speed
- 12:28Adapting in time
- 13:23Disposable software
- 13:56Continuous learning
- 14:15Failure is the condiment that gives success its flavor.
- 14:55Beginner's mind
- 15:40Awareness of assumptions
- 16:38The future
- 17:08Web Apps everywhere
- 19:52React Native for Web
related talks
06mJames Bellenger, Twitter | Node Summit 2017
28mTwitter Lite, React Native, and Progressive Web Apps
34mEnsuring Reliability of High-Performance Applications
27mResiliency and PWAs
45mThe (Awesome) Future of Web Apps
01h 00mBuilding Progressive Web Apps with React
32mProgressive Web Apps
25mBulding (Progressive) Web Apps