The Web in Google's Mobile Browser
Android's SDK offers an emulator that, among other things, lets you use the browser. Google used WebKit, an application framework that also powers Safari and Nokia's S60 browser. — Android's browser does a good job at rendering complex web pages …
Context & Ripple Effects
The browser reveal lands the same day as the early look Android SDK itself: the emulator Google shipped lets anyone drive the phone's browser on a desktop, and the screenshots Gizmodo picked up give the public its first real view of how pages will look on an Android handset. The notable engineering choice is underneath — the browser runs on WebKit, the same framework powering Apple's Safari and Nokia's S60 browser.
That means three of the most-watched names in mobile — Google, Apple and Nokia — are now rendering the web with one codebase. Reviewers testing the emulator report it handles complex pages well, which matters because rendering quality was the standing complaint against the phone browsers people already own.
First-order effects
- Developers working with the new SDK can test full-page web rendering in the emulator immediately, giving Android a visible answer to 'how good is its browser?' before any handset ships.
- Nokia's S60 and Apple's Safari now share their rendering engine with a Google-backed platform, quietly aligning three otherwise competing phone stacks on one web implementation.
Second-order effects
- Web developers gain an incentive to treat WebKit as the common denominator for mobile targets — a page tuned for Safari and S60 rendering now also covers Android, concentrating testing effort on one engine.
- Browser makers still shipping their own engines face rising compatibility expectations, since the pages users see on Android-class devices become the reference for what a phone browser should display.
Third-order effects
- If the engine convergence holds, competition among mobile platforms shifts from rendering fidelity to integration and interface — the browser hardens into the default application layer on phones rather than a per-vendor differentiator.
The trend: Mobile browsers are consolidating around shared open engines like WebKit, turning rendering quality into table stakes and pushing platform rivalry toward everything layered above the page.