Flash For Froyo!
In May, 2010 we published this blog;
In an interview with the New York Times, Google’s Vice President Andy Rubin tells the world that Adobe’s Flash will be supported on the Android Operating System 2.2 or Froyo (Frozen Yogurt) as it is usually referred to.
When asked about Apple’s decision to not allow flash development for the iPhone, Andy compares Apple to North Korea, due to the removal of choice. “When they can’t have something, people do care. Look at the way politics work. I just don’t want to live in North Korea.”
The whole thing started after Apple updated its iPhone developer program license. The updated version included this paragraph:
“3.3.1 – Applications may only use Documented APIs in the manner prescribed by Apple and must not use or call any private APIs. Applications must be originally written in Objective-C, C, C++, or JavaScript as executed by the iPhone OS WebKit engine, and only code written in C, C++, and Objective-C may compile and directly link against the Documented APIs (e.g., Applications that link to Documented APIs through an intermediary translation or compatibility layer or tool are prohibited).”
The definition of stupidity is: doing the same thing twice, expecting different results. There must be some reason that even though, Macs have better graphics, better nano-technology, and less bugs, they still lose in the market to PCs. Hmm. Could it be Price or Compatibility?
Andy Rubin also said: “Open is open and we live by our own implementations.” This should be Google’s new slogan! Truer words have never been spoken! In the end, Andy Rubin feels that it is only a matter of time before Android sales exceeds iPhone sales, and with an all encompassing, universal Google-rich, open source solution that includes Flash (which is already widely used), it may seem, that the world is about to see the “Rise of the Droid” era, while iPhone may get ironically shut out, just like they have done to Adobe.
Now just over a year later the “Droids” are everywhere, have things changed in one year?
Do you think that Apple is making the same mistake twice? I look forward to your thoughts…