The mobile web is the part of the web that has to work when screens are small, input is imprecise, networks vary and browser capabilities cannot be taken for granted. The technologies have matured, but the core product question remains the same: how do you deliver useful content and services to the widest realistic audience without creating a separate experience that is harder to maintain?
A durable mobile-web baseline
For most publishing and content products, a responsive site on stable URLs is the starting point. The same primary content, headings, metadata and structured data should remain available across screen sizes. Layout may change, but the mobile version should not become a reduced copy that hides information from readers or search engines.
Progressive enhancement then adds capabilities where they are supported. Core navigation, forms and reading flows should work first; richer JavaScript behaviour, installation, offline support or device APIs can be layered on without making the basic journey dependent on them.
Where device detection still fits
The earlier Mobiletech platform relied heavily on device capability data because mobile browsers were fragmented. Today, responsive design and feature detection cover much more of the problem. Server-side device information can still be useful for constrained payloads, image delivery, analytics or specialised hardware, but it should solve a demonstrated need rather than create a parallel site by default.
The preserved MobileTech AJAX test suite shows how teams once tested JavaScript and DOM support in the field. It belongs here as a historical technical artifact, alongside modern guidance on browser compatibility and progressive enhancement.
Four decisions to make
- Reach: decide which devices, browsers and network conditions matter for the audience.
- Delivery: choose responsive HTML as the baseline, then document any justified adaptive or server-side behaviour.
- Performance: budget page weight, third-party code and rendering work before templates multiply.
- Measurement: combine field data with repeatable lab checks; neither one explains the whole experience alone.
Delivery and resilience
A mobile page can be hidden, suspended, preserved in bfcache, restored or discarded without receiving one dependable final callback. The guide to browser page lifecycle and bfcache explains how to move state saving, analytics and resource handling away from unload.
Start with the cornerstone material
- The mobile highway in 2010 — expectations about devices, fragmentation and mobile growth at the start of the decade.
- Some mobile stats to kick off the new mobile year — a preserved 2011 snapshot of traffic and device-share data.
- Mobile Web vs. Native Apps. Revisited — the domain’s central historical comparison of web and app distribution.
- Mobile Web Performance Reality Check 2026 — a current, evidence-led performance study.
Current primary references
For implementation detail, use the maintained guidance on responsive design and progressive web app best practices from MDN, together with Google’s mobile-first indexing guidance.