This is amazing if it actually works.  No more remote control.  My life will love me, the price of a Xbox is worth it just for that alone.  This is the TV future I have been patiently waiting for.

The big surprise here is that this is not Apple.  The Apple-Media-Club (Gets a lot of clicks to fanboy apple) have always been waiting for this in Apple announcements.   They have been predicting it for years.  So the fact Microsoft has in some ways overtaken Apple here would be a little shocking to them, (But not surprising to me).  And really, if Microsoft can make the best game console into such a usable platform in my living room, and I can easily justify it to the wife.  Wow, this is a winner indeed.

The interesting point here is how fast can apple respond or will they even bother.  Will Apple just keep pushing the AppleTV cheap small unit out as is.  Or may be, in an upgrade/new unit, get voice (new iPhone 4S-Suri) control?  But not motion control, you would need to much CPU I imagine.

Still, could we ever see Apple allowing an iOS tool to control an Xbox like an AppleTV.  This is the question.  Apple tends to only allow Apple technology to work with Apple technology.  This is the one MAJOR failure with Apple.  Yes this has given them an advantage in the early evolution of this technology, but as it become more pervasive, will this be the cause of mass abandoning of Apple closed technology?

Will apple open up?  Especially now the Steve Jobs era is over?

I have been waiting for this “Change over period” for a long time.  I am just happy it seems to be upon us.

TV 2.0 here we come.

The current war cry of the blogger based movement is, HTML5 or native code.  To a long tooth coder like myself, both are unrealistic and if anything, based on propaganda by large companies with hidden agendas.

The objective for a programmer is to build a solution using the best tool for the job.  To build a solution that is cost effective and works within the capabilities of the client.  For example, budget, time frame, future proof etc.  HTML5 and native code are exactly NOT this.  For the programmer, this type of development may be interesting and fun, but for the client, these technologies do not supply these results.

HTML5 is, when looked at objectively from a management perspective, is most lkely the worst programming language combination of tools ever invented.  It utilizes about 5 different technologes all trying to run together, pushed by “commitees” with aifferent agendas and finally, implemented by a plethora of comapnies trying to better each other.

Native code does produce better results on slower platforms, but also locks you into those platforms.  It feels like the PC/MAC wars all over again.

The ironic issue here is that once HTML5 does mature enough, it will be used for the same annoying content Flash is used for today, however, once integrated into the base HTML code, it wll be impossible to remove ads and other annoying portions of a web page.  Has anyone ever considered that this is EXACTLY what Google wants as it make it impossible to block premium content ads?

If we look at Adobe Flash as an example, there are reasons why it became as popular as it did.  The core reason is that it was truly cross platform.  Produced results closer to native applications that HTML could not.  Used a few more cycles then native code but worked everywhere.  Was far easier to develop for.  It was everywhere because it was simply enough for any coder to master.

The push into HTML5 and native apps only helps the companies we use these technologies with.  In the short term with the imature platforms from Apple, Google, Microsoft, yes following these paths have some short term gains and hype about them, but in the long term, the same old problems programmer have had will start to float to the surface and technologes like Flash will come back like a train.

Be it flash or a new generation of cross platfrom tools, being open or closed.  The current trends are foolish and short sighted.  They only help the large monolithic companies archive dominance through lock in or lock out.

HTML5, locks you out of truly effective apps, native Apps lock you in to the vendor your using.

If anything, I wish the bloggers and media would talk to real programmers, and not the properganda from the larger companies.  But then again, we all need to get paid.

Yesterday, however, I discovered a huge issue with Android.  A fundamental fault in Android that, as a developer, lets all the hot air out of it as a mobile platform.

What is the issue? You may ask.

The problem with Android is that it underlying exposed API’s are not static.  Meaning, each vendor who makes a phone, be it with blackberry type keyboard, slide out keyboard, or any custom input device, have been implementing non-standard API’s.  This has lead to Apps having a moving target in terms of compatibility.  (Ie, its near impossible to make an App that works on most Android phones.) You can spent 2-3 times longer just making the App work on different phones, then writing the app itself.

After learning this, I now understand why Ice Cream Sandwich is such an important release.  And why it slated to be taking so long.

If Google plan to make Android a viable App platform, they need to act as a traffic cop and force all hardware makers to adhere to common API’s across all phones.  Ie, so an App has a fighting chance to work across most phones.

This is a big  turn in direction to make, so much so that they will have to re-think many of the business relationships and models currently happening with Android.  Ie, a Reboot, potentially into a completely new Android world is required if they plan to stay relevant.  Windows Phone really has a chance to leap frog Android here.  Microsoft appear, from what I have heard so far, to have done this right out of the gate.

Currently, I am now leaning towards Apple iOS as it does have this right. I have a love hate relationship with Apple.  I am not a big believer in some of its business practices.  They can be very unethical at times, but they do know how to make an OS eco system for mobile.

HTML5 pitfalls for Apps

The freedome of “View Source” has done the internet well with the “Web 2.0″ look spreading fast.  With no real way to protect your code, others can leverage of your code for their own ends with little effort.  As a web designer, this could be considered a good thing, a good opportunity.  As an applications developer, an end game.

Lets look at the reasons.

Web developers build sites as fast and cheaply as they can.  The HTML code is not considered a key to this as the site in question is only really of value to the person wanting the site make.  The unprotected code is an issues but not a project end game.

