Remember, AT&T made some MAJOR changes to their network to accomodate this new phone. They have as much to lose in this investment as Apple does if it fails. So to limit the number of things that could go wrong at launch (eg lock out developers) would seem likt a natural result.

I know I probably live in la-la land, but I think it's in Apple's interest to listen carefully to it's developer base. But then I also happen to think Free Software is the way forward.

"Quit whining."

I also think that lively discussion is important. Apple gets feedback this way. These comments are legitimate in my opinion. I for one would rather not have someone implying that they're irrelevant.

i made a little badge just for those iphone apps...

http://blog.zydev.info/2007/06/16/ready-for-iphone-the-badge/

remember the 'Made for iPod' badge? mocking apple w/apple.

I was just picking up on your very valid "it ain't what you say, it's the way that you say it" point.

I understand that it's the "marketing schlep" that some developers have taken to heart. Gruber makes some valid comments.

But my! Aren't Apple developers a touchy bunch! I think the real complaint I have is that there was no realistic, competent expectation of an SDK being released. However, those nutjobs who DID feel that they were somehow divinely entitled to one (and would want whatever crapfest documentation came along with it), are now jumping on this, foaming at the mouth, and generally drowning out just about any other discussions.

We all know the reasons why there *isn't* an SDK, and Jobs's ill-judged attempt to put "lipstick on the pig" (cf Macalope) by reaffirming the browser's "first class" status has rubbed some people up the wrong way. However, I'm getting mighty sick of all the shit-flinging going on among the chimps here, and I look forward to when everyone's calmed down and got on with their lives.

If it's in Apple's interest to release an SDK, they will. If not, they won't.

And if anyone's been stupid enough to bet life savings on the hope that they will, then that's your problem. Quit whining.

There is no, I repeat, ZERO access to any data on the phone.

There is no local persistent store outside of cookies.

There is no Flash, so you can't even use that to do an "end run" around lack of persistent store.

There is no *outbound file transmission*...you want a picture off the phone, you need to use email. No AJAX uploading.

And as yet another steve said...there is no indication *whatsoever*...not a single hint, that this will change.

The i"Phone" is essentially a widescreen NAND Flash-based iPod...the greatest of its kind, no doubt, that happens to have phone and web browsing.

That was the MWSF takeaway, and the confirmation was delivered at WWDC. As Steve Jobs said in January:

"An iPod...a Phone...an Internet device...An iPod...a Phone...an Internet device...An iPod...a Phone...an Internet device...are you guys getting this yet?"

Well...

Are ya'? ;)

There are a lot of downsides to providing an SDK: security, deciding what to expose and having to maintain compatibility with it, support developers, etc. Balanced against that, it would make it a platform... and platforms lead to unexpected innovations.

Is there anything to the SDK-in-the-future idea other than wishful thinking?

@ addicted

Yes, I know there's a lot more to WWDC than the keynote. I was just commenting on the appropriateness of the message to the audience. But, frankly, Gruber put it much better.