Flash is dead. Long live flash

Until now, in the eyes of many developers, even web developers, Flash along with Actionscript are a scripting language and a tool allowing you to create banners and ads that kill your CPU and freeze your browser. I’ve seen these prejudices many many times. Probably in the future, these things will never change. It’s just plain human to consider yourself a better person if you develop in Java or C#

But Flash is much more than this. Flash was much more than this. Flash was the number one solution for creating rich internet content, including games, video streaming, applications. Flash was number one because it allowed you to create content and deliver across browsers and operating systems. Some chosed it because it’s more difficult to hack than javascript, some because it was very easy to deliver rich content, some because it allowed complex architectures to be created. Whatever the reasons  were, forget about them, Flash is dying. Flash is not dying because of HTML5, Flash is dying because Adobe is too small to fight such a big battle with the giants. Adobe doesn’t believe it stands a chance in front of the HTML5 traction. Therefore, like in a war, Adobe is changing sides and is choosing to go with the flow. Focusing on the battles you can win, forget about the rest. This sucks, but in a way it makes sense.

Adobe has developed a plugin that has over 50 million downloads on the Android market. Adobe has the Flash Player reaching a total of over 99% of personal computers, a penetration rate that Java only dreams about. However, Adobe dropped AIR for Linux. Adobe is dropping Flash Player for mobile. But who was using those afterall? Who was creating content for Linux? Who was designing in Flash Player optimized for mobile? They are only focusing on what works and they are restructuring. Flash is still going to be a solution in the short term, but in the long run, flash is going to die in the way that we know it.

Flash is going through an identity crysis. It needs to honest with itself and I think this is what Adobe is doing. Flash is not appropriate for delivering mobile web content. Linux is not a platform targeted by flash developers. Therefore they’re out. When HTML based technologies allow you to create stuff that was possible in Flash 4 and 5, you are not going to use a 3rd party plugin to create your banners or your presentation sites. You are going with the SEO optimized over hyped HTML5 version. You are going with the rational solution. Flash is targeting now stuff that wasn’t possible back in Flash 4. Flash is focusing on 2 main directions: Gaming and Video streaming.

Adobe is trying to pivot with the Flash technology and not lose the traction it has at the moment. Adobe is switching the focus on AIR and delivering across platforms in a different way. The world we live in has changed into an application selling market. Adobe knows this. We know this. Everybody knows it. Even Microsoft who often fails to see the obvious sees it and takes a big step ahead with Windows 8. Adobe will deliver AIR on all the major players and will try to do this in the best possible way. It will be the alternative for HTML5, but will only make sense for gaming and video streaming. And Flash can kick HTML5’s ass on gaming and delivering video (DRM) because you basically don’t have them in HTML5. And there is not the smallest chance that you would see them out there very soon. Because HTML5 is just a big step back for any flash developer, going back to the origins, to the prototype based programming.

It is quite unclear what will happen to Flash Professional and the Flex framework. I think they will be gone or will suffer major transformations. Flash Professional will help nobody anymore. I am still using Flash Professional CS3 and I don’t miss any of the updates up to CS5.5. I use it for developing games but more for generating library files and grouping graphic assets together, I am not using it for animations or other stuff. Technologies like blitting make it obsolete when you are trying to squeeze every bit of performance. Flash Professional can only survive if it turns into a game creation tool, including 3D workflows. Flex framework is very cool to create rich applications for the web, but HTML5 will probably excel in this. It will make little to no sense to use Flex to deliver users rich applications when you can simply use HTML5. I can only see flex surviving if it’s ported in a way or another to HTML5.

Focusing on gaming and video streaming, Flash Player will be able to keep up the innovations. This is what is needed today, this is what Adobe will be offering you as a flash developer. It will also release technologies that will allow you to make the transition to HTML5 development. However, Flash as we know it is dead. It will have only these 2 specific use cases. Flash will work for desktop in the same way it worked until now and will allow you to deliver your rich content to your clients via the AIR runtime. And will probably do this very good in the short future. In the long run, if Adobe will manage and will want to invest in further innovations for the Flash platform, it needs to reinvent Flash. It will need to keep the constant gap that will be between Flash and HTML5 because really, you can do in Flash anything you can do in HTML5 but not vice-versa.

