Companies wanting to cover all bases now get to develop 2 times in 2 different coding environments often with different programming talent at around 2X the cost. THAT is the reality of HTML5 vs. Flash now and for a long time into the future. A company that chooses to solely embrace HTML5 now and in the medium-term is choosing to NOT make their media content visible to the bulk of the world. If their customers are not just Apple people (and Chrome and a few others), they have NO CHOICE but to at least include a Flash version too.
Your advice runs counter to what Adobe itself is advocating. Here's John Nack, Adobe's Principal Product Manager
blogging on Adobe's own website. He was talking last fall about Wallaby.
John Nack of Adobe said:
Pre-Adobe, I made my living building rich, Flash-intensive sites for Gucci, Coca-Cola, Nike, and other big brands. Doing that job today, I’d be in a jam: How could I create rich experiences that run on desktops and on iOS devices where Flash isn’t allowed? I’d have to create two versions of a everything–one Flash, and one HTML5. Good luck getting clients to double their budgets, though, and yet they don’t want richness cut in half.
So, the opportunity: Cut the cost of targeting multiple runtimes & we’ll deliver real wins: more richness for clients, and a competitive advantage for customers. [...] Are you surprised? Don’t be. As I’ve written many times, Adobe lives or dies by its ability to help customers solve real problems. That means putting pragmatism ahead of ideology.
People here often post Apple's crushing sales results as proof of the world voting against Flash. I doubt that they are voting against Flash (again see post #27); they are instead voting for all the other great features & benefits that come from embracing iDevices vs. other options.
The sales numbers mean two immediate things. The first is that a Flash-free computing device is just fine for those purchasers. The second is that any website that deploys Flash apps is shutting itself out from a huge segment of the market. There are now over a quarter of a billion iOS devices, and the demographics of the owners of those quarter-billion devices are very attractive. Hobbyists can do what they want, but commercial website developers can't ignore them. Hence you get the Principal Product Manager of Adobe recommending that developers put pragmatism ahead of ideology and deploy exclusively with HTML5.
Personally, I think the iDevices we have would just be more valuable to those that would like to have a Flash player if Apple would allow that OPTION for them. It wouldn't hurt any of the "die Flash die" people as they could choose NOT to install that option just like one user isn't forced to install any other apps another has on their iDevice.
The only problem with an option like that is that people would use it.
I've discussed the accessibility problem extensively in this thread; Jobs also covers it in his
Thoughts on Flash memo. Many people -- including you -- ignore what Jobs notes as the most important problem with Flash. How would you deal with Flash's accessibility problems? How would you deal with the general problem -- the most important problem that Jobs notes -- of enhanced APIs on new computers and new classes of computational devices?
Look at what happened with one simple Flash UI issue: two-fingered scrolling. It took Adobe years to upgrade the Flash runtime to scroll Flash text windows this way (and, BTW, it
still doesn't work the same way that native scrolling does in the browser). Adobe's solution actually required a change in the executable file and re-building of Flash apps. Since many Flash developers don't know, don't care, or have moved on to other clients/projects, many Flash apps will NEVER be rebuilt and redeployed with the scrolling-capability. This one tiny little change broke WORA in Flash.
This is a tiny little nightmare for users. Flash apps are like a box of chocolates: you never know which ones are a bit too ... old ... to scroll correctly. It's probably even worse for users who don't comprehend this level of minutia of the Flash user experience; they just know that scrolling is broken in Flash. With this one tiny enhancement in the framework, Adobe exposed the fragility of the entire Flash ecology.
I suspect the main reason to ban Flash is as many have surmised: business. If Flash-based apps can run on iDevices (too), developers can code it ONCE in Flash and it will run EVERYWHERE. Flash Apps don't have to be sold through the iTunes store; one can argue they are all web apps (so millions of Flash apps won't be able to flow 30% to Apple when they are added to iDevices).
Most Flash apps are free; 30% of $0 is still $0. Adobe has released the tools; Flash apps have been available for over a month. One must wonder: why haven't we seen a "gold rush" of free Flash apps into the App Store?
Etc. Do I think some of what Steve wrote against Flash is what he actually believes? Yes, and I believe it too. But is that the real reason to ban Flash... or is that good PR reasoning? After all, if you post "thoughts on Flash" and offer that it's bad for Apple's profit motives, that's unlikely to be as well received even to those completely under Apple's spell.
I believe that Apple is fanatically interested in a superior user experience. The developed new interfaces for the iPhone and new APIs for code to access those APIs. Then they looked at Flash -- and realized that it was problematic for Adobe's product to ever access those new APIs in an elegant and seamless fashion. The were unwilling to have their user users access the Internet through a lowest-common-denominator approach.
I don't love Flash. Actually, I'd love a better alternative. But between now and when that better alternative is fully in place and universal (runs on as many things as Flash does now), I'd rather we users have the personal option for Flash rather than Apple deciding for us.
That would be a simplistic and seductive approach. But it would do nothing to address the fundamental problem. With its quarter-billion iOS devices, Apple is helping to accelerate the exodus from Flash to HTML5. All users who need accessibility aids on all platforms will benefit from this initiative.
The users on this forum bash flash 24/7 because they agree with everything steve jobs and apple says.
@boonlar: I don't know a single person who agrees with everything that Apple says. I disagree with some of Apple's actions; I think they were completely wrong to not license their MagSafe technology to HyperMac to use with its wonderful external batteries. It wasn't even OK for HyperMac to modify Apple's own cables; they finally had to ship a DIY kit with their batteries and have users modify their own cables.
Can you name a single person participating in this discussion who agrees with everything that Jobs and Apple says? If not, will you please promptly retract your statement?
You miss 99% of videos online because of lack of flash and that's good enough reason not to get an iPad.
That claim is indefensible. AFAICT, 100% of YouTube and Netflix are completely accessible without any Flash whatsoever; those two sites by themselves account for at least 1% of the videos on the internet. It was a number pulled out of ... thin air ... and has no correlation with reality.
Two things:
1. They recommend that sites should only have HTML5 on their websites.
Where?
See the John Nack quote I included earlier in this message.
Eh. I guess since it's graphics and video that make up the bulk of Flash usage, I doubt there is much of a demand for such accessibility features. I mean text I can understand, and it would be up to the web developer ultimately to make sure accessibility is there [...]
You acknowledge that it should be up to a web developer to make sure accessibility is there for text. How exactly does one do that in Flash? Where exactly do you have hooks to access each platform's specific accessibility widgets? You don't!
One thing that has become radiantly clear in these Flash discussions: very few people have actually read Jobs's memo in detail. Very few Flash advocates could name what Jobs identified as the most significant issue with Flash. And Flash developers have no concept of how to comprehensively address accessibility issues in web browsers. Adobe certainly does not.
AFAICT, the only solution is to get rid of Flash in the browser.