Despite what some folks in the Adobe community think, I’m actually still a big fan of Flash and what it represents. I do however hold Adobe up to a much higher standard than I did with Microsoft, as for me they have shown endless amounts of potential but have in my opinion squandered through either in-fighting or misalignment with the rest of the industry.
I’ve read a many a post on the “Open Screen Project” and whilst the concept of putting Flash Runtime on multiple devices etc is quite an appealing concept, I just don’t see them pulling it off beyond a few million units here and there. It’s a reality check that I think a lot of the Adobe staff need to take a step back and review.
Putting Flash on the iPhone or vNext desktop device is the easy part and I don’t think a lot of companies are realistically against that idea on it’s own. They would be typically skeptical of the technical dependency when you start too look beyond the “Open” PR spin and start focus on the tooling and ecosystem surrounding it.
Adobe just don’t have the developer numbers to support a sophisticated ecosystem it requires. There are a lot of exceptionally talented programmers in the Adobe community, some of which are fighting well above their weight – these however aren’t the majority. Adobe needs more of a groundswell of developers, ones that typically hail from either .NET, PHP or JAVA as their previous breeding ground. To date, they haven’t yielded that as fast as they should/could.
So why me, someone with little PHP experience? I’ve always felt like evangelism is about growing your developer community and developer relations is about helping the community you have – Ryan Stewart, Adobe Evangelist.
Adobe needs to court these folks and fast, as if they can get these folks to switch gears into the Adobe community lifestyle, they in turn and increase there developer base in a much more significant way than they have in the past by pounding at the Java and/or .NET developer doors.
Assuming they fix the Developer base, they next need to convince OEM manufacturers that their tooling isn’t the liability in this equation. I say that, as whilst its fun and 10x more productive to build Flash based solutions via Adobe specific tooling, this in turn creates effectively a liability in around the concept of being “”Open”. It’s not really Open, its more of a half-hatched Open concept, as producing a SWF outside Adobe tooling is actually not a likely thing to occur in the industry. The reason being is, whilst you can technically make your own SWF, you are still required to fall into line with Adobe’s roadmap and vision of where it all heads.
Implementing software which creates SWF files has always been permitted, on the condition that the resulting files render "error free in the latest publicly available version of Adobe Flash Player." – Wikipedia.com
Point is, that whilst their intentions are righteous and feel open, you have to face reality that this is just shifting the boundaries on a total lock-in and instead of declaring the Runtime and File Format as completely locked, its really the tooling story behind it is where the money tree begins. After all, Adobe aren’t in this business for free, they have shareholders and a $3billion+ fiscal profit expectation to meet.
The tooling component to this equation is really the bottleneck as could you imagine what would happen if say ActionScript 3.0 and Flash were solutions that a Visual Studio .NET developer could write inside the said tooling? It would have a huge impact on both sides of the isle roadmaps that’s for sure.