Flash Professional and the Future
Yesterday was probably one of the most overwhelming days of my entire career. First, Adobe informed developers that we are going to stop developing the Flash Player for mobile browsers, then news came out that there were layoffs at Adobe, and finally, Adobe held a financial analyst meeting where we spelled out the Creative Cloud, and the fundamental strategic shift Adobe is making.
All of this news is a lot to digest at once, and I know that there are a lot of questions and concerns from the community about what all of this means. I am working on another blog post which will address this from the Flash community’s standpoint, but I wanted to make a quick post and debunk a rumor that has been going around about the future of Flash Professional.
I have seen a couple of versions of it, but basically, the rumor is that the entire Flash Authoring team was laid off and that we are no longer developing Flash Professional.
Both of these rumors are false.
We are actively working on the next version of Flash Professional and have a long term commitment to it’s continued development.
While there were layoffs on the team (as there were on a lot of other teams), we still have a team actively working on future versions of the tool. The Flash Professional team continues to have offices around the world, just as they did prior to the announcements. The core team, including product management and engineering members, continue and will continue to be based in San Francisco.
I can’t go into a ton of detail about all of the new features and improvements included in the next version of Flash Professional (we gave a sneak of some of them at FOTB Brighton last month), but some of the new features include:
- SpriteSheet export for both Starling and HTML5 / Canvas. Lee Brimelow has a sneak here.
- Support for packaging and exporting AIR applications for mobile that leverage native extensions.
- Mobile prototyping and simulation for AIR apps.
In addition to working on new features, we are also in the process of a pretty fundamental re-factoring and modernization of the tool’s code base, which, among other things includes a de-carbonization of the tool on the mac platform. This is longer term project, being done in parallel with CS 6.0 development.
I am going to be speaking at FITC Tokyo in a couple of weeks, and will be showing some of the latest stuff we have been working on in Flash Professional.
I understand the confusion and frustration around everything that has been going on, and I know how difficult the past couple of days have been (probably the most difficult of my entire career). As I mentioned above, I am working on a broader blog post to discuss some of the news from yesterday, which will hopefully provide more information and clarification around all of the changes going on.
Please post any questions in the comments, and please keep comments on topic.
UPDATE : Just a quick reminder, but please keep comments on topic (about Flash Professional). I know there are a lot of questions about just about everything Flash, and I am working on a post to address them.
UPDATE : Added some clarification around team composition.
[...] Chambers lays to rest the myth that the whole Flash Professional IDE Team were made redundant. They’re obviously [...]
Photon Storm » Blog Archive » The reality of developing web games with Flash, HTML5 and Unity
10 Nov 11 at 5:48 pm
Thank you for debunking that myth. I had heard it from several places, and confess I did actually believe it when taken in context with all the other mess going on over the last 48 hours.
My only concern is that I honestly don’t think it matters any more if you are or aren’t working on it. The features being added seem HTML5 focused, which sends a confusing message that the Flash IDE may just evolve into an HTML5 content prep tool. The damage done by the original Adobe press release is incalculable right now. But at least I’m glad the IDE will be updated for the next year or so while we transition to new platforms.
Richard Davey
10 Nov 11 at 5:54 pm
thanks Mike for posting this- it does help to clear things up.
There has been a lot of confusion around all of the recent changes and wish the PR this week had been more clear from Adobe. It would be good to have Kevin L also have a blog post about what these changes mean for the Flash Platform to reassure devs to continue to use Adobe tools for mobile app development.
Having been a part of the mobile Flash team at the beginning of things, and since moved onto Nokia, I know it’s going to be difficult for those Flash devs to educate their clients (existing and new) to consider AIR mobile apps.
I’d suggest that the evangelism/marketing team create a simple one page graphic that illustrates what’s possible now with Adobe’s tools and run-times for mobile, desktop and web. Without any clear visual definition of the new strategy, devs and clients will have to interpret blog posts and PR releases.
Bill Perry
10 Nov 11 at 5:56 pm
Spot on Mike.
I haven’t commented on any of the rubbish being broadcasted over the internet cos I didn’t feel the need to. Adobe is smart enough to know that Flash plays a major role in it’s long term strategy.
Flash developers are safe and will soon be able to export to HTML5. i really cannot be bothered.
Thanks Again.
Ifeanyi Gbemudu
10 Nov 11 at 6:00 pm
Hi, Mike! Thanks for the clearing things up!)
Some weeks ago I watched the Flash Professional sneak peek “A glimpse-at the future” at Adobe.TV (http://tv.adobe.com/watch/max-2011-envision/flash-professional-sneak-peek-a-glimpse-at-the-future/) and wish everyone interested in the Flash Pro watch it too.
So, any rumors about Flash Pro discontinue are groundless after watching this great session from recent Adobe MAX.
focus
10 Nov 11 at 6:02 pm
@Richard Davey
–
My only concern is that I honestly don’t think it matters any more if you are or aren’t working on it. The features being added seem HTML5 focused, which sends a confusing message that the Flash IDE may just evolve into an HTML5 content prep tool.
–
Well, to be fair, I only listed 3 features, only one of which was related to HTML5. The other two listed focus on mobile AIR development.
But, and this is something I want to be very upfront about, a lot of the things that you have done in the past using Flash, are going to be increasingly done via HTML5 / the browser. I realize that this is a big change for a lot of people who have done Flash work for a long time. Adobe is working to not only make tools to make it easier to build this HTML5 content, but also to make the transition easier for Flash designers and developers (for example, the spritesheet export feature above).
The thing is, as the capabilities of the browser have grown, especially in regards to motion graphics, the demand for designers and developers who have experience working with motion graphics have grown. You have probably noticed that a lot of the cutting edge motion graphics work being done in HTML5 today, is done by designers and developers who have been long time Flash developers (Grant Skinner, Branden Hall, Seb Lee-Delisle, etc…). This is a huge opportunity for anyone who has worked with Flash.
But, the bottom line is, if you need or want to use Flash Professional to create motion graphics or other content, you will be able to.
mike chambers
mesh@adobe.com
mikechambers
10 Nov 11 at 6:05 pm
@Bill Perry
–
It would be good to have Kevin L also have a blog post about what these changes mean for the Flash Platform to reassure devs to continue to use Adobe tools for mobile app development.
–
Hey Bill, good to hear from you.
Yes, we could have provided more content around some of the announcements. Our goal was to try and be very clear about what we are doing, but in trying to focus our message, we lost some of that context.
Regardless, I am working on another blog post which will hopefully provide some of that context and clarity.
mike chambers
mesh@adobe.com
mikechambers
10 Nov 11 at 6:07 pm
Thanks Mike,
Interesting news. Personally I would welcome a world where there was an option to build in AS3 and export to JS. I’ve recently dived into the world of haXe and the freedom to work towards both paradigms is liberating. If Adobe’s content tools are pivoting to supporting HTML5, I hope that they also consider adopting the haXe approach towards platform agnosticism for AS3.
Alec McEachran
10 Nov 11 at 6:10 pm
Good post,
however, we’ve seen products like Fireworks that Adobe decided to offshore… and all they do is fix bugs and eventually the quality drops… it crashes everytime I close the app.
I would like to know whether Flash is being offshore? I think everyone should know that… What percentage of development is being done in SF vs offshore??
And I also heard the head of Flash team was let go , is that true?
YG
10 Nov 11 at 6:16 pm
does Flash Pro have a fairly healthy-lifeline?My question is what about Flash Builder 5& Flash Builder?? it would seem a nice ‘may just evolve into an HTML5 content prep tool.’-for good!!–is that something Adobe might consider???
Dave V,
10 Nov 11 at 6:41 pm
By “de-carbonizing” the Flash IDE for Mac, I assume that means you’re going to give it a new interface that gets rid of some really ugly legacy (Macromeda-era) buttons, dialog boxes and other quirks?
Don Allen
10 Nov 11 at 7:33 pm
+1000 on the idea of a single focused website promoting air’s capabilities and reach. The marketing is just pure fail right now.
Look at this website: http://www.anscamobile.com/corona/
That s how you market a product. Basically it’s nine slides, saying thesame thing ver and over and over, “we are the best solution for mobile” Links to overwhelmingly positive articles about the product, quotes from developers, statistics about install base. If a journalist or developer goes there, he leaves pretty convinced!!
This is not even hard stuff here, this is just fundamentals on promoting your products. Here’s basically 2 guys, former flash devs that are now beating the pants off of a multi-billion dollar company in terms of marketing, and developer/public perception.
You have a great mobile product. The real question is, why does no one know that?
Shawn
10 Nov 11 at 7:50 pm
@YG
–
I would like to know whether Flash is being offshore?
–
The Flash Authoring team, as well as pretty much every other engineering team in the company, has engineers and offices in multiple locations, not all in the united states. That has not changed.
The core product management, marketing and engineering teams are based in San Francisco. That is not changing. I updated the blog post to try and make that a little clearer.
Here is the section I updated:
The core team, including product management and engineering members, continue AND WILL CONTINUE to be based in San Francisco.
I am not going to comment on any individual lay offs.
mike chambers
mesh@adobe.com
mikechambers
10 Nov 11 at 7:58 pm
@Dave V
–
does Flash Pro have a fairly healthy-lifeline?
–
Yes, I think so (and I hope that came through in the blog post).
mike chambers
mesh@adobe.com
mikechambers
10 Nov 11 at 8:00 pm
@Don Allen
–
By “de-carbonizing” the Flash IDE for Mac, I assume that means you’re going to give it a new interface that gets rid of some really ugly legacy (Macromeda-era) buttons, dialog boxes and other quirks?
–
They are doing a pretty comprehensive overhall of some of the framework layers, but I dont have any info on any updated UI or UI elements (we still have a lot of work to do).
Sorry I dont have more info right now.
mike chambers
mesh@adobe.com
mikechambers
10 Nov 11 at 8:01 pm
Hi Mike,
can you clarify the future relationship between flash pro and Edge. Are developers supposed to use Edge to develop content for html5 and then switch back to flash to make the same content to work reliably in older browsers. I can accept that moving to html5 is the way forward but if adobe wants to keep me as customer they could do a lot to make the transition easier and be clearer on the direction they expect developers to take.
david doull
10 Nov 11 at 8:04 pm
@Shawn
–
+1000 on the idea of a single focused website promoting air’s capabilities and reach. The marketing is just pure fail right now.
Look at this website: http://www.anscamobile.com/corona/
–
Thanks for the link. I have forwarded this internally.
mike chambers
mesh@adobe.com
mikechambers
10 Nov 11 at 8:05 pm
@David
–
can you clarify the future relationship between flash pro and Edge. Are developers supposed to use Edge to develop content for html5 and then switch back to flash to make the same content to work reliably in older browsers. I can accept that moving to html5 is the way forward but if adobe wants to keep me as customer they could do a lot to make the transition easier and be clearer on the direction they expect developers to take.
–
We definitely want to make the transition easier (Edge uses a lot of the same metaphors as Flash Pro).
Let me ping them Edge team and see if they have any thoughts on your question.
mike chambers
mesh@adobe.com
mikechambers
10 Nov 11 at 8:08 pm
@David, this is Mark Anders from the Edge team. First, Flash Pro is a tool that is optimized for the Flash Player/AIR runtime environment, and Edge is a tool we’re building that natively targets HTML. We’re not building a single tool that targets both environments. We ARE looking at ways to have great workflows between both of them.
As to downlevel, we’re doing work to better support downlevel browsers as best we can, though it will not have the same level of compatibility as we’ve been able to achieve with Flash. Meaning you won’t simply write once and have it deploy everywhere reliably as you have had with Flash. We are targeting having it reliable for modern browsers, but IE8, 7 and 6 will be degraded in various ways.
We are looking into ways that we can take Flash output and convert it to HTML5 as well, so that is another direction that we’re enabling it.
So the scenario of how to support older browsers is something we’re working on, from both the Flash Pro and Edge perspectives.
Hope that helps!
Mark Anders
Mark Anders
10 Nov 11 at 8:29 pm
I also think it would be great to offer a simplified message for the masses explaining that AIR has become a focus (and why this is a good thing). Arguably, that is the message Adobe wanted/tried to put out- but many tech blogs seemed all too eager swoop in ‘for the kill’ for whatever bizarre reason. I swear if I read one more ‘Flash is dead!’ headline…
Folks are taking it upon themselves to create educational sites, i.e. http://www.thoughtsonflash.com . It would be great to have a single, clear, Adobe-created page- to help ease anxious (or confused) client minds as this transition occurs.
Greg Gavutis
10 Nov 11 at 8:59 pm
Sure hope Adobe does something about all the negative press Adobe and Flash has gotten. The PR release really did not help and has only hurt our industry. Sadly I think more people are jumping ship or already have.
While I applaud and appreciate your effort, I don’t think enough people are listening or actively participating in the community (especially the media that has ran with this story of doom and gloom).
Adobe directly needs to step up and clarify their position more assertively as well as address the rumors. Anything less will not be enough. ignoring it is not enough. And a small tip: Put the good news first: “Adobe focusing more aggressively on cross platform App development”.
-erik
erikbianchi
11 Nov 11 at 3:36 am
Hi Mike,
everybody here appreciates your efforts to communicate for the future of Flash.
What worries me the most is not if Flash will last 2 , 3 or 5 years, but if Adobe will keep the same communication strategy:
- not a word at max about giving up flash for mobiles ( there was even sessions for it!)
- not a even a word to the employees so that can prepare themselves.
- firing 750 people the same day.
Even if there is a strong roadmap for flash for the next two years, I will now take for granted that I can’t rely on this roadmap, not only because if major tech changes occurs meanwhile, but also because this is Adobe, a company that doesn’t have a “Steve-Jobs-best-sides” like CEO.
Let’s sing along
“I was looking for a
boris
11 Nov 11 at 3:39 am
I would just like to thankyou for attempting to restore some sanity and sleepless nights for the flash dev’s out there.
Maybe this can serve as some sort of lesson for developers to not get too tightly wound up about one language, and Adobe about how to release info and involve the community.
Flash has a great community which in my opinion is un-rivaled. Lets keep it that way and keep pushing the boundaries with innovative content, and Adobe with tooling to let us do that.
Matt Thomson
11 Nov 11 at 3:39 am
oops submitted by error so:
Let’s sing along:
“I was looking for a job, and then I found a job
And heaven knows I’m miserable now
In my life
Why do I give valuable time
To people who don’t care if I live or die ?”
Cheers
boris
11 Nov 11 at 3:42 am
I don’t see enough from Adobe that encourages me to continue investing in AIR for devices. It’s a shame too, because until this announcement, the progress being made with Flex 4 SDK, AIR SDK, and the AIR runtimes for devices, were looking really promising and looked like it was headed in absolutely the right direction. But from the announcement, AIR for devices, seemed to get just a passing handwave mention, and the message seemed to be that in a few years, it will be superseded by PhoneGap and its ilk. Combine that with the lack of any reaction from the Flex SDK and AIR teams following this announcement (maybe they were all sacked), and it would seem to be a dumb move to continue any more investment targeting AIR for devices.
anon
11 Nov 11 at 4:50 am
Cleaning up the code base on Flash Pro? WOOOOOOOOOOOOOOO!!!!!!!!!!!!! It has crashed on me ( on a mac ) at least 15 times in the last 3 days. It crashes almost every time I close it normally as well. I am very glad to hear this.
Shawn Makinson
11 Nov 11 at 6:17 am
You need to understand: “no Flash on iOS” could be changed in soon future. Android is growing up very fast and lot of people decide to Android only because it have Flash. So probably iOS could allow Flash. But Adobe destroy everything. Adobe lost trust of people.
The fact is:
- mobile is the future of www
- no Flash on mobile browsers = dead Flash
- performance of Flash on future mobile – no problem since there are still faster CPU
GREG
11 Nov 11 at 7:16 am
@boris
–
“I was looking for a job, and then I found a job
And heaven knows I’m miserable now
In my life
Why do I give valuable time
To people who don’t care if I live or die ?”
–
Not sure if that is completely on topic, but I approved it because I am a huge Smiths fan.
Also, I hope Im not getting trolled by a very good spam bot.
mike chambers
mesh@adobe.com
mikechambers
11 Nov 11 at 8:54 am
Thanks for the update Mike. Flash mobile gone – don’t care much. Not affected. Flash team gone – huge loss on a professional and personal level. Flash Pro moved over seas – sounds like the beginning of the end regardless of the new features for CS6. It’s been a long fun ride but this sounds very much like Adobe letting Flash die a slow death. Someone make some room on the shelf next to Director please.
I’m excited about Edge and evolving with the times. There’s a sentimental loss when it comes to Flash that I will eventually get over. Heck I can still use older versions if needed. I’ll mostly miss the camaraderie of the people that developed Flash and that post conference beer or 3 after FOTB and MAX. Realizing those days are over hurts more than anything. They gave what is otherwise just a software product a face, a personality. Suddenly, without them, it’s become all to antiseptic for me.
chris
11 Nov 11 at 10:08 am
good this news scared me because I’m starting with Flash to create mobile applications
jose rosales
11 Nov 11 at 10:26 am
How about officially bringing Easeljs into the fold, like phonegap. I know you personally are involved with Easeljs so get it done :).
Nate
11 Nov 11 at 10:48 am
It would be appreciated if Adobe could level with ActionScript developers about whether ActionScript has a future or not. As an ActionScript dev, with this move, you have substantially reduced the market addressable by my skills.
Edwin
11 Nov 11 at 10:54 am
[...] discussed the future of Flash Professional in a separate blog post yesterday, so I am not going go into detail on it here. As I stated yesterday, we are actively [...]
Clarifications on Flash Player for Mobile Browsers, the Flash Platform, and the Future of Flash at Mike Chambers
11 Nov 11 at 1:32 pm
@chris
–
Flash team gone – huge loss on a professional and personal level.
–
Its not
–
Flash Pro moved over seas
–
Team still based in San Francisco, with other members in different locations (which was the case prior to this week).
mike chambers
mesh@adobe.com
mikechambers
11 Nov 11 at 1:37 pm
@Edwin
–
It would be appreciated if Adobe could level with ActionScript developers about whether ActionScript has a future or not. As an ActionScript dev, with this move, you have substantially reduced the market addressable by my skills.
–
Info here:
http://www.mikechambers.com/blog/2011/11/11/clarifications-on-flash-player-for-mobile-browsers-the-flash-platform-and-the-future-of-flash/
mike chambers
mesh@adobe.com
mikechambers
11 Nov 11 at 1:39 pm
Thanks for the response Mike. Mind if I ask who is still on the team and will remain in SF? Being on the prerelease for a number of years and having been a sort of go-to resource for animation features, who still has an adobe badge these days? I realize you may not have the privilege of answering publicly, I just keep reading about how the entire US based Flash team got fired which makes me think:
1. Don’t believe everything I read
2. If its true what becomes of my own investment in the evolution of Flash.
It feels very fragile to me at the moment. As a user, I have a lot of questions and concerns about the future of Flash and don’t know who remains in the Adobe building for me to ask.
chris
11 Nov 11 at 2:51 pm
@Chris
Well, you can either choose to trust me or not. Ultimately, that is a decision you will have to make.
I have tried to be open and honest with the Flash community on this, but, at the end of the day, what you choose to believe is up to you.
I will say though, that I dont think I would have much a career in the Flash community and at Adobe if I had made a habit of just lying and misleading people. In fact, I think I have my current position because I have done the opposite of that.
mike chambers
mesh@adobe.com
mikechambers
11 Nov 11 at 2:59 pm
[...] that Flash is less relevant. It’s just Flash Mobile, not the many other aspects of Flash. Here is a good roundup of what [...]
This Week in InDesign Articles, Number 78 | InDesignSecrets
11 Nov 11 at 3:04 pm
I wasn’t trying to say you were lying. My bad – it was my wording that was confusing. I was truly asking who is left on the team in San Fran. I have had a pretty close relationship with the Flash authoring team for several years and to hear most of the team as I used to know it is now gone makes me question if I have any more influence on the real world usage of Flash.
I have always respected your honesty – that was never in question. My apologies for being misleading.
chris
11 Nov 11 at 3:11 pm
Mike,
Been on a HDslr and stills shoot in the eastern Sierra, trying to catch up, saw the “panic” attack thread in a CreataSphere news letter then read the press release which could have been rewritten one more time, before the positioning. You likely had NO input on the PR department’s mission and could possibly have reduced the shell shock had they asked.
Alas, it implied that iJOBS prevailed in some fashion from the crypt in the bowels of Cupertino’s Citadel and the I told you so fanboi’s and fangurls are delightfully stomping their collective sour grapes captive to the touch screen culture. (There is life beyond a F^&**#% cell phone, and no, despite the reality of html5, no one will be editing a feature film on a touch pad, for major release anytime soon).
Not to say you didn’t try to assuage the Adobe user community with some of your @ responses, but folks need to understand the dynamics of business, as it relates to market principles.
I don’t believe there were ever promises made last month beyond Touch Apps, AIR and Flash Pro to negotiate the handshake required to stay on one screen for pads and phones.
So why the hue and cry?
Oh, layoffs…hmm…always do happen after consolidations and buy outs, stop whining.
I suppose had I not been laid off to make way for the boss’s daughter, who was being laid off from a bank mortgage division, that even owning CS5.5 PP, would not be a reality. Cloud, silver lining holding on lines two and three.
It does appear from your input above, that the development community and dare we say CREATIVE folks who do support Flash are not being jettisoned or tossed out, babies from bathwater, after all.
Hence a caution to the folks writing the scripted and proofed content, lesson learned then, bad press is self created and there is such a thing after all.
Thanks for sharing, after reading every comment; I resorted to the Evangelist blog to see what’s really going on.
Now, if you folks would simply buy Cineform from the camera kids, things would be blissful.
Many thanks,
Rob
Rob Manning
11 Nov 11 at 5:38 pm
So to save me some time, will someone just tell me if in a few years I can still buy Flash for my desktop computer and make animations with it (or just buy flash, for that matter)?
No-One
11 Nov 11 at 10:47 pm
RE: “We are looking into ways that we can take Flash output and convert it to HTML5″ I think you really mean convert to JavaScript. But what happens if people start turning “off” JavaScript, especially for security reasons, in their browsers, tablets, and phones? Where will the mighty HTML5 be without the crutch of JS running?
I think this is what a lot of AS3 developers are miffed about… being forced to go back to 90′s JavaScript coding.
———
No, I did not mean just JavaScript. There are a number of relevant tetchnologies including JavaScript, SVG, CSS3, etc…
mike chambers
mesh@adobe.com
RazorX
13 Nov 11 at 10:12 am
Flash’s ubiquity in the last decade or so, and the enormous amount of flash engineered content living with so many companies is something to consider. They can either hire someone to re-invent the wheel, or they can hire someone for half the scope in transitioning heavy flash dev to HTML5( there’s a lot of opportunity in that). Skill sets change, and technology progresses; keep up to date, challenge yourselves and be part of evolution of the web and all that it encompasses.
Flash Engineers are typically both technically and creatively minded, which is combination that only increases in demand in world where UX and Interactivity dominates everything. If what defines you as a professional is knowledge of one tool set, then regardless of your marketability, based on the ebb and flow of industry factors you’re putting your eggs and your ego in the wrong basket.
Flash is a great technology, not for what has been under the hood, but for the creative genius its attracted in pushing boundaries, not due to its inevitable sustainability or demise.
~mike
michael berendsen
13 Nov 11 at 2:53 pm
Well, it certainly is good news that Flash Authoring is still around. To me, that is more important than Flash Player. Where there can be alternatives when it comes to output format (none stood up to Flash Player though), the Flash authoring tool itself is pretty much one-of-a-kind.
Still don’t like how it’s sounding like though. Flash looks a bit like GoLive to me now, “we’re still making new versions of it while encouraging you to move to a partial-alternative (Dw) that can’t do everything the original does,” and one version (GoLive 9) later, it got EOL’d.
nocturnal YL
14 Nov 11 at 7:19 am
I vote Adobe produce game creation software so people like me wont get so frustrated and disappointed with Flash’s inability to create stable action games without a computer science degree.
Kev Man
14 Nov 11 at 2:12 pm
I think Adobe should make exporting html5 together (or even without) swf a priority for future Flash Professional development, but using the same interface with minimal mandatory changes, also including converting Actionscript to Ajax. I love Actionscript, and I don’t want to start learning another language.
Thank you.
–
This is something we are working on in Flash CS6 (exporting content and animation for running in Canvas). We also are working on Wallaby which provides more advanced Flash export.
This is an area we are spending a lot of effort on right now.
mike chambers
mesh@adobe.com
–
ahmad
15 Nov 11 at 9:22 am
this is something I lonng to ask you. I tried reading more comments &your Entry and i hope its not dumb. But, could you see Flash Pro being a “good Window’s browser(I am also a mac fan, but eiiii?) Game maker. has flash not lost its esteemed Leaps Forward as a public (even offline, somehow?) greatly esteemed gamemaker, Loooking what they’ve done already!
no more -what ifs -questions. Have a good time in Tokyo! Cheers
—-
Yes. This is one of the areas (building games) that we are focusing on.
mike chambers
mesh@adobe.com
—-
Dave V,
15 Nov 11 at 4:52 pm
Wondering if there are any plans to allow for easier upgrading of the SDK that compiles apps. Right now it’s a bit annoying to update for CS 5.5 (although better than previous versions) This of course would include updating AIR dialogue boxes with new fields, checkboxes, etc…?
Phil
16 Nov 11 at 8:01 am
Well I used to be a Flash developer for web… But that doesn’t concern me so much now. Im now a software developer for a company that make jukebox’s. Im extremely proud that I was able to use flash alone to create the interface for it. Its never let me down once. I hope that adobe carry on developing air and the flash platform with as much enthusiasm as they always have done. You guys have put far to much work into a product to let it go by wayside now… I’m sure you wont.
Aidan Mack
16 Nov 11 at 10:08 am
just want to say to Flash/Flex Developers to think beyond the Flash Player..!
Awais
22 Nov 11 at 10:25 am
HTML export to me seems like it might be clunky if not done right. Does anyone know if adobe will be using a JavaScript framework like jquery or making their own proprietary JavaScript files to assist with the exported code?
Ducky
23 Nov 11 at 2:12 pm
I am a Flash animator and I feel adobe has ignored us in their development cycle for web developers and in the process broken some of the best tools. I must make a decision on whether to jump ship to Toonboom or stay with Flash. I am concerned whether Adobe will address our concerns such as their horrible export to Quicktime, symbol cycling and easier import of multiple character libraries plus sound issues.
Does Adobe plan to pay attention to us?
pam
26 Dec 11 at 11:14 pm