Making apps seem faster without optimizing
summary
Claims that perceived speed improves by shifting UX and state rather than CPU work: show immediate percentage complete and live progress updated every second or so, move heavy work into background jobs and persist checkpoints so long tasks persist and resume midway, and stop spamming stdout — replace prints with logging to avoid blocking and noisy I/O. Implements a resumable-job pattern backed by a database, push progress via websockets/SSE, and use optimistic UI updates; demos show shorter wait perception without changing core algorithm performance.
AI-written summary · about
chapters (7)
- 0:00Introduction and welcome
- 5:42Why apps feel slow without changes
- 13:24Perception vs actual performance
- 21:39Setting user expectations
- 30:27Psychological tricks for speed
- 37:56Optimization beyond code
- 42:07Q&A and closing tips
related talks
40mCreating Fast-Feeling Web Apps
21mAsynchronous UX
50mQwik: A holly grail of progressive hydration for ultimate speed
22mRoad to a better UX with Suspense and Concurrent UI
35mThe Impact of Micro-Optimizations on Large-Scale Apps
04mMaking things go fast in
01h 12mMake It Seem Like Everything Loads Fast
27mDon't block the event loop!JavaScript Async for Effortless UX