Critical Section

clash of the Titans: Apple vs Adobe

Sunday,  04/11/10  09:36 PM

Unless you've been traveling at lightspeed to another galaxy, you must have heard about the great Apple vs Adobe tweetle beetle battle*.  The iDevices (iPhone, iPod Touch, and now the iPad) do not support Flash, and will not support Flash.  Ever.  So Adobe created a Flash-to-native-iDevice converter.  And now Apple have announced iPhone OS 4.0 (in yet another magnificent Stevenote, yes, you must watch it), and the terms of the new developer agreement prevent cross-compiling apps originally written in languages other than Objective C, C, or C++.  Wow.

Sure, we can all see why Apple wants to prevent Flash web apps - that would route around their App Store monopoly - but I can't quite see why Apple wants to prevent native iDevice apps originally written in Flash.  I wonder if this will have the intended effect...

Anyone who is creating apps for iDevices now has two choices, create a native iDevice app, or create a web app using AJAX.  The third way of creating a Flash app which also runs as a native iDevice app seems shut.  Writing an iDevice app means learning Objective C and creating a decent native app from scratch is a pretty big development.  And at the end of the day it would be iDevice-only; you couldn't also run it on Android or WebOS or whatever.  Creating a web app with AJAX means it might not be great – probably less great than a Flash client – but it would run on iDevices, Android, WebOS, or whatever, and might make having a Flash client unnecessary for PCs and Macs too.

This is the problem with Apple’s strategy.   There will be people who take their existing Flash apps and rewrite them as native apps.   That’s what Apple wants.   But there will also be people who just switch to AJAX.   I can’t see why that helps Apple.  Overall the user experience is going to be worse.   Wouldn’t the Flash-to-native-converter approach have been better?

A final point.   Apple reviews all apps before letting them be published in the App Store.   Presumably if an app is super ugly or crappy or buggy or just doesn’t look like it belongs on an iDevice, they won’t approve it.   Since they have that level of control, why do they care about the underlying technology?   If the app was written in Flash (heck, if it was written in COBOL) and cross-compiled, and it looks and behaves like it belongs, who cares?

* from Fox in Socks

About Me

Greatest Hits
Correlation vs. Causality
The Tyranny of Email
Unnatural Selection
Aperio's Mission = Automating Pathology
On Blame
Try, or Try Not
Books and Wine
Emergent Properties
God and Beauty
Moving Mount Fuji The Nest Rock 'n Roll
IQ and Populations
Are You a Bright?
Adding Value
The Joy of Craftsmanship
The Emperor's New Code
Toy Story
The Return of the King
Religion vs IQ
In the Wet
the big day
solving bongard problems
visiting Titan
unintelligent design
the nuclear option
estimating in meatspace
second gear
On the Persistence of Bad Design...
Texas chili cookoff
almost famous design and stochastic debugging
may I take your order?
universal healthcare
triple double
New Yorker covers
Death Rider! (da da dum)
how did I get here (Mt.Whitney)?
the Law of Significance
Holiday Inn
Daniel Jacoby's photographs
the first bird
Gödel Escher Bach: Birthday Cantatatata
Father's Day (in pictures)
your cat for my car
Jobsnotes of note
world population map
no joy in Baker
vote smart
exact nonsense
introducing eyesFinder
to space
where are the desktop apps?