ThinkDigit Home
Subscribe to the Newsletter
Search
 
SKOAR!       / SHOPPING
 
 
News / Features / Downloads / Channel 5
 
 
The future of Flash and what it means for developers
 
Posted by
Kshitij Sobti
5
294
Posted on: Dec 01, 2011 23:34:39 IST

 
 
 

There has been a lot of news from Adobe when it comes to the Flash platform and it hasn't been very clear what the future holds for the Flash platform. Hopefully we can clarify what some of these developments mean.

Adobe has signaled the end of the Flash Player for Mobile, however does this mean the end of Flash? No. No more than it means the end of Firefox because Firefox isn't available on iOS. The confusion here stems from what Flash really means.

There are two aspects of Flash platform that we should take a look at. Firstly, Flash as a way creating content, this could be using Flash Builder, Flash Professional, or the number of free and even open source tools available that can create Flash content. These are tools for creating content, and Flash files are just an output.

Second is Flash as a way of consuming content. The Flash Player is a runtime that executes SWF files, or Flash files, this is comparable to how Gecko, and WebKit are runtimes that execute open standard web content (HTML, CSS, JS). A large number of the capabilities that we unique to the Flash runtime are now becoming a part of open standards.

There are many odd ways to creating Flash content that will run on the Flash Player. For example, Adobe's Alchemy lab project allowed developers to compile C++ code to Flash. Another language haXe allows code written in it to be compiled to Flash files.

There are also alternative ways to consume content created in Flash tools. The AIR runtime allowed Flash content to be packaged as native applications for desktops and mobiles. With haXe for example, one could write code that could be compiled to Flash to run on the Flash Player or to JavaScript and run directly in a browser. Adobe too is working on allowing Flash Professional to export HTML content, and is working on a cross-compiler that can compile Flex applications written in MXML and JavaScript to web standard (HTML + JavaScript) applications.

While Flash is being primed for creating native applications, so is the alternative of open web technologies via PhoneGap. PhoneGap allows one to package web applications as native applications on all major mobile platforms, so they can be purchased from a web store and run natively. It could well be possible to have a Flex applications compiled to HTML + JS running on PhoneGap.

So what does the recent announcement mean in this context? Mobiles will no longer be able to consume content created in Flash tools using the Flash Player. It will still be possible to use AIR and run such content on mobiles directly as native apps.

While Flash Player for mobiles made it possible for websites designed for desktops to work on mobile devices, merely working isn't enough. For a website to be usable, it needs to be designed for smaller screen platforms, whether it uses Flash or not. So while Flash for Mobile makes sites that use Flash accessible from mobile, it doesn't automatically make them mobile ready. This is as far as users see it. They have a Flash website they want to visit, and they can now visit in on desktops and mobiles thanks to the Flash mobile plugin. As long as the website works the same, users will not care whether Flash is used or not. 

Additionally, while one of the advantages of Flash has been that it is available on a majority of computers, the same has not been true of Flash on mobiles. With the major share of iOS devices, and no chance of the Flash Player on mobiles, it was unlikely to ever reach the same level of penetration, and thus unlikely to ever become a serious means of delivering content in the browser.

Adobe still intends to make it possible to create native Android, iOS and Blackberry applications using their tools. Why? Because these capabilities are useful to those creating applications, and something people pay for.

So for now Flash is safe, it provides a number of features still that aren't provided by any browsers directly, and in fact aren't even part of the standards that will define the future of these browsers. It also provides a number of features consistently that browser vendors are still inconsistent about. For example, Flash Player is still a consistent way to deliver H.264 video, and a consistent way to deliver DRM protected and streaming video. Flash Player 11 might also be a consistent way to deliver 3D content as Internet Explorer is still lacking there.

Additionally, the Flash runtime is being targeted by major toolkits such as theUnreal 3 SDK, and Unity 3D. Even Crytek is looking into enabling 3D gaming in the browser using their engine running in Flash. So for gaming at least there is a good case to be made, especially since such games will run on Windows, Linux and Mac OSX.

There is something really wrong when a plugin becomes necessary to use the internet. A plugin is something that is added to the core experience, and if that it required for all people, then there is something wrong with the core experience. As new web standards add more features that make it possible to create the kind of content only Flash can now, the Flash player will become further marginalized.

Plugins are very important, because the web can never be everything for everyone, and there need to be ways to enable things that web standards just don't allow or enable, however they should never be a requirement to view a majority of the content on the internet.

Currently Flash player is required if someone wishes to create a website that can display animations, play video, handle uploading multiple files, display 3d content, etc. One by one these features are becoming part of web standards, and eventually, Flash player won't be a necessary plugin but a plugin needed by those who wish to play internet games or watch protected video. The others will be able to do without it.