As a Application developer, having the code free available is a non-starter.  Imagine if Adobe had to give away the source code to Photoshop (Which cost them 10′s to 100′s of millions of dollars to develop) with every $1000 purchase of Photoshop.  Of course, there would be competative COPIES based but not directly copied of Photoshop on the market in months.  Adobe competitors could knock this code up and with an investment of $100,000 have a product on the self for $200 and 90% of the functionality of Photoshop.  Adobe would be finished.

So where does this leave us?

In real terms, nothing more then simply crappy RIA (Rich Internet pplications) are likely to even materialise under HTML5.  Products that depend on the back end, such as google etc, are likely to be ok as the “investment” is in the back end and not the application itself.

Any REAL application will have to go the way of the “APP” as it is not called.  Ie the “Apps” sold for iPhone and iPad.

As a App developer, HTML5 greatly reduces any possibility of making  money from selling them.  If you cannot protect the code.  Why would you bother.

So, in the end, who benefits? (OR why do they push HTML5)

• Apple, who gets 30% cut of any App sold, and is one of the only platforms that you can put compiled, difficult to reverse engineer applications on.
• Google, who bases its apps on its back end infrastructure which no one else can compete with.

In effect, Apple and Googles adoption of HTML5 is a form of protectionism under the guise of “Look how cool we are supporting open standards”.

HTML5 is a great open standard, but it is not a App sustainable one.  For the small Application developer, HTML5, if the only plaform available, is “VERY BAD NEWS”.

We need more then 1 standard to rule them all.  Flash.Silverlight, Javan DOT.NET.  Apple and Google locking them out for said reasons is disingenuous.

<!–8baa81a822574ee690346393f5fdb152–>

As a developer, it has been with confusion and bewilderment how the media has been swallowing the SPIN from both Apple and to a lesser degree Google.  The battle for the “cross platform development toolset” required by all varieties of mobile devices will hopefully surface from the “SPIN” infested waters.

In this era of web and mobile (And the plethora of devices that represents) a developer aiming for these platforms needs to cover as many platforms as possible, obtaining a reliable and consistent experience  across them all..  And doing it fast and with the least amount of effort.  Effort = Cost.

This is why Flash has become so dominent.  It fullfils many ingredients of this formula. It has archived what producers and consumers want. It has done this largely because it IS proprietory.  Flash has brough us a long way from the static text and picture web of 10 years ago.

Mobile, on the other hand, is an express train with a destination of more eyeballs then we could have imagined.  It has limitations we once battled with but left behind as Computer power and internet speed grew.  But here we are again.  The future of the cross platform Web/Mobile.  Static pages that we slide around with our finger.

Considering the developer needs, the use of cross platform development tools are “the standard” for any large development house doing content production in a large scale.  Economics simply dictates that these techniques must be used to be competative.  The internet is about cheaper faster.  For the time being anyway.

Apple and Steve Jobs on the other hand SPINS it the complete opposite way.  Steve argues that it must be written in custom code specific to the iDevice technology to be acceptable. Dictating to the developer what he can and cannot do. As a developer I would like to stand up and categorically say that this is essentially ”Bullshit” (Using Steves colourful language.)  There is a degree of truth to this but it is for extreme cases such as games. (And in general Games especially use custom $$$ cross compilers usually written in house to archive cross platform implementation.) To any and all developers it is clear that this “postion” Steve takes is one of marketing.  To manipulate the truth as to obtain a percevable advantage.  It has nothing to do with pure intentions.

In general most applications, or specifically applications created with a wide scope of Web and Mobile, can easily be created on cross platform technologies and have a very good user experiance on all.  Its very possible. (But correctly not wanted by those producing these new mobile devices.)

Where to now?  My advice is to start looking at HTML in general and how it can work in with these devices.  And if you have time, play with HTML5, it will become relavent in a few years. For now its a developing standard that keeps moving, something any commercial developer should stay well away from.  Flash, unless something changes, is a political football that neither Apple (Especially Apple as it has produced mountains of lies about Flash and its capabilities) and Google (“Support” it to be “Not Evil” but bog it down in red tape. Java implementation only (Slow as hell), no generic C based versions allowed (Fast as Objective C and much faster then HTML5 currently)).  HTML is your only REAL heterogenious (Cross Platform) solution.  I know, its frustrating.

As a developer myself, I have no time to invest in the Apple Only eco-system. Its far worse then Flash.  Flash actually CAN work on all the platforms and most likely will at some stage as common sense eventually comes to all the AppleFanboy media and bloggers who do not question Steves “Gospel”.  As recent events have shown, Steve manipulates the facts as AntennaGate has shown even to the most die hard AppleFanBoy.  Maybe now they will go back and question many of the other “Letters” Steve has written.

We as developers need to tell Apple/Google what we need to archive our clients wishes, not the other way around.  It is only through a broad understanding of these technologies with their advantages and disadvantages can we make this argument.

In recent days a number of major media evants have happened that voice this same disconetentment.

1. 3rd episode of new return of Futurama makes fun of eyePhone calling eyePhone users Supid bastards and protraying them as zombies under the control of a 1984 type regeme.  Its funny because it rings true. http://www.maclife.com/article/news/why_did_comedy_central_remove_eyephone_reference_futurama_online_clip#comment

2. A spoof of a stupid iPhone4 purchaser. http://www.youtube.com/user/tinywatchproductions#p/a/u/1/FL7yD-0pqZg
This video has gone viral.  Again because the the truth element to it.

