Mobile Safari is the web browser that shipped on the original iPhone in 2007, built on the same WebKit engine that powered Safari on the Mac. Its arrival marked the point at which a phone could load the real web rather than a stripped-down mobile variant. In the WebKit project’s own post announcing it, written by Maciej Stachowiak and published on January 10, 2007, the team states plainly: “The iPhone version of Safari is, no surprise, based on a version of WebKit. WebKit is also used for the iPhone’s rich HTML mail capabilities.”
That same post made an explicit bet about the future of the web on phones. It argued that the world “may soon see the end of the ‘mobile web’ as a separate concept,” because devices capable of high-quality browsing would remove the need for “a special dumbed down version of the web just for mobile devices.” This was a direct challenge to the prevailing WAP-style mobile web of the early 2000s, and it largely came true: sites began to be built responsively for a single web rather than forked into desktop and mobile editions.
Before the native App Store existed, Mobile Safari was also Apple’s original third-party application platform. At the iPhone’s launch, Apple’s recommended way for outside developers to build for the device was to write web applications that ran inside Safari, using HTML, CSS, and JavaScript. Developers did not get a native SDK until 2008, so for the iPhone’s first year the “app” model was effectively the browser. That early web-app emphasis seeded enduring interest in building applications out of web technology on mobile.
Mobile Safari’s reach extends beyond the standalone browser. Because iOS apps embed web content through WebKit-based components, the same engine renders web views inside countless native apps. Apple’s modern embeddable browser class, WKWebView, is documented as the framework’s view for displaying interactive web content, and it shares Mobile Safari’s rendering core. This makes Mobile Safari’s engine, rather than just its app, the substrate for an enormous amount of in-app web content on Apple platforms.
Mobile Safari’s influence on the web has been significant and sometimes contentious. Because Apple’s App Store policies have long required third-party browsers on iOS to use WebKit, Mobile Safari’s engine effectively defined the web platform available on iPhones and iPads, making the pace at which WebKit adopts new web standards a recurring topic in the web developer community. Whether celebrated for bringing the full web to the pocket or criticized as a gatekeeper, Mobile Safari has been one of the most consequential browsers in the history of the mobile web.