Web interfaces _are_ AIR interfaces — the graphic resources are identical to what you use in browsers: HTML and SWF. If you think they all suck, and only prefer native-coded interfaces mandated and restricted to a single hardware/OS manufacturer, then that’s your prerogative. But if you “hate” all AIR UIs, then you’re hating all Web UIs too.

So, assuming Web UIs are sometimes acceptable, then we’re at “What’s the user advantage to AIR over webpage?” There are many reasons here, varying by the individual application, but including: increased abilities (notifications, windowing, local storage, cloud synch, desktop drag’n'drop, etc)… dissociation from the performance and security issues of generic cross-site browsers… desktop presence across OS brands (setting as a start-up task, background operations, etc)… application resides locally and is always available, and UI, data and logic do not need to transfer themselves down through the Internet for each use. The new option fills several needs.

1.0 performance was indeed not fully optimized, just as the iPhone has been underpowered — the first generations are more for exploration and validation, later generations polish off the edges.

No need to feel threatened — AIR is an additional choice.

jd/adobe