True, I'm talking about two different things. Three, really: mobile flash, desktop browser flash, and the app-packaged flash solutions like AIR. I don't think

True, I'm talking about two different things. Three, really: mobile flash, desktop browser flash, and the app-packaged flash solutions like AIR. I don't think we can really split mobile web flash from desktop web flash, so I think that Adobe is fully aware that browser flash is dead, and I can't see them putting any real resources into the desktop version. Browser flash has, since it was omitted from iOS, limped along under the promise that it was coming to mobile devices "any day now". And every crappy implementation was met with "well you should see it on the next version of [android os|android phone|blackberry]". But that promise is gone, and browser flash is now a dead product with a rapidly shortening shelf life. The reason I think the death of browser flash is also going to kill AIR (Packaged Flash), is because it eliminates the easy entry point that the AIR platforms had. AIR was barely successful only because it took advantage of a huge, huge ecosystem of people writing browser flash. But that ecosystem has hit it's high water mark and is now officially receding: New developers aren't going to go out of their way to learn browser flash, and people aren't going to pick packaged flash over other tools if they don't already have a vested interest in the language and the runtime. It's ok, but it's just not that great, and at the end of the day true "write once, run anywhere" isn't that important (and it's a bit of a myth), and if it is for you, then write a web app.