So while it is unlikely that Flash will go away any time soon, in the longer term, it will just not be as important. HTML and web standard technologies are here to stay, and it is better to be prepared.







 
 
 
Latest Features
 
 
 
 
Comments 5comments
 
Posted by gyvjnvxfyvi on Jan 03,2012
 
7Y6J0T gaukbiazdcua
 
Posted by Jaclyn on Dec 31,2011
 
Appreciation for this infotrmaion is over 9000-thank you!
 
Posted by CyberCipher on Dec 27,2011
 
I am inclined to agree with eveything audas posted in his comment. One more thing, though. I've been developing Flex apps for web sites for many years now. One of the things that I really like about Actionscript/Flash based web apps is that I write them once, and they run in IE, Firefox, Chrome, et. al. with little or no modification, They just run. I don't think we're going to be able to say that with HTML 5. Each browser vendor is going to render this stuff differently. We are going to be back to "write once, debug EVERYWHERE". If things turn out the way that I think they will, we are going to be right back in the 1990s again. Someone needs to start an initiative to return to HTML 4 and fork this entire process into an altogether different direction.
 
Posted by Kshitij Sobti on Dec 02,2011
 
@audas And Microsoft's WPF can make even more expressive and rich applications and games than Flash and with a lot more privileges. It is very easy to make a plug in that simply provides access to all the features of the native system. Java can do a whole lot more than Flash. So why is Flash more important? Because it is easier to make content, especially for designers, and Flash is installed on most computers. Flash is ahead of HTML in the same way that Java is "ahead" of Flash, because there are some features that are not important or needed.
 
Posted by audas on Dec 02,2011
 
firstly flash player 11 on mobile will be maintained - that means it will be here for at least two more years. In that time we will see what flash does (amazing animation at lightening speeds in tiny file sizes) being done by web kits and html5. This means ridiculously large file sizes, incredibly slow and processor hungry. Flash has everything html has - including touch, layout, fonts - everything. So now RIA applications will have to be done in html5 for web - and along with the new breed of tools from adobe, this means you are going to see the internet inundated with huge files sizes of clunky, ill considered, poorly executed web sites, ads and animations from every two bit kid on the planet spamming your mobile phone. Remind you of anything ? Yes it does - it reminds me of when flash first arrived - hell is going to be revistited because of small minded IDIOTS who dont like plugins despite all the amazing benefits they bring. As far as your assumptions about 3d in non explorer browsers - you must be kidding me if you think this is somehow capable of what flash is delivering. There is a pretty good reason why flash is now known as the WEB HD while html5 is now RICH. Keep up. The features of flash video are so far ahead of html5 that there is absolutely no way it will be able to compete with flash in delivering what the web is all about - consuming media, games and music (because flash 11 has dolby 7.1 surround buddy). So what does this REALLY mean ? What is the future ? Well firstly flash has always been miles ahead of html - years - in fact the latest html5 incarnation is in reality about flash 5 at best, or flash from 5 or 6 years ago. Sad really. And this is where html5 will stay for at least 8 years. And in that time flash has already moved to being the best interface between native and cloud, touch, video, 3D, native extensions, peer to peer, digital rights management etc, etc. HTML will not be able to do that for 8 years. And in that time where will flash be ? Well we saw how incredibly fast it left html behind over the past 8 years - safe to say it will happen again. So the reality is that html5 is set to pull the hair out of every mobile user on earth as crap ads take over their screens with resource hungry animations clog down their mobiles, drain their batteries and chew through the costly mobile bandwidth - and that my friend is EXACTLY what is happening right now. Whats the solution ? Javascript blockers, thats right, javascript blockers are being installed on mobiles faster than you can say - BRING BACK FLASH. Here we had an entire mature industry of animations specialists who will be put out on their ear by jealous inexperienced wanna-bes. So in two years time - when mobile phones are pretty much as powerful as todays desktop - what will happen after everyone has pulled their hair out screaming about this nightmare called html5 ? Well - adobe will simply offer the same plugin to the msart phone that they do for the desktop - will be the same by then. The reality is that adobe has just realised you idiots just need time to realise that super fancy high end animations and frustrating html5 pages are just as bad no matter if they are written in flash or html - and has given you two years to work this out - during which time flash player 12 will be out for desktop, same download for your Android - so basically there wont ever be a time when we dont have a flash player. Have a nice day - a very best of luck with your new html5 animation conversion tools - your gonna really, really, really need it.
 
 



 
 

 
 
 
 
Newsletter Subscription
 
 
 
 
 
 
 
 
 
 
 
 
 
 
http://devworks.thinkdigit.com