Now that we have an app, let's kill our mobile site!
summary
Company builds a dedicated mobile web site (75% of traffic) by scrapping a bulky responsive shell and shipping a hand‑rolled CSS framework plus shared server‑side models, deliberately targeting a subset of browsers. Animations run with zero lines of JavaScript (CSS transforms) and an on‑recharge rocket animation yields a 33.3% uplift in conversions. Later traffic from Opera Mini/UC Mini exposes the browser coverage gap, prompting consideration of server‑side rendering (Node.js) and broader graceful degradation.
AI-written summary · about
chapters (33)
- 0:00Intro
- 2:07Serious question
- 5:28Building a mobile web experience
- 7:17Identifying the top browsers
- 11:18Keeping it meaningful
- 11:53Process steps
- 14:18Animations
- 15:06Performance
- 15:34Demo
- 17:35Is it native
- 23:51The Flying Rocket
- 24:33Zero lines of JS
- 27:59Sharing code
- 29:18Frameworks
- 31:16Challenges
- 33:35Go JavaScript free
- 35:21Platformspecific experience
- 36:51Mobile only
- 37:43Experience
- 39:29Common Sense
- 40:06Bullshit
- 40:56Create desktop shortcut
- 41:33Do brands have a responsibility to educate users
- 42:20What is your take on this
- 44:27Browsers not app vs mobile
- 44:54No strong opinions here
- 45:32Cherrypicking browsers
- 46:06Cherrypicking was a bad idea
- 47:42Manual route
- 48:33Classic recharge
- 50:47Beta groups
- 52:15Split CSS
- 53:22Should features be on mobile
related talks
31mMobifying eCommerce: taking an internet business mobile
49mUX Patterns for Web Developers
55mReckoning: Frontend's Lost Decade
42mBuilding quick apps in 2018
29mBringing Mobile Web back to Life
42mChallenges for Developers of Building Large Web Applications
37mA Single Page Story
39mDoes The Browser Have A Future