This is an extended reply to a question:

I was shocked to see the following listed as a negative against the
Playbook: ‘Supports Flash’.


Does Flash deserve the criticism it’s getting at the moment and what can Adobe
do to rectify the situation?

In order to reply, I’m going to include a short biased history for some context.

Many moons ago, Adobe kicked up a large fuss when they saw that they were unable to exploit a particularly lucrative1 new platform (iOS/iPhone/iJobs), leading them to trade lies and half truths around user freedoms in both blogs and the mainstream press. This provoked an uproar which, unfortunately for Adobe, caused many people to start looking at Flash and critically evaluate Adobe’s closed tools and platform against the native tools (closed and open) and other alternatives.

The fallout is ongoing, as can be seen from the article Christopher mentions.

The people who are most likely to be aware of Flash on a platform, I think, are also those likely to be more technically au fait with the ins and outs of development, or at least techy geek types. Neither class of people are particularly renowned for enjoying bloated middleware, and that’s led to (at times unfairly harsh) criticism of Flash and it’s uses on phones, tablets, netbooks and so forth.

That will all blow over - most people don’t care how many layers there are between the thing they are looking at on screen and the instructions running on a CPU. They want the pretty colours or simulated flatulence generator buttons.

Unfortunately for Adobe, Flash content is often noticeably worse on highly portable devices. Users do notice that. Degrading someone’s expected experience is a cardinal sin, and a sin that is hard to forget. A couple of those and you are consigned to the “this is shit and doesn’t work” bin from which it can take years to escape. Ask Javascript: it’s had over a decade in that wilderness, and is only now being welcomed home.

Adobe has exacerbated the situation by breathlessly exclaiming to users (and sometimes to developers/designers) that you’ll have a desktop Flash experience everywhere. But then users see the jerky scrolling on pages laden with adverts, their battery life vanishing, bothersome control mechanisms, or games that don’t have any of the 3D slickness of a natively developed application.

At that point it’s partly the developer’s fault - but consumers see Flash as the issue, because that’s the brand which has been sold to them. Adobe looks, to them, as if they are another company peddling the usual lies (“yes, this version of the OS will run faster than ever before!”).

So, that covers my answer to the first question - in many cases the criticism is justified. Caught out by their own mis-truths.

How do they fix it? My answer to that one is: stop lying. Admit where the strengths and weaknesses are to everyone. Stop being so seemingly emotionally attached to Flash as a hammer for every solution. Although I’m sure you’ll see that emotional attachment flip as soon as they have a viable, and priced, alternative for generating HTML versions of Flash content.

Open source the Flash player - allow developers to improve your codebase, allow them to take what they want from it and remould it into something wonderful. Hell, let someone take the vector engine and add the good parts to the SVG spec and add the nice bitmap manipulations to the HTML 5 canvas spec. Make it a permissive licence like MIT.

Sadly, I feel its too late for that. There’s a momentum behind the changes coming for HTML - nothing like a good old implementation war to drive the fires of innovation. That’s something that Flash in its current form cannot have. The rate of useful additions to HTML has been astounding recently - far faster than the additions to Flash. Flash is being tweaked, HTML is innovating and adding new developer demanded features. For architecting a product, open source can be nothing short of miraculous. Flash is mired in its closed legacy.

tl;dr: Yes the criticism is justified, open source the player to attempt to fix it.

  1. Adobe’s true concerns were over the indirect revenues they stood to lose if people no longer used their Flash development tools for content on iOS, whether that was as an application or as content served in a web page. For comparison, how many set top boxes have Adobe lambasted for not allowing their player on the platform? How about XBox 360 applications? Televisions? LG phones? Samsung phones without Symbian? Adobe want to make money. It’s what companies do. Most of them aren’t silly enough to claim that their real intentions are selfless desires for user freedom. That sort of argument is generally reserved for misuse by governments, often while they’re shooting at you. It’s for your own good you see, now just put that stone down and let nice Mr. Tank through.

    I digress somewhat…