It is also starting to get out of hand with Steve’s unrealistic view on Blu-Ray, which to all intensive purposes has, as I have always blogged, taken of and is now a real market force.  This goes in the face of all the “Know It All” bloggers coming out of California. “Blu Ray is dead everything will Stream”.  This one eyed  and unrealistic viewpoints are starting to piss me of.  Where can I get eduated and knowledgable analysis?

Still, Steve still knows better and says no Blu-Ray so if you purchase Apple devices, you have to use his iTunes service..  As he knows better and knows better what you what then you do. Just remember that.

Lets look at possible one of the worst PR issues in Apple history, this Anatena fault in iPhone4.  Yes, Apple F-it up.  And what a MAJOR F-up it is.. Never has there been so many blog posts.  Never has there been so much Apple PR SPIN.  Steve being a dick about “Don;t hold it that way” then the PR department trying to say it was not him.”lie“.  Then the even worse Letter from Steve.

“We got he bar metters wrong.  Its not that bad, all phones do this blah blah..”.  Sorry, but nothing can save this from the Youtube videos showing it is a VERY serious problem.  The phone is simply not useable without a bumper.

Reality.  The phone is F-ed but no way are we going to fix it for free.  We are going to make excuses.  Oh and by the way, we made the iPhone show more bars then it should have to make you think it got better reception then everyone else.  But we will fix that now and use the “Industry standard”.  this will make the problem with the phone not seem so bad.  But your calls will still drop all the time.  But at least it “LOOKS” like we did something.

As you may pick up.  I am very annoyed with all this.  And really, its not so much Apples/Steve fault.  I kind of expect him to do this in his position.  Its the one eyeed approach and billions and billions of free marketing Apple recieves from the media.  Its the blatant lies he has written in his “Letters” that the media takes for granted.  Not bothering to examine the details and therefore the untruths (Or lies) hidden within.

Steve may be a master of PR and Spin, spinning the facts or conveniently making mistakes (lies) to archive his own ends.  But as the media, you are suppose to investigate and understand the details, not simply regurgitating it as it gets clicks (Makes you money).

Lets study the “Thoughts about Flash”

Adobe’s Flash products are 100% proprietary. They are
only available from Adobe, and Adobe has sole
authority as to their future enhancement, pricing,
etc. While Adobe’s Flash products are widely
available, this does not mean they are open, since
they are controlled entirely by Adobe and
available only from Adobe. By almost any definition,
Flash is a closed system.

Let’s get this straight.  Neither Apple iTechnology or Adobe Flash are OPEN.  They both use open and freely available standards. They both use proprietary standards such as H.264.  Steve Jobs claiming that Apple iTechnology is Open is a subjective point.  But let’s look it from another angle.

Free is usually associated with Open.  To use any of Apple’s iTechnology you have to purchase their hardware and be a registered($) developer to run software on them.  For Flash, you can use any computer using any operating system, obtain the Flash player for free, then download the open source compiler.  This is all free and Open, however the Player is closed source. (Or you could use the open source Flash Player called Ganash).

So comparing both, I can use Adobe flash technology and build workable results without paying Adobe a cent. I have access to all the source for the tools that make the swf files. Not so with Apple.  So who is more open again?

Apple has many proprietary products too. Though
the operating system for the iPhone, iPod and iPad
is proprietary, we strongly believe that all standards
pertaining to the web should be open. Rather
than use Flash, Apple has adopted HTML5, CSS and
JavaScript – all open standards.

The issue here is not the openness of the web, but
the tools and costs to get you to this open web.  For
Apple you have to purchase expensive iTenchnology.
For Adobe, you get a free Flash Player.

Apple’s mobile devices all ship with high performance, low power
implementations of these open standards. HTML5,
the new web standard that has been adopted by Apple,
Google and many others, lets web developers
create advanced graphics, typography, animations and
transitions without relying on third party
browser plug-ins (like Flash). HTML5 is completely
open and controlled by a standards committee,
of which Apple is a member.

Has anyone bothered to tell Steve that HTML5 is a “developing standard” and is not slated to be completely ratified until 2012?   HTML5 is by no means a technology we should be putting out there on a large scale yet as the standard is likely to change.   Every time it does, every website using the current Draft and prototype example implementation will have to change their code to suit.  Any web developer pushing hard into this now is being foolish at best. Potential Darwin awards member of the web community at worst.

Second, there’s the “full web”.

The full web, to me, would mean the most common technologies, Open or otherwise. But let’s keep reading..

Adobe has repeatedly said that Apple mobile
devices cannot access “the full web” because 75% of
video on the web is in Flash. What they don’t say is
that almost all this video is also available in a more
modern format, H.264, and viewable on iPhones,
iPods and iPads. YouTube, with an estimated 40% of
the web’s video, shines in an app bundled on all
Apple mobile devices, with the iPad offering perhaps
the best YouTube discovery and viewing experience
ever. Add to this video from Vimeo, Netflix, Facebook,
ABC, CBS, CNN, MSNBC, Fox News, ESPN, NPR, Time,
The New York Times, The Wall Street Journal, Sports
Illustrated, People, National Geographic, and many,
many others. iPhone, iPod and iPad users aren’t
missing much video.

Ok, let’s be specific here.  Flash, way back since Flash Player 9 Update 3, released on December 3, 2007, Flash has been able to play back any standards based MP4 container with H.264 and AAC video, all the way up to HD 1080.  (HD performance subject to Hardware acceleration, ie not on Mac).  Since then, any Video website would have likely switched over to H.264 media files. (Better utilisation of bandwidth  $$$)  Meaning EVERY website would be using them now.  Moving a Flash based Video site to the <video> tag would only take days of development. (No transcoding needed)

