Responsive Web Bloopers at Viki
summary
A responsive redesign at Viki exposes three concrete failures: designer–developer back‑and‑forth that omits expectations (missing cinematic mode and angry users), inconsistent CSS practices that increase technical debt, and late device testing that misses device‑specific bugs. The team switches to low‑fidelity prototyping (rule: build fast and ugly, under an hour), a pattern library, and a coding style guide, and adopts tools: localtunnel/proxylocal for device access, Ghostlab for synced manual testing, and Wraith for visual regression; the project is an active three‑month work in progress.
AI-written summary · about
chapters (10)
- 0:00Start
- 0:08Aysha Anggraini Responsive Web Bloopers
- 2:31Working Together Lack of collaboration between designers and developers
- 12:31Not necessary to prototype everything
- 13:53Writing Code Lack of planning on development
- 15:26Naming Conventions File Organizations Nesting levels
- 17:06Sass Style Guide by Chris Coyler
- 19:51Device Bugs by Scott Jehl
- 20:15Testing Site Testing late on devices and relying too much on emulators
- 20:51Testing Interactions
related talks
43mResponsive Web Bloopers at Viki
35mMarty McFly Has A Lot To Answer For
58mNew Adventures in Responsive Web Design
43mResponsive, Adaptive and Responsible
32mBetter Production Decisions with HTML & CSS
29mSquishy Pixels
19mNavigating the web in a world full of constraints
40mDid We(b Development) Lose the Right Direction?