In the end, if you want to say Flash is dead, yes, I agree. Flash is dead, but I know better. I’ve seen Flash grow, I can feel the potential. Look yourself in the mirror like Adobe does. Do you really need the Flash Player for mobile and all the problems it brings? Wouldn’t it be better for you to deliver your application to the markets and the stores via AIR? I think yes. So, leave the panic behind, get over this week when everybody is calling the death of Flash, the fact that the end of Flash is near and you’d better start learning HTML5, you know better.

HTML5 still needs to fix the compatibility along the browsers issue. Bear in mind that the world still uses IE6 and IE7. Flash has it’s major advantage in being developed by one company for all the browsers. When you have Flash Player Version > 11 you know you can use Stage3D. How will a HTML5 version check look like? How will you know what you can use and what you cannot? How many fallbacks will your code have? How will you be able to make all the companies implement the same standards in the same way? In theory, I know it’s simple, but let’s see the practice. I’m still not buying the entire HTML5 stuff. I will start using it in order to see the advantages, I will try to choose wisely every time between Flash and HTML5. But if Flash Player manages to keep the same excellent penetration rate, the same innovation level, I am sure that I have a future as a Flash developer.

And remember, even if Adobe kills Flash now, you will still be able to deliver amazing content. Adobe didn’t killed the existing Flash Mobile, it just killed the future updates. You can still use Flash Player for mobile with the current version.

Flash is dead, long live Flash.

Flash player 11.2 and AIR 3.2 beta

Adobe just launched beta versions for their flash player and air. These are the first multi-threaded runtimes. Unfortunately there is no mobile support yet.

The release versions are scheduled for the first half of 2012.

The biggest new feature for the AIR and Flash player runtimes is Multi-threaded video decoding which will currently work for Windows and Mac OS. This feature will improve the overall performance of decoding because the video decoding pipeline will be fully multi-threaded. Adobe points that this is the first giant architectural leap for future improvements to be build on.

The other major feature I find extremely interesting for the Flash enthusiasts is the Background updates which will currently work on Windows. The background updates will work only for the release versions which makes sense because you don’t want your precious debug version to update automatically. This will deliver a much faster penetration rate for the new releases and will provide a major advantage to the Flash platform over rivals like HTML5 where the penetration rate will definately be much slower. This is one of the biggest advantages of flash and I am glad that Adobe realizes this and is pumping on it.

You might be wondering what happened with the .1 releases and betas. Since .1 will be a minor release with no major features, Adobe decided to skip the launching of betas for these versions.

Unfortunately there is still no news about the Stage 3D support for mobile. If you are interested in this field, you are encouraged to join the Flash runtime prerelease program

In order to download the beta version of the flash player 11.2 you need to go to the labs page. For the beta air 3.2 the download link is here.

Adobe AIR on Windows 8

Windows 8 tablet

I’ve had the honour and pleasure of seeing a Windows 8 tablet live on the 10th Timisoara Mobile Development Group, held at the Haufe-Lexware Offices.

Our hosts at Haufe-Lexware were kind enough to share the “joy” of using and working with a Windows 8 tablet. Basically Windows 8 adds a bunch of new features to windows as we know it.

The most important thing is the addition of the Metro Style UI, which is quite neat and it delivers you the “smartphone” experience, simple, clean and easy to understand. Basically Windows 8 will work in two modes, being some kind of combination of the 2 modules: metro and legacy. Legacy is the Windows as we know it, with all the programs that run in exactly the same way. You get a desktop and the only thing missing will be the Windows Key which will take you to the Metro UI dashboard.

This means that Adobe AIR, Adobe Flash Player and all the other stuff that you have now on your Windows machine will just work.. in legacy mode..

However, the applications that are going to be used in Metro UI style won’t be backward compatible and the developers will need to implement some kind of interfaces in order to work with the program. Most of these programs will be written in HTML5 and JavaScript.

Metro UI doesn’t support Adobe AIR, Adobe Flash Player or any other plugin(not even Silverlight) whatsoever. Neither does the Internet Explorer 10 browser – the Metro version. Confused? It’s really simple. You will have Internet Explorer 10 installed as legacy and as Metro. This means that you will have 2 different applications doing the same stuff. And on will support Flash and one will not. They do share browsing history and stuff, but they’re plain different.

