I hear what you’re saying, but the argument assumes that Apple will hide native API’s from their widget engine. From the keynote, it sorta sounds like they will, but we don’t know that for sure. I entirely expect Apple to offer device-specific API’s via JavaScript, thus solving this thin vs. native issue.

Killer applications can be developed using web technologies, no doubt about. But thin/web clients they are. There are things that just can’t be done using the web model… Access to native is about taking advantage of the handset’s full capabilities, vs. just purely thin clients; and for now only Apple will be creating such apps. As a person who makes a living out of mobile software, I need both, the ability to write killer web apps, as well as killer local apps. There is room for both, and requirements for both. I know know all that…

ceo