Smartphone Browser Landscape
Users expect websites to work on their mobile phones. In two to three years, mobile support will become standard for any site. Web developers must add mobile web development to their skill set or risk losing clients. — How do you make websites mobile compatible?
Context & Ripple Effects
Three years after the New York Times described the mobile web as close yet still out of reach, A List Apart's December 2010 argument marks the turning point: the question is no longer whether phones can render the web, but when mobile support becomes table stakes for every site. The piece puts a clock on it — two to three years before mobile compatibility is assumed rather than quoted as an extra.
The timing is underwritten by the browser layer itself: Royal Pingdom's November 2010 finding that 71% of browsers run the latest version means modern rendering engines reach users fast, which is what makes a single mobile-capable codebase realistic instead of a per-device rebuild.
First-order effects
- Agencies and freelance developers face direct client pressure to deliver mobile-compatible sites, and per the confirmed claim, those who don't add mobile web development to their skill set risk losing clients outright.
Second-order effects
- Vendors of CMSs, frameworks, and testing tools gain a new buyer in every shop scrambling to standardize mobile deliverables, as mobile support moves from custom project work to bundled template and theme offerings.
Third-order effects
- If the two-to-three-year standardization holds, mobile capability stops being a separately billable line item and becomes a baseline expectation, repricing basic site builds and pushing competitive differentiation toward richer, application-style web work of the kind the 2007 AJAX-and-mobile-web coverage anticipated.
The trend: Web design is shifting from desktop-first delivery toward mobile as a default client requirement, with developer skill sets and tooling markets repricing around that baseline.