Wednesday, October 17, 2007

iPhone SDK coming in February

About time. I do wonder if this was planned from the beginning. Did Steve Jobs want to do this or was he forced by the unlocking of the iPhone?

From [Scripting News]
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. Some claim that viruses and malware are not a problem on mobile phones—this is simply not true. There have been serious viruses on other mobile phones already, including some that silently spread from phone to phone over the cell network. As our phones become more powerful, these malicious programs will become more dangerous. And since the iPhone is the most advanced phone ever, it will be a highly visible target. Permalink to this paragraph
How open will the process be? [Engadget]
Less excitingly, Apple claims that it agrees with Nokia's approach of "digital signatures" for applications, meaning that Apple gets to say who qualifies for entrance onto its hallowed devices as was rumored last week; though who's to say what exactly that will look like just yet. But even with that caveat, we suppose we should take what we get from this sometimes benevolent, but never aesthetically challenged, dictator of ours and eat it like we're told.
What happened to the "web as SDK" that Steve Jobs talked about? [Did the web fail the iPhone?]

Flipped around, as a proponent of the web, even I can admit how unexciting standard interfaces on the web are. And how much work and knowledge it requires to compete with the likes of Adobe’s AIR and Microsoft’s SilverLight. I mean, us non-proprietary web-types rejoice when Safari gets support for CSS-based rounded corners and the ability to use non-standard typefaces. SRSLY? The latter feature was specified in 1998! What took so long?!

No wonder native app developers aren’t crazy about web development for the iPhone. Why should they be? At least considering where we’re at today, there’s a lot to despise about modern web design and to despair about how little things have improved in the last 10 years.

And yet, there’s a lot to love too, but not the kind of stuff that makes iPhone developers want to abandon what’s familiar, comfortable, safe, accessible and hell, sexy.

No comments:

Post a Comment