Dear Flash & Flex Interactive Developers, keep calm and carry on. The news from Adobe seems like a big deal now but I’m not sure that it’s soon enough to judge what the long term impact will be. In my opinion, it’s not yet time to panic (is it ever?) and in this post, I’ll talk about why.
First, if you don’t know what I’m talking about, check out the news. I think the best explanation comes from Mike Chambers’ Blog and a corresponding post on the Flex Team’s Blog.
Don't panic! Take a deep breath and look at this cute bunny
Not much has changed with the Flash Platform
If you read closely, not that much has really changed. The problem is perception. Let’s review what is going away and why it’s not as crazy as it might sound.
Mobile Flash Player
Adobe is discontinuing work on the mobile Flash Player. I don’t know the numbers of people building Flash content for Android but I suspect it’s not incredibly high. I would also wager that even Air on Android/iOS is still far from critical mass, but Adobe say they will continue to support this. The desktop Flash Player will stay the same and for the foreseeable future continue to surpass HTML5 in features and cross-platform functionality.
Another way of saying this is that the Flash Platform remains the best choice for the tasks that it was already the best choice for. Mobile was never one of these and some applications, like video players, may have lost that title to HTML5. But in cross-platform, rich-media, deeply interactive experiences on the web, Flash is still ahead of the competition.
Flex is still here
Adobe is discontinuing its support for the Flex SDK. However, it will stay around as an open source project (it was already open source.) It may never get better than it is already, which so far has been good enough to become the platform of choice for many Flex developers.
Flex cannot get any worse than the next version 4.6, which you were probably looking forward to until today. And you know what, that’s okay. We don’t need to be so obsessed with the next thing that we change careers because the next next thing has an uncertain future. I happen to know of some projects that are still using Flex 3 and will probably never upgrade. Why? The user doesn’t know the difference between mx and spark skins.
It may also get better after being untethered from Adobe and in hands of the Flex Community. In other words, we’re in charge now. The Spoon community, who is inheriting the Flex project, already have plans to make a version 5.x.
Fear itself
The real issue now is the way the public will preceive this news. This announcement has sapped the confidence of a lot of people, customers and developers alike. In my opinion, it’s not the time for us to decry Adobe as evil jerks. It is a time for us as experts to try to help our clients, companies and the public to make sense of the news. It’s time to remember that Flash is just a tool in the arsenal of an interactive developer. In fact, Flash’s popularity, due to largely political reasons, has already been on the decline for a while now. But, it will certainly be dead if the Flash users themselves don’t believe in it.
The next time a client wants an awesome, interactive video, 3D puzzle game, website thing I will still recommend Flash. I don’t want to have him tell me “it has to be HTML5″ because he read online that “Flash is dead.” In fact, I think it’s our job to talk about its strengths and its weaknesses in a totally objective way. We should all dwell in the middle ground between Adobe zealotry and jumping on the next bandwagon.
Your next job
I feel hopeful that the shit will not hit the fan, at least not immediately. That being said, I am always an advocate of looking at other technologies and keeping those abstract coding skills honed. Good developers are in a prime position to port our skills to whatever platform comes next, and those skills are almost always in demand. Even HTML5 (JavaScript) apps share a very similar language with AS3 (really AS1). I was able to pick up JQuery and build my first HTML5 project in a matter of a day or two.
As Mike Chamber’s writes:
Joel Hooks adds some great notes on this in his blog post. I’d like to also add HAXE, Java, C# and Dart to the list of languages that you should be able to pick up with little effort.
The Community
In LA, our local Flex group shut down abruptly after this news was released. I personally feel this was very hasty indeed and wrote a letter about it upon which this blog post was based. I see that a lot of people are really pissed and their identities are in question. If you’re in this position, I would suggest instead of jumping ship, why not continue to talk about how this will impact our jobs and what skills we can port to other platforms. If there really are people out there who are going to lose their jobs over this, and I think it’s too soon to say, we should still be able to support each other as a community.
Even with all this positivity, I still have to agree with @neurofuzzy “Anyone who has ‘Flash’ in your job title, scratch it out and write ‘Interactive.’” It’s something we should have all done a long time ago because I believe we are more than just Flash dudes.
I’d love to hear your thoughts on all of this. Please leave comments. It will be very interesting to look back on this post in 6 months and see whether I was right to keep a cool head or being terribly naïve.