Flash has never claimed to be a video container.  It is what has made flash so popular, but that is not its core purpose.  So, cool, Adobe was actually not that bothered, IMHO, about this.   The <Video> tag has its purposes.  But then again Video in flash also has its purposes too.  Both will do some video interfaces better then the other. It depends on the application.  The <video> tag will in general do for 95% of what the web needs.  Adobe has never disputed that.  They have only tried to make it more innovative to keep it as relevant as possible.

Another Adobe claim is that Apple devices
cannot play Flash games. This is true. Fortunately,
there are over 50,000 games and entertainment
titles on the App Store, and many of them are free.
There are more games and entertainment titles
available for iPhone, iPod and iPad than for any
other platform in the world.

This is obviously a comparison between thousands of free flash games and thousands of $ games on the iTechnology platform.  It is a blatant admission by Steve Jobs that Apple would rather you pay for Games from the store and they get 30%.  And really, why the hell not.  Apple made these wonderful iTechnology products.

Steve, please come clean and do not make up false accusations and mislead consumers.  That’s bad form.  This is the core of why this fight is so high profile IMHO.

Third, there’s reliability, security and performance.

This is where it gets good. Steve has a point here, but chooses to leave out a lot of detail.

Symantec recently highlighted Flash for having
one of the worst security records in 2009.
We also know first hand that Flash is the
number one reason Macs crash. We have
been working with Adobe to fix these problems,
but they have persisted for several years now.
We don’t want to reduce the reliability and
security of our iPhones, iPods and iPads by
adding Flash.

Here Apple starts pointing the finger. Yes Adobe has security flaws. But so does your OSX and iTechnologes.  If Apple was so perfect, why can’t they stop the jail breakers?  How come they send out security patches on a regular basis?  Apple is also known for being one of the slackest when it comes to security fixes.

Yes, Flash has had some security issues, but like all complex tools, no more than its fair share.  Apple, you are just as guilty.  Again bad form Steve.

In addition, Flash has not performed well on
mobile devices. We have routinely asked Adobe to
show us Flash performing well on a mobile device,
any mobile device, for a few years now. We have
never seen it. Adobe publicly said that Flash would
ship on a smartphone in early 2009, then the
second half of 2009, then the first half of 2010,
and now they say the second half of 2010. We
think it will eventually ship, but we’re glad we
didn’t hold our breath. Who knows how it will
perform?

Lets look at the facts.  There are over 200 apps on the AppStore known to be made from the FlashCS5 tool set. (Probably more but developers are not willing to say.. for good reason as Steve will probably kick them off)  These Apps passed the TEST to go onto the Apps store.  One would expect the test involves looking at performance issues.  One would expect Steve has likely looked at these apps as there are Blogs and articles all over the Web about them.  So are we supposed to believe that Steve has simply not bothered to have a look at them?  The statement above is obviously misleading.

Fourth, there’s battery life.
To achieve long battery life when playing
video, mobile devices must decode the video
in hardware; decoding it in software uses too
much power. Many of the chips used in modern
mobile devices contain a decoder called
H.264 – an industry standard that is used in
every Blu-ray DVD player and has been adopted
by Apple, Google (YouTube), Vimeo, Netflix and
many other companies.

I recommend you have a look at “HTML5 versus Flash: Animation Benchmarking” (See video explanationComparison of performance of Flash Player 10.1 and HTML 5 on Mobile Devices) in which Flash is 200-500% more efficient then HTML5 running on webkit on an android phone.  Meaning it would use less power then HTML5.  Ie, Steve Jobs’ suggestion that HTML5 has better performance is misleading and obviously not true.

Although Flash has recently added support for
H.264, the video on almost all Flash websites
currently requires an older generation decoder
that is not implemented in mobile chips and
must be run in software. The difference is
striking: on an iPhone, for example, H.264
videos play for up to 10 hours, while videos
decoded in software play for less than 5 hours
before the battery is fully drained.

This is really good spin. Steve is right in that the very OLD version of flash before 2007 (3 years in internet time is a VERY LONG TIME), version 9, did use a CPU based codec.  But as stated above, H.264 is now the standard and all sites using flash are now using the same H.264 files in flash as is compatible with the Hardware accelerated decoders.  As such, Flash 10.1 is as efficient as it can possibly be on these mobile devices.  Steve implies Flash cannot do H.264 Hardware acceleration, which is again deceptive and untrue.

But lets get into the OSX story here.  Apple like to blame Adobe for the poor video performance on OSX.  Unfortunately, again, Steve has failed to supply the full story.  The reason Flash on OSX is so slow and buggy is as follows.

1. Video: Apple has refused to, until recently, supply the API required to implement it.  Flash 10.1 for OSX will have Hardware acceleration as, the API has only just been made available.  Steve conveniently failed to mention this. (See Adobe will accelerate Flash video using new Apple API)

2. General flash animation performance: Again, this is because those APIs available for rendering animated content on a web browser are old and not suitable.  Adobe has been waiting for better and supported APIs to become available.  Again, only recently because of the advent of HTML5 in the browser has Adobe now been able to implement Core Animation for use in Flash Player 10.1  The FlashPlayer development team say OSX flash player is likely to be even more efficient then the Windows version.

