How to put the Mobile in the Mobile Web
summary
A concrete case: a seven‑page guerrilla mobile website puts a telephone link on every page and after six months analytics show 57% Blackberry and 23% iPhone traffic, proving mobile-first matters. Methods compared: media queries, client-side JavaScript user-agent and feature detection, and server-side detection with libraries like WURFL or detectmobilebrowsers. Notes on bandwidth constraints, Opera Mini compression, and progressive fallback guide whether to serve a slim mobile site, responsive CSS, or a server‑redirected experience.
AI-written summary · about
chapters (28)
- 0:00Intro
- 1:00What is Ultimate Removal
- 3:00guerrilla mobile website
- 3:55demo company website
- 4:55my hunch
- 6:50Navigation
- 7:15Bandwidth
- 8:30Lebanon
- 9:30Data schemes
- 10:50Three approaches
- 11:25Semantic HTML
- 13:05Responsive Web Design
- 15:00Flexible Images
- 15:40Pros and Cons
- 19:10Meet CJ
- 20:20Mobile Internet in India
- 24:00Mobile Browser Detection
- 26:35Modal Mobile Compatibility
- 27:54Chandru
- 28:55Change in the Mobile Web
- 30:55Serverside Detection
- 31:57Serverside Scripting
- 32:48Werfel
- 34:54Challenges with bandwidth
- 36:25San Francisco is a connectivity black hole
- 37:39We need to pull together
- 41:07Resources
- 42:32Questions
related talks
43mThe Mobile Web: MIA
46mFront performance: the mobile web
05mNot the Mobile Web that you used to know
55mThe Future of the Mobile Web
05m"The Mobile Web: The Next Frontier"
35mWhat's Wrong with Mobile Web?
46mMobile- Or Attacker-Friendly? A Security Evaluation Of Mobile-First Websites
53mPerformance Checklist for the Mobile Web