To a Single Page Web App and Back Again
summary
Shopify rebuilds the admin as a single‑page app on a homegrown Batman.js MVC with every page bundled into large asset files, deploys a dozen times a day, then abandons it six months after release. The new approach returns rendering to Rails, uses a modified Turbolinks plus a 255 lines binding system (bindings.coffee), slashes client business logic and asset weight, and ships partial sections successfully so far with noticeably simpler onboarding and better performance.
AI-written summary · about
chapters (7)
- 0:00Introduction and background
- 4:04The evolution of Shopify admin
- 6:05Challenges with Batman.js
- 10:35Lessons in architecture
- 13:43Identifying and fixing jank
- 19:46The move to Admin Next
- 24:37Q&A and final thoughts
related talks
40mClient Side MVC and The Gosh Darn Back Button
43mRefactoring to a Single Page Application
51mBuilding Amazing Single Page Applications the Right Way
33mPitfalls and Opportunities of Single Page Applications
28mSingle Page Applications - was it a good idea?
35mFrontendless Rails frontend
23mRails Frontend Evolution: It Was a Setup All Along
24mBuilding Realtime Singlepage Apps