Looking at the facts, we can see it is Apple and not Adobe that is responsible for a lot the the problems Steve likes to blame Adobe for.  This, however, does not really make up for the stated CRASH level of Flash on OSX.  I personally have not had a lot of problems.  And this crash issue is likely more to do with authoring issues than the player itself.  Still, it’s an easy mark, and why has Adobe let it become such an issue?  I would say, simply because Apple has shown little interest in helping Adobe make a reliable and efficient Flash Player and as such, Adobe has shown little interest in fixing these issues.  A tool like Flash Player is only as strong as the foundations they sit on.  FlashPlayer OSX sits on the OSX API’s and as such, Apple, by definition and by action is partly responsible.

When websites re-encode their videos using
H.264, they can offer them without using
Flash at all. They play perfectly in browsers
like Apple’s Safari and Google’s Chrome
without any plugins whatsoever, and look
great on iPhones, iPods and iPads.

This sentence is obviously misleading as it’s a non-issue. As mentioned above, Flash Video migrated to H.264 over 3 years ago.

Fifth, there’s Touch.
Flash was designed for PCs using mice, not
for touch screens using fingers. For example,
many Flash websites rely on “rollovers”,
which pop up menus or other elements when
the mouse arrow hovers over a specific spot.
Apple’s revolutionary multi-touch interface
doesn’t use a mouse, and there is no concept
of a rollover. Most Flash websites will need to
be rewritten to support touch-based devices.
If developers need to rewrite their Flash
websites, why not use modern technologies
like HTML5, CSS and JavaScript?

Even if iPhones, iPods and iPads ran Flash, it
would not solve the problem that most Flash
websites need to be rewritten to support
touch-based devices.

This is a very good example of misdirection.  HTML/CSS sites are just as likely to use roll overs as Flash is.  And like HTML and the use of it in the Javascript apps for the iPhone, flash is just as usable in an interface designed in flash.  Flash 10.1 also support multi touch and pinch.

Sixth, the most important reason.
Besides the fact that Flash is closed and
proprietary, has major technical drawbacks,
and doesn’t support touch based devices,
there is an even more important reason we
do not allow Flash on iPhones, iPods and
iPads. We have discussed the downsides of
using Flash to play video and interactive
content from websites, but Adobe also
wants developers to adopt Flash to create
apps that run on our mobile devices.

We know from painful experience that letting
a third party layer of software come between
the platform and the developer ultimately
results in sub-standard apps and hinders the
enhancement and progress of the platform. If
developers grow dependent on third party
development libraries and tools, they can only
take advantage of platform enhancements if
and when the third party chooses to adopt the
new features. We cannot be at the mercy of a
third party deciding if and when they will make
our enhancements available to our developers.

There is some truth to this but, like all tools, you use the right tool for the right job.  If I am writing a Game, best to use the most low level code using the highest possible performance API’s available.  But if writing a simply end user App in that people read, input and view data.  This is completely WRONG.

The performance hit of cross platform tools that build tools for input and viewing of data (Anything but games mostly)  have little performance differences.  They save the developer massive amounts of money.  This is why cross development tools are so popular and expensive.  They are very important development tools that can make the difference between a tool being worth while doing or not.

This is a obvious attempt to lock in the developers and to get them to invest money into the closed Apple platforms.  As the more Apple can get them invested, the more power Apple can bring over them.

As a developer, Steve, you turn my stomach.  But at the same time, if that is where the money is, that is where the developer will go, even if he is selling his soul to make his living.

This becomes even worse if the third party is
supplying a cross platform development tool.
The third party may not adopt enhancements
from one platform unless they are available on
all of their supported platforms. Hence
developers only have access to the lowest
common denominator set of features. Again,
we cannot accept an outcome where developers
are blocked from using our innovations and
enhancements because they are not available on
our competitor’s platforms.

This goes both ways Steve.  But obviously in your mind, Apple is the only company that can “Inovate”.  My stomach turns over again.

Flash is a cross platform development tool. It is
not Adobe’s goal to help developers write the
best iPhone, iPod and iPad apps. It is their goal
to help developers write cross platform apps.
And Adobe has been painfully slow to adopt
enhancements to Apple’s platforms. For
example, although Mac OS X has been shipping
for almost 10 years now, Adobe just adopted it
fully (Cocoa) two weeks ago when they shipped
CS5. Adobe was the last major third party
developer to fully adopt Mac OS X.

“It is their(Adobe)  goal to help developers write cross platform” Yes exactly. As a developer, that is exactly what I want.  HTML5/ Object C, they are all just more languages.  We have so many languages because like having a tools box full of many different tools, Hammer, screw driver, spanner, we use the right tool for the Job.  Imagine a tool box with only a Hammer in it.  That is what Steve is trying to justify here.

Our motivation is simple – we want to provide
the most advanced and innovative platform to
our developers, and we want them to stand
directly on the shoulders of this platform and
create the best apps the world has ever seen.
We want to continually enhance the platform so
developers can create even more amazing,
powerful, fun and useful applications. Everyone
wins – we sell more devices because we have
the best apps, developers reach a wider and
wider audience and customer base, and users
are continually delighted by the best and broadest
selection of apps on any platform.

What a great company statement.  The only problem is that, there is no reason why Flash Player could not be part of that statement apart from the deceptions mentioned above and the business model that places Adobe as a threat.

Conclusions.

Flash was created during the PC era – for PCs and mice.

The C programming language is one of the earliest languages created. Even today it is one of the most common languages in use.  Just because it is old does not make it out dated.  This statement is obviously bate for the general user, not developer type, to relate to.  Like how your older cars are not as good as new ones.  That does not hold water in this case and neither does Steve’s letter.

