Wallaby: Adobe sneaks Flash onto the iPhone
Posted on 30 Jun 2011 at 15:47
Tom Arah argues that Adobe has done the best it can under the circumstances with Wallaby, its Flash-to-HTML5 converter
Recently, I’ve been making the case on the PC Pro blogs that Apple’s anti-competitive ban on Flash has stopped rich cross-platform development in its tracks.
As such, I was intrigued by a video I came across recently asking: “Has Adobe figured out how to get Flash to play on your iPhone?”
First, it’s important to stress that the obvious and by far the best way to get Flash content to play on your iPhone/iPad remains far off.
Try to convert a typical sample FLA and you’ll see that the unsupported features certainly aren’t insignificant
Although it would love to, Adobe hasn’t been able to announce the launch of a Flash player for Apple’s iOS-based devices to match its Android player.
There’s no question that Apple’s hardware could support it, but for reasons that I covered recently – money, and with no competition – Steve Jobs won’t allow it.
So is this a bridge from the old days of Flash and player-based development to the promised land of HTML5 and truly rich browser-based development? If anything, it looks more interesting.
After all, when Steve Jobs announced that iOS wouldn’t be supporting Flash, the case he made against it was that Flash was no longer necessary and that it should be replaced by HTML5 (a blanket term covering all the W3C standards such as CSS, DOM, SVG and so on).
The sign-off line to his thoughts on Flash was: “Perhaps Adobe should focus more on creating great HTML5 tools for the future, and less on criticising Apple for leaving the past behind.”
At first sight it looks like Adobe has done just that and that Steve Jobs has won the argument. After all, if you can deliver Flash functionality in the browser via HTML5, why shouldn’t you? Especially now, when there’s one overwhelming reason you need to: if you want to access the full web audience, including the crucial iPhone/iPad demographic walled up in Steve Jobs’ closed kingdom, there simply is no alternative. The browser is the only way to go.
I’m sure this is exactly how it will be seen and presented by many: “don’t worry that the iPad doesn’t support Flash, you just don’t need it nowadays, everyone’s agreed that it’s much better to do it in the browser rather than the player – in fact, even Adobe has given up on it now and has built its own Flash-to-HTML5 converter”.
Any such talk is misguided, misleading and dangerous. To understand why, you need to dig deeper and see what Flash-to-HTML5 conversion involves in practice.
In fact, you don’t need to dig far before a different picture emerges. Read the introduction to Wallaby and it’s clear that Flash-to-HTML5 conversion isn’t simple.
This initial version has several unsupported features due to the complexity of FLA files and the inability to represent some Flash Professional features in HTML5.
The major ones include no conversion of ActionScript, Movies or Sound, and some design elements such as Filters aren’t supported. For a detailed list of supported and unsupported features.
Try to convert a typical sample FLA and you’ll see that the unsupported features certainly aren’t insignificant. My first “successful conversion” came back with 291 warnings.
Many of these limitations are important, particularly when it comes to text – line-break differences, glyph spacing/positioning, no support for links, selectable or vertical text, and so on.
It's about controlling the platform..
It goes without saying that Steve Jobs wants to kill flash.
Sure, money is 1 reason.. Performance another, battery life and the fact that they're not touch interface & resolution optimised and even past history being a few more..
But on a more fundamental level, Steve Jobs simply doesn't want to be enslaved by a third-party company's proprietary platform. As ubiquitous as flash is, it is not by any stretch of the imagination 'open'.
HTML/Flash/Silverlight? None of the above. As rich as these development platforms are, these intermediary compilers will always be inferior to native platform development.
These idealistic notions of 'universal access' & cross-plaform development sound wonderful but haven't we been down that road before? (Java anyone?)
The reality is that the best user experiences are only achieved when you hunker down and develop to the native platforms specifications, specifically tailoring your app to that particular platform's strengths.
By ihsan on 1 Jul 2011
I appreciate many of the advantages offered by Mac's excellent range of products, but I do not buy any of them for the reasons stated in the article!
By Gorojore on 3 Jul 2011
The hardware doesn't support it.
"There’s no question that Apple’s hardware could support it"
I would question that... I have yet to see an android device—Most of which are more powerful than the 3gs, and some more than the 4—Which really support it in the real world.
Forgetting the hardware restrictions, which are numerous... It's slow, eat's battery like almost nothing else, and is quite intrusive on all phones i've tried it on... The fact remains that Adobe has done very little to make Flash truly touch-screen compatible.
If I am being forced to re-write my site to support touch-based interfaces, then there is no reason not to move away from flash altogether.
I think Wallaby is a step in the right direction, HTML 5 needs a solid GUI development environment, and there is no need to reinvent the wheel if Flash CS5 can output HTML5, then why not use it, but I just don't think flash player really works in a touch environment, with the possible exception of the playbook, which, in my opinion, relies altogether too heavily on Adobe right now, and is liable to suffer for it, in terms of future app development and innovation, if they don't get a more native SDK out soon.
By LukeHB on 4 Jul 2011
Please Leave Me Alone
Please, for the love of God, keep Flash off of my iOS devices.
Take a deep breath. Either give up on Flash or give up on iOS. Either one, I don't care.
By Felix on 5 Jul 2011
- How to sell more ebooks on Amazon
- 10 ways to make your business more secure
- Top five VoIP mistakes
- How to add in-app purchasing to an iPhone, Android or Windows app
- Remote-control ransomware: TeamViewer and software hardball
- Why laptops with serial ports matter to the Internet of Things
- Make your mobile battery last longer
- Small steps into handling Big Data
- Nexus 5: does it really run stock Android?
- How to get broadband to a garden office
- 20 years of PC Pro: our best covers
- Why we've closed the PC Pro forums
- How to turn off Google Location Tracking
- 20 years of PC Pro: our greatest review mistakes
- 20 years of PC Pro: our first A-List
- Wikipedia's "right to be forgotten" protest hits the wrong note
- 3D printing hits the high street for plastic selfies
- 20 years of PC Pro: What amazed us in our first issue
- How Google Glass ruined my lunch hour
- Smartphone battery packs: can a USB power pack beat the festival battery blues?
- Microsoft refuses to hand over customer emails
- Microsoft yanks Windows 8.1 update after crash reports
- Microsoft backtracks on blocking out-of-date Java
- Gartner: time to start planning your Windows 7 upgrade
- Still on IE8? You've got 18 months to upgrade
- Who's buying Chromebooks? American schools
- Microsoft targets Windows in next Patch Tuesday
- Microsoft to block old ActiveX controls in security push
- Samsung and Apple call off all legal disputes, except in the US
- Microsoft ordered to hand over European data