Steve Jobs Announces iPhone SDK

An anonymous reader writes "It finally happened. Steve Jobs announced an iPhone SDK today. The plan is to release it in February, and the suggestion is that apps will need to be digitally signed (not unlike digital signing in Leopard). Here's hoping that developing for the iPhone/Touch will be cheap (or free) enough to allow the folks who have been writing apps to continue doing so. Says Jobs: 'It will take until February to release an SDK because we're trying to do two diametrically opposed things at once--provide an advanced and open platform to developers while at the same time protect iPhone users from viruses, malware, privacy attacks, etc. This is no easy task.'"

Comments

Digital signing

[PlatyPaul]

TFS got it wrong: Apple did not in fact say that digital signing was going to be a part of the SDK or making sure that apps are kosher.

Here's the quote that may have misled:

Some companies are already taking action. Nokia, for example, is not allowing any applications to be loaded onto some of their newest phones unless they have a digital signature that can be traced back to a known developer. While this makes such a phone less than totally open, we believe it is a step in the right direction. We are working on an advanced system which will offer developers broad access to natively program the iPhones amazing software platform while at the same time protecting users from malicious programs.

So, what they're really saying is that they're hoping to do something along the same lines as signing, but not signing per se. This actually may be the most interesting part of their announcement, in that it could signal the next step forwards in indicating trust and providing clarity of who worked on what. Here's hoping it's not just repackaging.

Re:Digital signing

[RzUpAnmsCwrds]

Possibly. One of the new features in Leopard is digitally signed apps though, and Apple is setting up some kind of infrastructure so you can verify the signatures. It would seem likely they'll use the same system on the iPhone.

I'm just going to point out that Windows has had digitally-signed apps since (at least) Windows 98, and that nearly every system library and executable in Windows XP and Windows Vista is signed. Vista even checks the signature before you see the UAC dialog, and the dialog for signed apps looks completely different (and has different keyboard shortcuts).

Windows Mobile also has signed apps.

Of course, I'm sure that some Mac fan is going to point out how this is another Apple innovation.

Re:Ipod touch

[BlakeReid]

Will this apply to the ipod touch as well?

Yep - FTA:

P.S.: The SDK will also allow developers to create applications for iPod touch.

Re:Finally!

[n8_f]

No, your post is just wrong and should be moderated as such. Here is Jobs at the D5 conference on May 30th, about a month before the iPhone was even released:

Q: All indications appear that the iPhone is closed, we'd love to develop apps...

This is an important tradeoff between security and openness. We want both. We're working through a way... we'll find a way to let 3rd parties write apps and still preserve security on the iPhone. But until we find that way we can't compromise the security of the phone. I've used 3rd party apps... the more you add, the more your phone crashes. No one's perfect, and we'd sure like our phone not to crash once a day. If you can just be a little more patient with us I think everyone can get what they want.

Re:Finally!

[Sparks23]

As some of the hacker community will readily point out, splitting open Springboard (the Finder/shell equivalent) in the iPhone, you discover Springboard always had some support for additional applications... and going forward, more was added. In 1.1.1, Springboard even added code added that supported multiple pages of applications... a pretty clear indication that either Apple was planning to add a LOT more apps, or were thinking of third-party dev.

There were lots of other little clues people found that the iPhone had either had plans for a third-party SDK which was scuttled, or had a third-party SDK in the works but not yet announced. So I admit, I am with the folks who are saying that Jobs probably had this planned from day one, but held off on the announcements until closer to the SDK/security methods being sorted out for marketing/publicity/spin reasons.

3 months after the phone was released is not a huge waiting period, but if he'd announced ahead of time that the iPhone would have a native SDK in February, lots of folks would have waited both on buying phones and on doing iPhone development. Instead, now we have hackers who have already worked on third-party native apps, there's all kinds of web-apps to keep those who won't jailbreak busy in the meantime.

Love him or hate him, one thing Jobs knows how to do is build anticipation, and manage publicity. He'll take bad press for a while simply so that he can sit on some announcement to greatest spin effect.

Misinformation

[Space cowboy]

Have you actually written any iPhone apps ? Or are you just postulating ?

The iPhone essentially runs a cut and trimmed version of OSX, so getting an SDK for it is NOT some massive undertaking

• The SDK is *not* the same as the Cocoa SDK on Mac OSX. They use UIKit (all the classes start with 'UI' not 'NS'). They use CoreGraphics directly (so you have CGRect structures, not NSRect structures). The port of the Foundation library is incomplete (there's no NSNetService or NSTask that I can find, for example, though basic things (collections, iterators, etc.) are there).

I mean, look, despite Apple's attempts to keep people from using their own phones, random hax0rs got a working SDK up within days

• Those random hackers didn't "get an SDK up in days". They ran classdump on the libraries that *Apple* created, and made the headers available.

A iPhone SDK would use a gcc cross-compiler (since the iPhone isn't running PowerPC or Intel chip -- by the way, gcc makes it easy to build a cross-compiler so this isn't a big deal)

• Interesting. Those "random hackers" got the gcc compiler to cross-compile. Oh, but you can't have any methods that return a float (*) like, er, just about every UI class since co-ords are floats in UIKit. Oh, and it can crash with internal errors in cc1. And they're onto the third incarnation of the compiler now. Perhaps it's not so easy after all. The ARM chip is an established supported target for gcc, so building a cross-compiler itself is relatively trivial. Writing the bootstrap code is presumably harder, and writing the support libraries (libarmfp for example) needs to be done as well.

Not a massive undertaking at all.

• And here's where you lose all credibility. Not a massive undertaking to write a new 2D-accelerated UI framework from scratch, trying to be as compatible as possible with the 'Mac' way of doing things while incorporating a completely new input method ? On a new hardware platform for the OS ? With a very aggressive release schedule ? And design it so there will be no frequent (ahem) updates in the future ?
  
  No, that's trivial mate. Tell you what, we'll do you two, in case one breaks - have it to you next Tuesday... Not.
  

Writing whatever they needed for the initial (general public who don't give the shake of a rat's tail about the SDK) release, then writing/polishing a general developer release is so obviously the way to go, I can't believe people are still talking about it. And if you expected 'The Steve' to lay out all his plans ahead of time, you've obviously been in a coma for the last decade. Welcome to the new century.

Simon.

(*) I think this is actually resolved in version-3 of the compiler. I'm still stuck with v2 because I can't get the LLVM part to compiler on my mac for some reason.