It's something more fundamental. When writing software for mobile devices, you really need to optimize for power consumption. There was a recent talk at Google IO about the new polling vs pushing for web services, and it's alarming. If your Android app polls a web service every 5 minutes, it'll use something like 10% of the battery in one day (just that one app!).

Flash apps are simply not designed for optimal power consumption. Flash is designed for multimedia apps, which are generally power hogs.

I develop Flash professionally, and I'd never run it on my phone.

There is an option to set Flash to "on demand" mode on mobile devices.

There is so much flash content out there on the web, and being able to play flash content on-the-move, on-demand is obviously a good thing.

Well you should open your mind a little, because it's currently the only way to get video on most sites. You can turn it off for sites where you don't need it.

Do you run games on your phone? Aren't those multimedia apps as well? But they're ok and Flash is not? Why is choice a problem here?

I'm mostly worried about Flash in the context of network usage. I can't say how the power performance is for graphics and gaming, but I'd guess it's about the same as native phone apps.

It's easy to imagine flash apps with network access patterns that aren't optimized for phones. Take any advertisement or analytics system which continually polls the server for more data. This will kill your battery if left running.

"Take any advertisement or analytics system which continually polls the server for more data. This will kill your battery if left running."

How does this compare to some AJAX + a timer? Is it the network call itself that's an issue, or just how that is implemented in Flash?