Flash is a successful business for Adobe,
and we can understand why they want to push it
beyond PCs. But the mobile era is about low
power devices, touch interfaces and open web
standards – all areas where Flash falls short.

That is your opinion Steve. Unfortunately facts appear to indicate Flash will be a very usefull cross platform technology applicable for mobile to browser.

The avalanche of media outlets offering
their content for Apple’s mobile devices
demonstrates that Flash is no longer necessary
to watch video or consume any kind of web
content. And the 200,000 apps on Apple’s App
Store proves that Flash isn’t necessary for tens
of thousands of developers to create graphically
rich applications, including games.

As long as everyone uses the web as Steve has dictated. Yes. Selling Apps in which Apple gets 30% or everything, yes.

Sorry but this is absurd.  The web is about using whatever works for you.  Be it open or closed.

Flash has a right to exist just as Apple has a right to sell locked down iTechnology.  However, Steve does not have the right to deceive and slander another company.  This is where Apple stepped over the line.  Adobe, on the other hand, has tried to follow Steve’s unrealistic laws and write the FlashCS5 Cross compiler. This has been slapped down with anti-competitive practices of changing the ULA for reasons that do not hold water.  This has never been about what Steve says.  Its about business models.  The CEO of Adobe is very right in saying that this is a smoke screen and this letter is nothing but FUD to try and justify anti-competitive behaviour.

New open standards created in the mobile era,
such as HTML5, will win on mobile devices (and
PCs too). Perhaps Adobe should focus more on
creating great HTML5 tools for the future, and
less on criticizing Apple for leaving the past behind.

Again, deception.  Adobe have not criticised Apple.  Adobe employees and specifically Flash evangelists who are most likely working on the Flash to iPhone tools did.  Can you blame them?  They put long hard work into following Steve’s ULA.  Implementing a method of making Flash Technology on the iTechnology platform while keeping to the conditions in the ULA, only for Steve to change the wording just before launch.

HTML5 is only a small part of this.  Steve knowns this but is using it as a magical platform, that for all intensive purposes in not real yet as the standard and implementation are only still in early implementation and subject to change.  Because of this unknown potentaial of HTML5, it is the “Fix All pill” we hope will come along and fix those issues we all dislike about the Web.  The truth is, its not going to be anything like that..  Exactly the opposite in reality.

Why Do We Hate Flash

Flash is the Advertisers big stick they hit us with to make us take notice.  Like everyone, we hate being hit by this big stick.  What we have here is similar to the slogan “Guns don;t kill people, people kill people.” which equates to “Flash does not annoy the web surfer, the advertisers making the Flash content annoy the flash user.”

The issue here is that the Web Surfer cannot see past the ad, so they focus on Flash.

The performance issue is a group effort.  FlashCS4 does not lend itself to optimised programming but for real programmers its not difficult at all.  The Advertisers using flash want active and very eye catching ads jumping around attracting your eye.  This of course kills your battery and annoys the user.  Flash can be programmed to archive better then javascript and HTML5 type performance.  The biggest problem here is that it is not generally commercial for web developers to do this.  And this will be true for HTML5 as well.

Every programming language can be programmer poorly.  Even ObjectiveC, C or C++.  Adobe is guilty for letting this get out of hand.  Actionscript3 has brought this back in line a lot as it is far more programmer centric.  You need to understand the code much more.  You cannot simply cut and past into the time line in AS2.  However, at the same time, this has reduced the number of flash programmers as many AS2 users say it is too hard to use now.  Its a double edged sword.

Performance on OSX does SUCK.  Its Crap.  But as mentioned above, Apple is just as responsible if not more then Adobe.

HTML5 is not what we hope it to be

One of the biggest misconceptions of many Flash haters is that HTML5 will save their battery and stop the crashes.

Unfortunately this is WRONG.  The big issue here is that once HTML5 replaces flash, and as a flash developer, I would expect it to. Those who enjoy the ad free internet by using an Ad Blocker or Flash Blocker..  That will be impossible once HTML5 is adopted.  The browser will not be able to tell the difference between an ad and the website.  Ads will be proxied directly into the application, as if they are part of the website.  The ad-blockers will simply not be able to tell the difference.  This is why Google and now Microsoft (with its announcement to drop flash from IE9) are so into HTML5.  No more blocking the premium animated and most profitable ads.  Its obvious any company who makes money from online ads will want flash to disappear from online ads ASAP.

As the “HTML5 versus Flash: Animation Benchmarking” (See video explanation Comparison of performance of Flash Player 10.1 and HTML 5 on Mobile Devices) indicate, those ads you will no longer be able to block will be running all over your open web pages eating up more battery then Flash 10.1 would.

The HTML5 future everyone is hoping for is exactly the opposite of what it will deliver.

Here comes the DOJ

Considering the level of deception and properganda Apple is generating, the DOJ would have to get involved at some stage.  Apple is being anti-competative while also producing large amount of misleading and false information to the general end users.  This is of course hurting Adobe.  In Australia, if Apple was located here, would be in very deep trouble.  Anti-competative behaviour is illigal no mater if you are a monopoly or not.  In the US, these DOJ investigation, altho on the surface, has no real merrit in US law, the DOJ will be compalled to do some type of investigation.

Apple is being anti-competative.  If this behaviour is seen to effect any area Apple is deemed to monopolise, Apple is likely in trouble.  This being such a complex area with so many subjective views, this is unlikely to go any where.  However, the bigger issue here is   “Steve has been seen deceiving end users.”  Ie lying for his own gain.