However, considering the recent acquisition of PhoneGap, the long known cross-platform development tools offered by Adobe (Adobe AIR, Adobe Flash Player), considering the fact that the Metro UI applications are written in HTML5 and JavaScript, I am more than optimistic in relation to the development and deployment of AIR applications on Windows 8. For God’s sake, flash is running on Smart TV’s, is running on iOS, why couldn’t it run on Windows?

Adobe tries to play nice with Microsoft, considering that maybe until the release of Windows 8 in second half of 2012 things can change. Flash player 11 and Adobe AIR 3.0 definitely offer some exciting new features, like native extensions, the captive runtime and of course Molehill API and they have all the chances to find their way across the new Windows platform.

 

 

 

Adobe MAX 2011 news

The latest news from Adobe MAX 2011:

Flash player 11 and AIR 3 are released.

Flash based apps are live on Samsung SmartTVs. Soon to be supported on LG, TiVO. There are now 100 unique digital home devices that support Flash and AIR. Of course, this is only the beginning.

Samsung official release can be found here

Adobe now offers HTML5 cross platform application development using Nitobi’s PhoneGap. PhoneGap is a popular open source framekwork for building mobile cross-platform  applications with HTML5 and JavaScript. Adobe doesn’t want to loose its title of King of cross-platform development.

Also, a third public preview of Adobe Edge was announced. Adobe Edge is a new HTML5 web motion and interaction design tool.

Adobe Creative Cloud is a new initiative that radically redefines the content creation process. It is announced in parallel with Adobe Touch Apps which is a family of 6 intuitive touch screen applications designed for Android and iOS tablets: Adobe Photoshop Touch, Adobe Collage, Adobe Debug, Adobe Ideas, Adobe Kuler, Adobe Proto

Adobe aquired Typekit Inc. a leader in the delivery of high quality fonts for use on websites.

Adobe Digital Publishing Suite, Single Edition allows designers to publish interactive content created with Adobe InDesign CS5.5 on the Apple iPad tablet

More to come..

Flash player 11 and AIR 3 release

They‘re finally here.

Flash player 11 on flashplayerversion.info

Flash player 11

You can download the official releases here: Flash Player 11, AIR 3

You can also update your mobile versions from Android market and Amazon Marketplace.
However, 3D support for mobile is expected to be launched in a production release, so we cannot test the full mobile power of Molehill.

Starling framework for flash

With the release of the new flash player 11 Adobe is taking out from the dark the Stage3D and gives actual 3D power to its users.

However, since 3D is in the early stages, it’s not always easy to find your way around. Therefore, Thibault Imbert – the guy who owns the bytearray decided to make a collaboration with the Austrian company Gamua and the results are amazing.

What they were trying to do, is to simply interface the use of Stage3D and hide all the complex business logic behind the scenes. You now have the power to use 3D without having to learn 3D. Their framework is called Starling Framework and is the new star on the block. It’s based on the Sparrow Framework, widely used on iOS and I think it’s going to rule the world. At least the 3D world.

 

You can find the introduction of the framework here and you can find, download and test the actual framework here 

 

Enjoy!

Adobe flash player 11 and AIR 3

Adobe announced it’s going to launch the Flash player 11 and AIR 3 updates in early October, probably during the Adobe MAX conference

We are very excited about this, since it’s going to add lots of new cool features. Of course, the crown jewel in the new releases is the Molehill API which is going to boost the performance for flash games and it will provide the first real 3d support.

Flash player 11 will be the first version of flash player to deliver native 64-bit support and it will provide the “so called” native extensions which will allow you to run native code on different devices (including iOS, Android and desktops) which is kinda cool.

Starting with flash player 11, you no longer have to worry about the users that don’t have AIR installed because  you can use the captive runtime. This means that the user doesn’t need to have AIR to run your application. Moreover, you can ‘bind’ your application to a specific version of AIR runtime without worrying when a new AIR release is out.

Along with these releases Adobe will roll out their Flash Builder 4.6 version which includes some further optimizations and hopefully it will fix the bugs from 4.5.1 Also it will introduce some new components and improved performance.

You can download the release candidates from Adobe Labs.

 

You can read the flash player 11 release notes on the adobe blogs.