Steve Jobs’ announcement of Safari for Windows at the WWDC yesterday was puzzling to many. What was in it for Apple as a business? iTunes for Windows made sense because of increased iPod sales and iTunes Store purchases, but what could Apple possibly stand to gain from porting a web browser? After giving it some thought, nine possible reasons came to mind.
- First and foremost, the iPhone uses Safari, and the only way for third party developers to develop for the iPhone is through web apps. Having Safari on Windows helps more people develop for the iPhone, which makes for happier iPhone users and perhaps more iPhone sales.
- Apple makes millions of dollars from people using the search box in the browser’s toolbar. I believe that Mozilla made something like $50 million dollars last year from the Google search in Firefox. It’s very profitable, and with version 3 they’re also adding Yahoo.
- Bookmark syncing between Safari on OS X and Safari on Windows (Bootcamp, work computer, multiple computers, etc.) is another incentive for people to pay $100 a year for .Mac.
- Simplifying development of the iTunes Store.
- In Mac OS X, the Safari rendering engine is actually separated from Safari itself into a framework called WebKit that’s used by many different OS X apps, third party software included.
- Apple wants the iTunes store to look identical in both Mac and Windows versions of iTunes.
- The KHTML rendering engine for the longest time could not be used on Windows because it required certain Unix roots. This has only fairly recently been resolved.
For these reasons, Apple has had to maintain two separate rendering engines: one for WebKit and one for iTunes. Apple has always bundled QuickTime with iTunes because it’s what handles the actual grunt work of media playback. They’ll be bundling Safari with iTunes for Windows, and I think that in the future iTunes may use the Safari rendering engine for the iTunes store. That would simplify things for Apple.
- From a fairly long term point of view, this is also about ensuring Apple’s relevance. In the future, it may very well be the case that the web browser becomes your real platform for your apps, and your OS may not matter as much. Apple will be able to offer web apps to Mac users and Windows users. Also, because the KHTML rendering engine used by Safari comes from Konqueror (a browser/file manager for the popular KDE desktop environment for Linux), users of all three major OSes could be potential customers. .Mac could even be the way to access these web apps.
- More exposure to Apple products to Windows users mean more potential switchers, although obviously Apple has to be careful about what they make available so as to not diminish the point of switching entirely.
- More web site compatibility with Safari.
- No need to promote a competitor (Firefox) to Windows users wanting to develop for the iPhone.
- The Apple employees may have wanted Safari for themselves for when they have to use PCs. They are a major Windows software developer after all.
If you’ve thought of some reasons as well, I’d love to hear them.
Paul! You have a blog. WWDC just wasn’t the same with out chatting with you on AIM. Great post, I can’t really argue with any of that.
Here’s a thought – what’s now the easiest way for a phone manufacturer to become ‘iPhone compatible’??
(Clue : it’s open source, 6 letters long, and already available on certain Nokia phones).
Interesting to see the range of problems people reporting with Safari on Windows – says an awful lot about the advantages of end-to-end managing a single platform.
Interesting to see Adobe and Apple have taken different approaches to WebKit on Windows (Adobe use Cairo, Apple have ported CoreGraphics).
Interesting. I wasn’t aware that WebKit was available on Nokia phones or that Adobe was using it. Thanks.
Out of curiosity, what is Adobe using WebKit for? Live preview in Dreamweaver CS3, I’m guessing?
i thought nokia used opera
thats 5 letters
LOL