How to Survive the Single Page App-ocalypse
summary
Claim: many Single Page Apps that teams build around five years after the SPA boom become slow, buggy and resistant to change and SPAs damage businesses when product teams stop early. Evidence: anecdotes about CRUD-heavy apps, Google Maps as outlier, hype around React and Vue, and repeated rewrites that add cost. Prescription: avoid big rewrites, rewrite = forgetting, split by user journey into smaller apps, take small iterative steps that prove simplicity and sustainability.
AI-written summary · about
chapters (4)
related talks
28mSingle Page Applications - was it a good idea?
29mSingle Page Apps: What an API Developer Should Know
23mNot Every App is a SPA
33mPitfalls and Opportunities of Single Page Applications
01h 07mGreat single page apps need great backends
24mThree Keys to Successful Single Page Web Applications
34mSurviving the Big Rewrite
41mOptimize the Size of Your SPA, the Battle for Bytes