This establishes that Steve is deceptive.  Where does this stop.  The end user?  The investor? The government?

The DOJ is compelled to have a closer look now.

Why does Apple want to displace Flash?

Finally we need to look at why Steve is pushing this issue so hard.  They want to displace flash as a dominant platform on the web.  I have seen a number of interesting post looking at very holistic reasons. This one is especially interesting but essentially wrong. “A good problem to have“.

Apple/Steve is very smart.  The one market he has not been able to dominate to the degree you would expect is ONLINE VIDEO. The online video owners, unlike the music industry, are a bit more aware of what Apple is trying to archive.  As a result, they have fragmented the industry as much as possible to ensure no indeviduel company can gain enough control as to start dictating to them the conditions.

Steve is trying to manuvor the online video industry into a position in which they have no option but to sell their soul to Apple.  To do this they have looked at the future trends of video. Producer to consumer.

Producer to consumer with subscription or paid to view will be the future.  However, this future will need a transaction system and a video distribution system.  Currently we have two options.  Apple and Adobe.

Its quite simple. Take out Adobe before its Flash platform really starts to shine in this area.  With hardware playback, better then javascript/HTML5 performance, the best authoring tools on the net, cross platform agnostic (Run on anything from a mobile phone, computer, TV) DRM, for those who want it (And all big content owners WILL) AND.. built in TORRENT technology.

Once Flash materialises this technology coming in 10.1 towards the use of video distribution on the net.  Apple will not be able to catch up..  Its all out WAR now.  Crack and kill the egg before it hatches.

I am very much behind Adobe/Flash on this mainly because Adobe is a tools company.  I will be able to purchase the tools to distribute to my consumers directly. I will control my future.  I will not have to ask Apple/Steve permission to distribute my content through his gateway and toll booth, the iTunes store.

Conclusion

In conclusion, as a developer who likes Flash, to tell the truth, I can respect the business decision by Steve to not allow Flash on their iTechnology platforms for good old competitive reasons.  What is wrong here is that Apple is on a campaign of deception.  They are not happy to not use flash, but are also producing FUD to displace Flash as a relevant web technology.

As a Apple user who may be reading this blog entry (And congratulations if you got this far), consider your relationship with your Apple products.  You have just been told your friend is deceptive and will lie to you to get what he wants from you.  How would this go down if this was your partner or best friend?

Let me finish with a video of Adobe’s CTO Kevin Lynch.  Here is a simple and honest view of where flash fits.  I could not agree more with what Kevin says.

I am simply relieved that the “Amazing new ideas” Steve jobs at Apple was going to bring us in the iPad simply did not materialise.  Now we can get on with the job of recreating the way we consume media.  Sure the iPad will be a sucessful part of it.

The real story here is that Apple, with the iPad hype, has persuaded the Media industry to start embracing these types of new media consumption devices.  Content is king, and even if the iPad is the most elegant of devices for consuming this new form of media, without the content producers behind it..  its worthless.

Talking to my fiends in the Media industry, they note that these large media organisations have all done deals with Apple.  But interestingly enough, the key to these deals is the “Non-exclusivity” aspects of them.  Meaning, if any other [A-Z]Pad devices come out in the near future, those devices will have access to the content just as much as Apple does.

Look at the killer aspect of the “PADS” , we have the immenent demise of news papers and magazines. The “PAD” device will be a must have.  And that’s the deal with the iPad.  It is suppose to be the bridge between the old and the new.

My point here is that the iPad may be the first bridge we build between the old and the new, but it will only be the prototype.  The bridge we get the best bridge makers in the world to build first.  Then we get the companies who make 80% as good for 50% the cost and that goes mass market.

What I am waiting for is the disposiblePAD. $100-$150, does all what iPad does, but a little slower, App store may be not so good.  But really, it supplies the killer aspect of the device.  And it is cheap enough to drop it once a year and not think twice about replacing it.  Apple’s culture simply cannot compete with this type of device.  Apple will be very sucessful just as BMW and Mercades are very sucessful.  However, Apple is not a everybody device.

I think the blogisphere underestimates this issue. Price is everything in that market. Due to the way we will use he PAD, I can see it getting broken and lost very readily.  No one can afford to do this with a $500, cheapest iPad device (And I expect Apple to drop the price much more after the Apple Fan boys have purchased).  I expect a $150 for a nice equivalent, then add subsidized subscriptions to a few content providers, and we are talking equivalent to free device.

I am just happy the Apple hype is over.  There was nothing we didn’t already know.  We can all get on with what we where doing.  Apple hasn’t changed anything.  All they did was confirm what everyone was thinking but had not invested in as yet due to waiting on the Apple magic that did not appear.

1. The hardware spec and prototype was most likely finished quite some time ago.  Obviously they have been refining it continuously as time permits.  However, it is not the hardware that dictates the iTable release.

2. Anyone pushing the “iTable is only rumor etc” is obviously just trying to generate clicks. (Total opposite to general opinion generates traffic) I don’t even look for these leaks but I have heard that it certainly exists.

3. The iTablet success is connected to content.  Apple will not release the iTablet until they have the content in place.  It is far more important then the product itself.  Why buy a TV if you have nothing to feed it, ie Movies/TV shows.  Remember the old days, the Radio makers MADE the Radio shows to drive demand.

