The Absolute Last Thing I'm Going To Say About the iPhone

...this week.

No. I'm not buying one on Friday.

I'm not buying one because there are only 20 phones per Apple or AT&T store. There will most likely be far more than 20 people to buy it here in New York.

I'm not buying one until I have some quality time with one in an Apple store with one. I want to see if, you know, I like it.

I'm not buying one until a few weeks have passed for any manufacturing glitches to work themselves out.

Right now, there are no iPhones. There is only hype versus FUD. Its not a great criteria to base a $500 to $600 purchase on. I have a feeling I'll really like it (or I'll like it better than my current phone, which sucks) but I just don't know yet.

So there.

iWebMusicPhoneThang

I can't resist. My take on Steve Jobs' keynote at WWDC yesterday.

iPhone Development is Web Development

So Steve says: "Want to write apps for the iPhone? Make them AJAX-enabled web apps. They'll execute in the safari runtime, and we'll give you some extra APIs so you can do stuff like make the phone call someone." This is a pretty bold move, and to me it illustrates the following points:

• AJAX is ready for prime time for many apps. Well, when Google released Google Docs and Spreadsheets we knew the gig was up. You can just approach a web app like a desktop GUI app if you want, and there are more and more toolkits to allow you to do it if you wish. Additionally, with Flash you can pretty much take care of whatever you can't do with AJAX and DHTML.


• Safari is the sandbox. Way back in the Web 1.0 days, we had Java applets, and we liked them. Actually we hated them. But they did have a good security model baked in: they could only operate in side a secure "sandbox" where they had limited access to the resources of the system, preventing the viral spread of malware that was propagated by certain Redmond-based software companies. Sandboxing the apps into Safari is actually a pretty good security decision for an environment of transmitted apps on mobile networks.


• You already know how to program for this. Making iPhone development JavaScript, HTML and otherwise web-based means tapping into a huge existing pool of talent, with little learning curve.

Safari is iTunes

Safari is to the iPhone as iTunes is to the iPod. That's why its now available to Windows. All Apple software is marketed with the intention of adding value to their hardware platforms (where they make their real money). iTunes is available on both Mac and Windows not to add value to Windows, but because its real platform is the iPod. In this case - the platform for Safari isn't so much Mac or Windows, its the iPhone. Let me say that again: Safari is the iPhone runtime.

Dashboard Widgets are Also Web Development. On Safari.

But wait, the real platform isn't exactly Safari, its WebKit, the engine underneath. When someone makes an OS X Dashboard widget - its using JavaScript, CSS and running on the same WebKit runtime that powers Safari. Why, its web development! But here they've added a few extra APIs for you to access.

I think this is a good indication of where Apple is headed for network-device development. They are basically saying that Safari/WebKit is the network runtime, and that they will extend that to expose the capabilities of the individual devices. They will have "gateway" software like iTunes and Safari which will run on whatever personal computer OS is handy, and that will provide added value to the real hardware platforms: the iPhone and the iPod.