Bitchin’ on the iPhone

Many people are complaining about the SDK for iPhone, or the “insulting” lack thereof. I’m sure some others will have opinions on this for years to come, however I’d like to point out that some of the functionality of the iPhone hasn’t been clearly described for all the programmers and developers out there.

But I have a guess, and it leads to a functional problem of how the phone works and what has to be happening in the background.

First off, let’s all agree that the core apps of the iphone, which would be the 11 apps shown as icons on the front, are running all the time, every time the phone is running. After all, the time it takes to load Address Book, or Google Maps, or Safari on the desktop version of the Mac OS would be beyond annoying on the iPhone. So already the functionality is booted and just waiting to be called up by pressing one of the Top 11 App buttons.

And if you’re in one of those apps, to get back to the main screen, you press The One Physical Button on the iPhone and it takes you back to the main screen. Or does it?

What if TOPB is actually taking you to the iPhone Mac OS Dashboard? And then, what if those “buttons” that we see are actually just Alias’-as-Widgets to get to the basic functionality?

It seems reasonable to me. After viewing the demos (over and over) and the commercials (over and over) it suddenly hit me (while driving) that TOPB created a visual suspiciously like F12 does by default in Mac OS 10.4 Tiger. How could so many others have missed this? And why does it matter?

With this scenario, it’s possible that Webkit, if not the full Safari, is running and being used to render many things for all the apps. GoogleMaps is supported already by Webkit’s rendering, so why not reuse it? And we know that Dashboard widgets also use Webkit. If the home-screen of the iPhone is really just another form of the Dashboard, as the use of one button to activate it implies, Webkit probably handles it.

And didn’t Apple release a devkit for Dashboard? Huh.