Apple's fussyness shows the real platform - the web

Recently, there have been public tussles between companies I used to work for. Apple has blocked Google's Latitude and Voice products from being in the iPhone App Store, for reasons they haven't disclosed, though it is speculated because they compete with built-in applications or carrier plans.

The iPhone App Store has gathered so much buzz recently, that it has obscured the underlying effect of the change that is happening due to the iPhone and its imitators. An iPhone is not so much a phone, as a good Web browser in your pocket that works everywhere. By incorporating the excellent Webkit browser, iPhone tipped the pocket net experience from email-like to fully web-like. As I said at its launch, even Steve Jobs can't ignore the Web.

As iPhones, iPods, Androids, Palm Pre Chrome, Safari and some Nokia phones now run Webkit browsers, the growing part of the Web browser usage is in a browser that supports HTML5 and the geolocation, video, vector graphics and local storage APIs that that implies. So Google Voice's website UI can work on iPhone, Android et al and make calls, as can other web applications that make calls.

The real platform that everyone can build on is still the web, and attempts to enclose or limit it will continue to fail. The Open Web Foundation, which I'm proud to be a member of, is working to keep this true and make it easier to grow new web standards and agreements.

MacWorld wishlist

John Gruber says "all Mac-related web sites must publish pre-Macworld Expo predictions regarding what Apple may announce at the show."

What I have is not so much predictions as an "I hope they've been thinking along the same lines I have" wishlist.

• An HD or better laptop. 17" if you must, but I'd like a 15" or smaller. The iPod Nano has 204 pixels per inch and a beautiful display. A 1920x1200 screen at that density would be 7" diagonal, or at iPhone's 163 ppi it would be 8.8" - there's plenty of room. You could get the 30" display's 2560x1600 into a 13" screen at iPhone ppi.
• Come to that, a 7" diagonal HD iPhone/ iPod Touch would be lovely too. Not just for video, but for reading the web and facing-page PDF's on. Give it Bluetooth keyboard support.
• Obviously, a new Mac Mini. I have a big shiny Sony HD TV and I want a little Mac to drive it (are you getting the HD theme here yet?)
• Separate out the phone crap. I don't like phones, and holding screens to my ear is daft anyway. Make the earpiece separate naturally. Come to that, negotiate me a data plan without a calling plan with your carrier buddies. Amazon did it for Kindle. And for goodness sake ship iChat for the handhelds. Put a camera on the top of the screen like the Macs all have.
• Drop DRM already. For videos too. And HDCP. 
• Extend your lovely bluetooth keyboard to have a trackpad too. Make it work with iPhones and the new 7" HD iPod too.
• one more thing -  Phil Schiller, stop charging for QuickTime Pro. Admit the mistake you made ten years ago and make video editing natural again.

Open versus Closed - code and networks

I read two things this morning in praise of closed systems and fêting their future dominance, both by people who should know better. Bob Cringely praises Adobe's Flash, and predicts that AIR will take over the world because Flash can be made to run on cellphones. Clearly, this is wishful thinking on Adobe's part. There is a standard for creating user interfaces that has many orders of magnitude more developers than Flash, is installed on every computer and nearly every cellphone already, and is powerful enough that even Steve Jobs didn't dare to leave it off the iPhone, and that's HTML.

Cringely says:

Once you own the interface to every mobile device you can make those devices talk more easily to your networked applications than possibly to those from Apple, Microsoft, or Sun. As we move toward a fully mobile Internet, compliance with mobile APIs will be more important than what operating system is running on the server, which is why I believe Adobe is putting so much effort behind AIR and Flex.

"Owning" interfaces is not something that you can do when there is an existing interface that is simple, powerful and deployed on every device imaginable already. That would be HTTP - Cringely's piece starts by saying how HTML has made it beyond ubiquity to invisibility, but HTTP is so invisible he doesn't even notice that it's there (let alone TCP or UDP).

Marc Andreesson also has a good underlying point about the Valley's short attention span with regard to technologies, but he too ends up praising a closed application model, in this case Facebook's. They provide access to their users under sufferance, and clearly can't provide access to users of otehr social networking sites. For Marc to back a closed system like this when he has built his career on open ones is odd to me. Kottke puts this well:

As it happens, we already have a platform on which anyone can communicate and collaborate with anyone else, individuals and companies can develop applications which can interoperate with one another through open and freely available tools, protocols, and interfaces. It's called the internet and it's more compelling than AOL was in 1994 and Facebook in 2007. Eventually, someone will come along and turn Facebook inside-out, so that instead of custom applications running on a platform in a walled garden, applications run on the internet, out in the open, and people can tie their social network into it if they want, with privacy controls, access levels, and alter-egos galore.

Dave Winer agrees it is time to do this:

Eventually, soon I think, we'll see an explosive unbundling of the services that make up social networks. What was centralized in the form of Facebook, Linked-in, even YouTube, is going to blow up and reconstitute itself.

The thing is , pace Andreesson, we have been working on building a consensus to express these connections in an open way for a few years now. We already have a way to express social networks and personal information online. We have hCard for expressing contact information and authorship, and we have XFN to express social connection. Twitter, Dave's experimental platform, already supports this. Lets continue to spread it further.

Even Steve Jobs can't ignore the web

When Jobs introduced the iPhone, it was clear that the platform they could not afford to ignore was web developers - however closed the platform was, having a crippled web browser was not an option. Jobs confirmed that today by saying that the SDK for iPhone applications was Web 2.0 Internet standardsWeb 2.0 + Ajax. Jobs also announced Safari 3 for Windows, so Webkit is now a platform that runs on all computers and a lot of phones.

This is another step in the Innovators Dilemma disruption of the PC computing platform by web-based applications, where learning lessons from the web, and reusing others work are important principles.

iPhone's great step back from iChat

I did watch the iPhone Macworld Keynote last week - here's my chapter-list version of the stream so you can skip through it to the bits you find interesting:


(I'd do the same for the download except 1. Apple obfuscated the url enough that I can't be arsed to packet sniff it out and 2. they still don't have HTTP 1.1 seeking support working right, despite me building and demoing it about 5 years ago).

After watching it, my biggest surprise was how much of a step back it was from the rich interaction that iChat supports. With iChat you get presence info, chat, sending documents and integrated audio-video chat (when the other user's computer and connection supports it). Instead, iPhone had a legacy telco worldview baked in, with calls not conveying any further context (watch the combined demo near the end, where Jobs has to retype Schiller's email when talking to him on the phone). The iPhone has the camera on the wrong side to be a videophone, and Jobs did not mention any ability to make calls over Wifi rather than the Cingular network, or anything about IM (as opposed to SMS).

My hope is that this is just Jobs not mentioning the features that don't demo well yet, but my sidekick's AIM integration is the reason I am so hooked on it; it buffers chats server-side so thatintermittent phone connections on the train don't interrupt conversation flow.