Safari on Windows - Apple's Smart Client Play


 Catagories: Computers, and Web

I have spent the last week now looking at everyone’s ideas on why Apple released Safari on Windows.  I think some people have come up with some rather good ideas.  Others have come up with some rather strange ideas.   But I still don’t think that all the real reasons have come out.  Lets look at several key important factors that we know about apple and their direction.

  1. It’s about software.  Steve Jobs stated this several times at the D Conference.  His point is important.  It’s about hardware, with good software.  This has always been the case with Apple.
  2. It’s about the cloud.  Steve also said that his paradigm for software included the cloud of web services.
  3. It’s about the SDK for the iPhone.  Many people have pointed out that by having a version of Safari on the Windows, it allows those individuals to develop applications for the iPhone on the Windows.

Software Software is important.  Having your software running on a given piece of hardware is important.  By itself there is value in having your software run on Windows.   The more software that Apple releases on a given platform the less unique that platform becomes.  The software is the user experience and the brand.  All the software that Apple releases for the Windows platform breaks the branding of Windows.  What would happen if Apple continued to release different pieces of functionality from their iLife applications for Windows.  Would people use them.  Yes.  Would people recommend them.  Yes.  Would they be more usable than the built in Windows software.  Probably.  This hurts the Windows brand.

This also plays right into a weakness that few have exploited up until this point.  Microsoft has to allow for 3rd party applications to replace built in Windows functionality.  As soon as this becomes hard for Apple to do, all someone needs to do is complain about Microsoft lock in.  Google is doing this right now.  I’m surprised more companies are not doing this.  Adobe should start to build Bridge into the basic operating system search, replacing the way Windows handles graphic searches.  Also, I’m not surprised that Microsoft hasn’t played this card against other platforms they are trying to gain traction on.

One final point. Isn’t Safari used to render out all those widgets in OS X?  Will this mean that those guy will now run on Windows and on the iPhone?  If the answer is yes to this question, then we now have a common development environment for these widgets.  This is an end run around Google, Microsoft, and Yahoo all at once.  This also leads to my next point.  This also provides a common platform for Cloud based Applications

The Cloud What applications use the cloud these days.  There are all sorts of tools which use web services.  But in the end, there are only several standards that are available in this space.  The battle is still being fought.

Microsoft has been doing a lot of heavy lifting in this area with their .Net framework and the implementation of WS-* to provide inter-platform operability. All this stuff is great for fat clients and .NET  based smart clients.  But this leaves Apple and Adobe to build in support for the WS-* standards into their smart client applications.

Oh wait, Apple has no Smart Client platform.  Or do they?  Perhaps Safari is their Smart Client Platform play.  Adobe has AIR, and Microsoft has Silverlight.  We notice with both of these platforms each company is extending their strength (Flash and .NET) into an area that is a weakness.  So what do you do if you are Apple.  You need to extend things you control, things like Safari and Quicktime.  I wouldn’t be all that surprised that if in the next 12 months you see WS-* get extended down into both of these applications.  In the mean time we have things like JSON and AJAX.  While you can’t get all the functionality out of these services as you can out of a WS-* framework.  You do get enough to handle the day to day workings of a consumer device.

I predict that Safari + Quicktime will be the Smart Client platform that Apple will move towards in the next year to create their cloud development platform.  This will be done to extend the widgets platform that currently exists today.

SDKs I think this is going to be the true SDK for the iPhone.  If you merge Quicktime into the Canvas tag, then you truly have something.  If I had an iPhone right now, I would love to play around with some of the Apple specific tags supported by Safari.  What happens when I throw widget code at it’s JavaScript interpreter.  What happens on Windows if I do this?  I would also love to point it to a .MOV file online that has some interactive content in it.  Extend and expand this, and you have a nice save environment to build applications that won’t take down the network they are running on.

Summary I feel that the decision to make Safari as the SDK for the iPhone is a good idea if they take some of the steps laid out above.  This is an opportunity for Apple to take control of the platform that will be used to develop “cloud” based applications.  They will leverage their iTunes / Quicktime platform on Windows and combine it with their iPod platform into a cell phone form factor, bypassing the coming standards war which will feature Google, Microsoft, Adobe, and Yahoo fighting it out to control the Smart Client Platform.

Tags: ,

Blog Search