Flash Roadmap Whitepaper Published
We have just posted a new whitepaper on Adobe.com. The whitepaper, titled Adobe roadmap for the Flash runtimes lays out the 1 to 2 year roadmap for the Flash runtimes (primarily Adobe AIR and Flash Player). This includes information on specific planned releases, longer term player work, and supported platforms.
This is actually the third Flash platform white paper that we have released in the past week (Adobe’s view of Flex and its commitments to Flex in the future, Adobe Flash Player and Adobe AIR security), and is a part of a larger process of trying to provide clear and open communications around our thinking and plans for the Flash platform.
The primary goal of the whitepaper is to have a single definitive resource that provides clear insight into Adobe’s plans and thinking around the roadmap for the Flash runtimes.
While in the past we have been open around our plans for the Flash runtimes, there was never a single resource where developers could find all of the latest thinking and plans around those runtimes. News and information was often spread across multiple resources, including the Adobe website, Adobe blogs, personal blogs, forum posts, and even tweets. We will still leverage these various means of communications, but they will build on top of the whitepaper. As our thinking and plans around the Flash runtimes evolve, we will update the whitepaper with those new plans.
This is also part of some more extensive changes at Adobe to help us avoid some of the communication missteps which have caused so much consternation and frustration over the past couple of months. Not only does the publication of the whitepaper give us a clear and concise way to publish information and plans around the Flash runtimes, it also provides developers with a definitive resources on where to get the most current information around the Flash platform.
This speaks to another goal of the whitepapers. We understand that we have damaged our trust and credibility with the community over how we have communicated some of the recent changes around the Flash platform and that trying to regain that trust is a long term process. We have to be clear and open around our plans around the Flash runtimes, and then demonstrate that we can follow up those plans with actions. This whitepaper lays the foundation of the first part of that, and hopefully our actions and runtime releases over the next 6 to 12 months will demonstrate the second part.
Finally, as part of the release of the whitepaper, I and some other members of the Flash and evangelist teams will be visiting user groups world wide. This will be an opportunity to go over the roadmap in more detail, have a frank and open discussion around recent changes around Flash, as well as discuss Flash’s role on the web and how it related to HTML5. The first set of meetings are over the next two weeks in Europe, and we will announce more for North and South America, and Asia over the next couple of weeks. If you would be interested in hosting a meeting, just shoot me an email at mesh@adobe.com.
We are already planning an update for the whitepaper in a couple of weeks, so if you find anything is not clear, or would like it to cover other topics, please post them in the comments, or shoot me an email.
This is mostly expected and if all is true and will happend as stated, will be major fo the platform
Martin Weiser
22 Feb 12 at 1:23 am
[...] Flash Roadmap Whitepaper Published This entry was posted in Informacje. Bookmark the permalink. Post a comment or leave a trackback: Trackback URL. « Praca przy projekcie dla Flash/Flex Developera [...]
Przysz?o?? jest tu: Flash, Flex & AIR whitepapers
22 Feb 12 at 1:55 am
[...] Flash Roadmap Whitepaper Published http://www.mikechambers.com/blog/2012/02/22/flash-roadmap-whitepaper-published/ [...]
Hawaii Flash User Group » Blog Archive » Flash Roadmap Whitepaper Published
22 Feb 12 at 2:28 am
I would like to see more talk about the future of enterprise flash development also from Adobe
Nikos
22 Feb 12 at 3:53 am
The language and VM improvements look so far away, sigh, I’d love an improved ActionScript so much… I love AS, thanks to it I learned to program several years ago, but it looks outdated nowadays.
My view: method overloading and enums would make a lot of codebases and public APIs look better and cleaner. The option to use “typed” functions, like in HaXe would be a nice addition as well. I don’t care much about being able to create abstract classes, as I feel current workarounds to be valid enough, and composition is preferred, would like to see some new event model, or way to specify that a class implementing an interface must dispatch a certain event.
Also, generics would be nice. Some people say that generics support is overrated, but we cannot deny that it would bring cleaner and faster code.
A couple more things I’d love:
- Cryptographic API: way better than any custom implementation if implemented propertly.
- Native Extensions for the web: I understand it could conflict with the sandboxed environment the plugin runs on, but maybe the ANEs could be signed or use a system similar to what Android developers do, and/or make the plugin to show some alert advicing the user and asking him for permission in order to run the content. Similar to the webcam alert.
Héctor
22 Feb 12 at 4:13 am
Forgot another thing… I’d understand if this remains untouched, but a lot of programmers would like some IDisplayObject interface.
Although it’s hard to settle on how it should be… an interface that works with both Stage3D and the old display list would be nice, but I get it’s not possible (at least if Starling or other frameworks could use the built in interface, it would be a gain and a plus).
An interface with a simple “asDisplayObject” would be desirable I guess, I see it being easier to use and reuse, the problem would be, which return type to use then? Generics would solve this problem. Having x, y, z, scale, rotate and a myriad of other properties and functions would be bothersome…
Héctor
22 Feb 12 at 4:24 am
Can we sign up for beta on new tools with these changes?
Shawn Makinson
22 Feb 12 at 8:03 am
What about multimedia/game developers using flash builder and especially, Flex libraries inside their projects?
I mean, I’m mostly a graphic designer (think audiovisual shows and interactive presentations for museums and concerts), but i’m accustomed to libraries, frameworks, testing methodologies associated with Flex Libraries.
It seems that from this roadmap plus the recent changes on the Flex front, I should expect to gradually abandon even simple flex-related stuff like ArrayCollections and HTTPservices, Buttons and Container Widgets and start from scratch using Flash CS5.5 hoping that some of those libraries could reappear in the “Next” refactor of flash-based technologies.
I mean, some of those future updates are great, especially low-latency audio, full screen input support and multi-threading, but considering how much stuff I have to learn again to reach what I was able to do with my previous toolset, it seems that the prospect of forgetting flash altogether for most “multimedia” audiovisual projects and jumping to stuff like Processing or MAX/MSP (which already match most of those future capabilities of the Flash, plus some more like MIDI/OSC/USB device support) is more appealing.
Mr. Jingle
22 Feb 12 at 9:50 am
Is there anything I can do to get involved with testing the next version of Flash Player (Cyril)? For the last few years I’ve been working on projects that rely on Flash’s audio and microphone APIs, including the ability to depend on predictable timing of generated audio playback and recording.
Tyler
22 Feb 12 at 10:19 am
It would be great to see some mention of Alchemy in this whitepaper as well…
———
Yes, the current roadmap doesnt include tooling yet, although we are considering adding it in the next update.
mike chambers
mesh@adobe.com
Keith
22 Feb 12 at 11:51 am
You can sign up for private pre-releases at:
http://adobe.ly/jmajkr
mike chambers
mesh@adobe.com
mikechambers
22 Feb 12 at 11:54 am
Mike, so if I read this correctly we should expect the same flash player features in Adobe AIR at the same time?
——-
Yes. That is correct.
mike chambers
mesh@adobe.com
Nate
22 Feb 12 at 4:19 pm
So, reading through this, I see nothing about standardizing hardware acceleration over different platforms. Will StageVideo ever reach desktop AIR builds? Multithreading action script is a nice to have, but developers of AIR have an immediate need for (GPU) hardware accelerated video support in desktop applications. I’m currently splitting a single AIR app into multiple AIR apps because of the single threaded nature of action script and the CPU bound performance of video delivery on desktop AIR runtimes.
Jeffrey Gilbert
26 Mar 12 at 10:00 pm
When can we expect stagevideo support (desktop) in AIR?…
Hi Jeffrey, I no longer work at Adobe so I cannot comment on product plans. Multithreaded video helps accelerate video playback at the decoding level. StageVideo accelerates video at the rendering level. For the latest perspective on the Flash runtime …
Quora
27 Mar 12 at 6:04 am