Daniel Eran Dilger in San Francisco
Random header image... Refresh for more!

Apple’s Safari grows to 8% browser share, WebKit now second only to Microsoft IE

Apple’s Safari browser has now exceeded an 8 percent share of web browser use across all devices, powered by strong growth in iPhone and iPad sales.

The new high water mark for Apple’s web browser, combined with Google’s popular Chrome browser, also now makes Apple’s WebKit the second most widely used rendering engine among web browsers, second only to Microsoft’s Internet Explorer and just slightly ahead of Mozilla’s Firefox.

According to Net Application’s NetMarketShare data, in the last two years, Microsoft’s IE has slipped from nearly 67 percent share to just 52.8, while Firefox use has slipped slightly from almost 23 percent to July’s reported 21.48. Google’s Chrome as exploded from 2.84 percent to 13.45 percent, while Apple’s Safari share has nearly doubled from 4.07 percent to 8.05 percent.

Chrome and Safari combined now represent more than 21.5 percent of web users, slightly ahead of Firefox even before adding in a small number of alternative WebKit browsers.

A decade ago, Microsoft’s share of web browsing with the Windows-bundled IE reached such overwhelmingly high numbers that it appeared unlikely that any other browser could ever gain more than a scrap of market share, given the apparent lack of any profit incentive to develop an alternative web browser.

The failing Netscape Navigator browser was eventually spun off into an open source project that resulted in Mozilla, which developed the Firefox browser. Its advantages in speed and other features, combined with its independence from Microsoft, quickly created an avid following among both PC and Mac users.

The Rise of Safari and WebKit

In 2003, Apple debuted work on its own Safari browser, after Microsoft stopped actively developing IE for the Mac. Apple leveraged the existing, open source KHTML rendering engine, which it forked to deliver WebCore, a parallel project Apple continued to maintain under the GNU LGPL.

Two years later, Apple released its entire layout engine for Safari under the more permissive BSD license, naming the entire package WebKit. This package proved to be far more valuable to third parties than just the core KHTML-based rendering engine, causing WebKit to immediately be adopted by Nokia for use in its smartphone web browser for Symbian.

Google later adopted WebKit for use in both its desktop Chrome and mobile Android browsers. RIM’s modern BlackBerry 6.0 browser and HP’s webOS browser and entire application runtime are also based on WebKit, as are the majority of other mobile browsers, including Amazon’s latest Kindle browser. WebKit is also used within a variety of applications, ranging from Apple’s own Mail, iTunes and Dashboard to Adobe’s AIR and Creative Suite CS5 and Valve’s Steam gaming platform.

Widespread use of WebKit has enabled Apple (and other WebKit developers) to rapidly deliver and deploy new web standards ranging from Apple’s Canvas to a variety of enhancements to CSS, HTML and SVG, without worrying that there won’t be enough modern browsers available to take advantage of the new features. This has enabled the development of a new open platform for sophisticated web applications, commonly referred to as HTML5.

Shifting the industry toward HTML5

Apple’s successful development of not just a desktop browser in the model of Firefox but also the creation of Mobile Safari for iOS devices as the first very usable, high performance mainstream mobile browser (something Mozilla has yet to deliver itself) has left a tremendous mark not only on the web browser market but in web-related development as well.

The exclusive use of HTML and JavaScript on Apple’s iOS devices without any provision for plugins such as Adobe Flash and Microsoft Silverlight has upended Adobe’s control over the deployment of web video and other dynamic content, forcing the company to bring its development tools to an open HTML5 foundation in order to reach the valuable iOS segment of the market.

Microsoft has also largely abandoned Silverlight, its own Flash-like development environment, to instead focus on standard HTML5 tools for building web apps and services.

5 comments

1 relativity { 08.01.11 at 4:43 pm }

Welcome back Daniel, or is it…Where is the usual “Daniel Eran Dilger” prologue…Is this a hack by Anonymous? LoL…

2 Mike { 08.01.11 at 5:23 pm }

Let me be the second to welcome the columns back. Your written work is much superior to the interviews (sorry).

Re: Safari and WebKit. On a Mac, the latest Safari has major issues with memory fragmentation. I use a lot of tabs (50-70 maybe, spread across about 10-15 windows) and 5.1 even more than 5.0 before now slows my Mac Mini down to a crawl after only a few hours. I can’t realistically run any other large memory app together with Safari anymore.

I ditched it and am using Chrome. It is a lot better than Safari and my system has been reborn. The only problem with Chrome that I have found so far is that it does not respect custom monitor color profiles, which is kind of a problem. But it’s not anywhere near the problem Safari has with slowing the system down.

3 macsdounix { 08.01.11 at 7:06 pm }

Yeah, it’s Daniel. This article – along with the iCloud piece – bear his byline on Appleinsider. Hope all is well, Dan.

4 macsdounix { 08.01.11 at 7:07 pm }

bears his byline. Gad, I hate subject-verb disagreement.

5 Jonathan Gibson { 08.03.11 at 7:13 am }

Webkit has changed application development around the shops I’ve worked with in Silicon Valley this decade, even before the proliferation of smart-phones.

I have been impressed at how so much of the development process can revolve around a webkit-centric engine. Wikis can keep the client feeling informed and aware, working notes for the team, functional + design specs are available to all with ease, documentation, marketing, interface design, to prototypes from the code team can all gather around this hub.
Open sourced means all you need to do is fork over your own version with custom libs and you can let Webkit put your best foot forward handling typography, layout, etc… and it’s cross-platofrm for all intents and purposes.

Welcome back Mr Dilger… my summer was a tad boring without your caustic wit skewing the deserved and praising the noteworthy.

You must log in to post a comment.