As part of the commentary on Jamie Zawinski leaving the Palm Pre for the iPhone (linked in the previous post), Daring Fireball adds:

Apple had a similar idea to WebOS for the iPhone, where certain apps would run as Dashboard-style widgets, written in HTML, CSS, and JavaScript. Apple abandoned the idea in the six months between the iPhone’s January 2007 announcement and when it went on sale at the end of June, concluding that performance for such apps was unacceptable and that they should go native Cocoa across the board. And Apple was only going to do it for small apps, like Weather, Stocks, and Calculator, not the flagship apps like Calendar and Mail.

Of course, web technologies have improved since 2007, especially JavaScript rendering. Usability and performance complaints aside, Palm embracing web developers in order to incentivize adoption of their platform was a smart strategy. Still, it's interesting to see Apple's reaction to it back then, and their decision to go 100% native. (Especially considering they're now being criticized for not having widgets).

Did Apple make the right choice, do we still want widgets on the iPhone, or is HTML5 and SQLite ?