4. Apple needs to get the formula right.  The iTablet success is based around replacing the hole left behind by news papers going away and everything going online.  This is all well and good, but the old timers, the general MASS MARKET, (As opposed to the very small and limited tech hype engine that is western US) will only adopt the product in mass if it is seen as a replacement for what they know and love now.  Ie picking up the news paper in the morning and reading it while you eat breakfast.  This is a key issue that combines the functionality of the iTablet and the media deals.  For the iTablet to be as successful as everyone is hoping it will be, it need to exist in its own right.  Not an iPhone replacement, not a Ultra light PC/MacPro replacement.  A product in that “it” is the best product for the purpose.

5. The magic  you get when this product come along, interactive magazines, video communication, (Twitter, facebook integration etc) is what  makes this product worth all the hype. It is what the excitement is really about. All that BLUE SKY..  the potential.

The more interesting aspect of all this is the wave of change in the printing industry this will bring.  Unlike Music in which Apple found itself in a very dominant position and sacrificed the artist for its dominance in portable music players, no other industry has been willing to let Apple do this again.  The AppleTV, for example, is been a failed project as the media providers are not willing to let Apple gain a postion of dominance.  They are making sure other companies and paths to market exist. As Apple has not seen a path to dominance, they have not spent much time on AppleTV.

So, how is Apple doing these deals with Print Media is the bigger question.  From what I hear, Apple are doing very reasonable deals.  I expect they understand they cannot get away with what they did with music.  Print media suppliers are not going to back themselves into corners like the Music industry did.  They are likely to make open ended deals in that other hardware makers will easily join in on. (For example, at half the cost of an iTablet) This means Apple is not as likely to be able to dominate the market with the iTablet.

However, I think Apple masterful plan as to use the “accidental” success of the App store with its lock in APPS (Ie not cross platform, only run on Apple) as a form of obtaining dominance.  Apple will be open with its media suppliers, but will lock in the users by locking them to APPLE only applications.

The iTablet will obviously have a App Store, and countless Apps will appear over night.  Users will find themselves investing another few hundread dollars in Apps before they know it.  If your iTablet breaks, or the battery dies (And most likely cannot be replaced) what are you going to buy, a new white box Tablet at 1/2 the cost and loose access to your APPS, or just get another iTablet?

This explains why the open and cross platform technology from Adobe (Flash Development platform) and Microsoft (Silverlight) , are being poisoned as much as possible by the Apple hype engine.

In any case, we are all likely to want one, I just hope th contract I sign to get it, does not include small print that means Steve owns my Soul as well as my wallet.

So what is going on.  Development tools are expensive to develop. Why are they been given away now?

As the use of computers, PDA’s, Mobile phones has increased, the more important factor for these products has not been selling the tools or programs used on them but to simply own a decent portion of the market by having the applications available to them.

The more Applications available for your product the better.  Especially if the tools are NOT-cross platform and lock the end user into the product as an investment.  Ie like not being able to move your (mobile) phone number to any other telco.  Your locked in and the telco can take advantage of this.

Lets have a brief look at the four main players. Microsoft, Apple,  Google and Adobe.

Apple and the iPhone has changed the landscape of development.  Initially some of the development tools for Apple did come with a small cost.  These days they are free for anyone who cares to download them.  Especially iPhone development tools.  Initially a cost was involved to become an iPhone developer.  This is no longer apparent and iPhone development has been pushed onto any developer to pass the Apple developer site.

Apple has identified that it is the plethra of Apps on the App-Store that is locking user into the platform. This reminds me of the early days of the Computer and a factor Microsoft used effectively on its road to dominance.

Google, a leader in Open-Source development tools, is putting an extrordinary amount of investment in giving free tools and development platforms away.  These tools encourage the use of the Internet as a platform.  And as we all know, Google makes more and more money, the more we use the Internet to search or surf.  It is within their interest to get everyone using the internet as much as possible.  Open-source tools that direct users away from walled garden tools are where Google is encouraging us to go.

Microsoft, in which Steve Palmer is famous for shouting “Developers Developers, DEVELOPERS”, is now in a difficult position.  It has a very mature development tool set which once cost a decent amount to obtain.  All the tools are not available for free under limited conditions, or can be obtained for long evaluation periods.  Still, they tend to be the most expensive.  And really, it is probably hard for them to reduce costs or make them free.  Especially when there is a huge business community that are happy to pay for tools and support to go with them.

Microsoft know that developers drive the success of selling infrastructure.  For example, if all the business tools are based on Microsoft development tools. Large organisations are likely to purchase Microsoft server and other expensive business software tools to run them on. The free or near free nature of the tools coming out of Apple, Google and Adobe are definatly making it hard for Microsoft.

Adobe is new to this area with the newly dubbed ”Flash Platform” including Flex, Flash Professional and many other new tools. Adobe is trying to leverage the success of Flash as a Web technology.  These tools are easy to get and very inexpensive.  Adobe hopes that back-end infrastructure technology will drive the profits.  For example video streaming and DRM server purchased at very high prices by the incumbent media gatway companies. However, I am doubt this will work for them.

Adobe Flash technology does have (performance) issues.  The idea behind what Flash has evolved into is, from a developer perspective, very good.  Microsoft has identified that and given birth the Silverlight.  Possibly one of the most impressive developments from the Microsoft Development DEV team ever.  However, those who would likely use these tools, the general web developer, tend to be anti Microsoft.  Silverlight has less traction/takeup then anyone expected. In the business community it is probably very different, however as a general web surfer you will not see evidence of this.

As a developer, it has never been a better time.  The tools are fantastic and next to nothing to get.  I feel like a kid in a candy store..  And the candy is all FREE.