The Flash Platform is dead! Long live the Flash Platform!

Adobe announced, or TechCrunch announced, or Adobe will announce… um… anyway, there’s this brand new thing called the Flash Platform now on Adobe.com:

http://www.adobe.com/flashplatform/

The Adobe® Flash® Platform is an integrated set of technologies surrounded by an established ecosystem of support programs, business partners, and enthusiastic user communities.

This is not to be confused with the Flash Platform that was announced by Macromedia several years ago. Not to be confused, because it’s the same thing. Which is good, because I’ve been running the Boston Flash Platform User Group for 3 years now. Would be a shame if that meant something else now.

Some have reported that Flex is changing its name to the Flash Platform, but I don’t really read it like that. In fact, this chart shows things very clearly:

I have to say though, that I’m really disappointed that Flex Builder is still Flex Builder. It’s SUCH a misnomer. As Chuck said in the link above:

The product we knew as FlexBuilder has really just been a much more code-friendly way to build apps for Flash. This name-changing effort will clear up a lot of confusion, especially to those new to Flash that didn’t quite understand how/why two differently named products ended up producing the same thing — a SWF.

I wholeheartedly agree. I spend many, many, MANY hours a week using Flex Builder and the last time I did anything with Flex itself was… I don’t remember. Some time this past summer I guess. It really should be Flash Builder, Flash Platform Builder, Adobe Builder, something else. I mean, look at that diagram above. It doesn’t make sense at all. Flex Builder is the tool, tied to the Flex Framework by name. But it also does just about everything in that Client box too. Well, we’ll see what they actually call it when Gumbo goes live.

This entry was posted in Flash. Bookmark the permalink.

28 Responses to The Flash Platform is dead! Long live the Flash Platform!

  1. Seb says:

    I don’t really get it. We all knew already how all these Adobe product relate to each other. All I can make sense of from this, is this is just like a pretty poster or something. They haven’t made anything new, just designed a flashy way of explaining their products.

    Or maye im missing the point here? Rather confusing, if you ask me! 😀

  2. Tyler Egeto says:

    I agree, I don’t get it. As far as the Flex/Flash confusion, in my opinion, that mostly stems from Adobe itself. They like to put out pres releases like this one:

    “Adobe has joined the Zend Framework project and will work with the framework community to optimize communication between Zend Framework and Adobe Flex applications. Adobe has contributed support for the open, binary AMF format for exchanging data between Flex applications and PHP applications to the Zend Framework.”

    No wonder there is so much confusion around this. They say Flex an awful lot when the should be saying ActionScript, or the Flash applications.

  3. kp says:

    “They say Flex an awful lot when the should be saying ActionScript”

    Exactly.

    I know they need to market Flex, but there’s way too much fixation on it. And it is what is driving major confusion.

  4. kp says:

    For example. I constantly have this conversation with people:

    Them: Do you use Flex?
    Me: No.
    Them: So what do you code in? Flash Develop, FDT, the Flash IDE?
    Me: I use Flex Builder.
    Them: But you just said you didn’t.
    Me: I use Flex Builder, but I don’t use Flex.
    Them: Huh?

  5. Matthew Fabb says:

    I definitely think Flex Builder should be renamed. Then again, I think the Flex brand name should have been dumped with version 2.0, to avoid confusion with the server product that was Flex 1.5.

    Why not call it “SWF Builder”? Since that’s what you are doing, building SWF files using either the Flex framework or pure ActionScript. However, I imagine that Adobe marketing team might think that it’s not catchy enough.

  6. kp says:

    But you aren’t even necessarily building just SWFs. You might be building AIR apps (again with or without Flex), which do contain a SWF, but the real product is an .air installer file.

  7. Jay A. says:

    Guys, are you not being too innocent here?

    So you have all this $$$ comming to Adobe from Flash Professional licenses and you expect Adobe to put a huge banner at the door basically saying: – hey you can now build anything with this new “Flash Builder” that you can build with Flash Professional and guess what, it’s totally free so you should actually think to or three or four times before you decide to send us money.

    Lol. Not likely to happen anytime soon 😛

  8. kp says:

    Jay, Flex Builder is not free.

  9. RyanP says:

    They could always just build a better development environment within Flash and keep Flex for Flex/MXML stuff. Although I have felt somewhat confused in where to develop and when to you Flex for Flex.

  10. Mickey says:

    I think I like flex builder more than bloated flash IDE. It should be thermo, ekhm… Flash crappylist and flex builder.

  11. Alan says:

    @kp
    He didn’t say Flex Builder was free, I beleive he was alluding to the fact that Flex is free – which it is.

    Voila! Adobe’s confusing nomenclature in action.

  12. Matthew Fabb says:

    kp: “But you aren’t even necessarily building just SWFs.”
    True enough, even through .air files contain SWF’s not everyone knows that and a name like SWF Builder is likely to cause some confusion when it comes to AIR development. I guess that leaves some sort of name with the word ActionScript in it (ActionScript Builder? ActionScript Coder? ActionScript Developer?), but once again I think Adobe marketing would want something that was more catchy.

  13. Mike Britton says:

    How about renaming it ‘FlashDevelop’ and taking it out of the Eclipse platform?

    Flexbuilder is so slow it discourages use. Give me a new, extensible IDE sans Eclipse and I’ll gladly buy it.

    Sorry, don’t mean to be a hater but I’m sure Adobe could cook up a nice IDE that integrates more intuitively with its products.

  14. Stu says:

    Ok I’ll be the first to admit that I’m completely confused! I still develop using Flash and it wasn’t until September at FOTB08 that I was introduced to the wondrous world of flex builder…or was it flex?! I was planning to start using it asap. I now have no idea what is going on!!

    Will somebody please clear up the difference for me?!!

  15. Ozren says:

    What? Are you all stupid or what? If product names confuse you, how the hell do you guys even make a decent peace of software in those same products? What will be next then, namespaces confuse us, name them adobe.org.with-this-i-can-make-text.

  16. kp says:

    Yes, we are all so stupid, I don’t know how any of us make a peace of software. Piece, bro!

  17. Matthew Fabb says:

    @Ozren
    I and others who use these products every day have no problem with the branding. However, we all have to work with people who aren’t familiar with these products who get confused. From clients, back-end developers, designers, project managers, HR and to even friends and family when you try to explain to them to what you do, all get confused with bad branding. I still come across backend developers who confuse Flash SWF files for Shockwave files. Then even more important, it confuses people who are new to the technology, and to some who Flash development is just a small bit of their job description and skill set. All of this could be cleared up with better branding.

  18. Steven says:

    Rename Flex Builder to ActionscriptWeaver. Problem solved :).

  19. @Matthew Fabb – indeed, the official launch of the Flash Platform appears to be nothing much more than a re-branding of everything that communicates or plays a part in the current (and to an extent, future) Flash ecosystem. I’m not sure how coming up with a high level umbrella term will clarify the low level conversations that go on daily in the workplace that users are mentioning here.

    Time will tell I suppose… One things for sure, that Flash Platform image looks impressive!

    @Ozren – I kinda take your point, but you probably could’ve pieced it together a bit more eloquently 😉

  20. I must be blind, or have I seen the light? The diagram, even the naming/branding, actually make perfect sense to me! Once I’d found out WTF Flash Catalyst is…

    (that’s actually the whole point of my post, rest is just drivel, but more fun than working…)

    As a Flash head, the Flex name has stood for “Flash for serious programmers, who vowed they would never touch a timeline with their bare hands.”
    In that respect it’s been a huge success, for what essentially is still just Flash. Java programmers see Flex as an answer to their dreams (or Swing nightmares) where Flash was never on their radar. For me going from flash (v2) animator to Flex developer it’s meant a learning curve like Kilimanjaro, but it’s (almost) all good. I was an Adobe sceptic when they took over, even to the extent of resigning as UG manager, but having done my first projects with CS4, it has to be said they’re strategy is quite brilliant (AS editor in Flash CS4 still blows, but hey, that’s a tradition. Give me some shortcuts!).
    This diagram is meant to clear up the ambiguity. Like I say, it works for me, and will hopefully work for giving an oversite of “the .swf ecosystem” for newbies and customers aswell. No one ever asked me in real life to explain the difference between Flex Framework, Flex Builder and Flash (it might be my deoderant?) but If they ever did I can now send them to that link.

    For most people I meet, who are *either* designers OR developers, it’s *either* Flash (via IDE + possibly fave text editor) OR Flex (with Eclipse or Flex Builder). If you use Flex Builder without ever touching the Flex framework, then I would suspect you’re one of a minority of hyperFlashers (or hyperFlexers, your choice!) that work equally with design and programming and can weld together both approaches. I know I can’t, I still prefer FlashDevelop for Flash projects.
    Honestly I feel the branding/naming fits well over the demographic. If you’ve got long hair and pale skin, choose all things Flex, if you’ve got a goaty choose Flash, if you want to use the SDK to compile swf from another programming environment, what the hell are you doing out of your cage, get back to work! (I know this is an unforgivable and gross generalistion, I actually once saw a designer without a goaty).

    @Matthew Fabb – ‘I still come across backend developers who confuse Flash SWF files for Shockwave files’ – and after you’ve explained they invariably ask ‘what does SWF stand for?’ (bugger! :O)

  21. Justin says:

    Steven: “Rename Flex Builder to ActionscriptWeaver. Problem solved :)”

    Haha, or how about “AShole”! – Which should imply that I agree with Mike, ‘Flex’ is great but the weight of Eclipse that Flex Builder carries around with it has made me steer clear of it whenever possible, especially after using an IDE like FlashDevelop which has everything but design view and feels light and breezy 🙂 I’m sure Adobe could manage a fresh approach to the editor.

    I see the reason behind keeping developer-centric and design/animation-centric applications separate, but the current setup certainly can seem a bit convoluted.

  22. Lee Brimelow says:

    Adobe realizes that the name Flex Builder doesn’t appropriately describe what it is actually used for. Unfortunately I can’t say anything more, but I think you can read between the lines ;-).

  23. kp says:

    oh boy Lee, you let the cat out of the bag! 🙂

  24. Lee Probert says:

    I just wish the’d hurry up and decide what they’re releasing and then package up a decent developers/RIA package for CS4 that should include Flash, Flex, Catalyst, Fireworks and Dreamweaver. I need to buy the software soon but you know what’s going to happen … {sigh} … anyone from Adobe know if they plan on offering such a package in the near future?

  25. Lee Probert says:

    And another thing … Adobe should just develop and market ‘Flex’ or whatever they want to call it as an Eclipse plug-in and SDK and concentrate on making it as impressive as FDT. This would clear up the confusion amongst people about what the hell it is in relation to Flash. Calling Flex Builder a piece of Adobe software is an insult to the Eclipse foundation.
    Catalyst/Thermo should be integrated into Fireworks too.

  26. Martin says:

    I dont think the slowness of FlexBuilder is caused by being based on eclipse, after all I can run countless other setups in eclipse and they have no speed problems at all (JDT, CDT, EMF, PyDev, DLTK, PDT etc..) the problem is both the compiler and how its integrated.

    If you turn off automatic builds and setup a keyboard shortcut for build project then its not so painful, well, apart from when you want to launch an app and FB triggers a build anyway and sometimes hangs for about 30 seconds wondering wtf its doing.

    Im really hoping FB4 (or whatever it’ll be called) and the associated SDK will have dealt with those issues.

    like Lee said, its giving Eclipse a bad rep.

  27. you heard it here first: I predict Flash Catalyst will be integrated into Flex Builder–basically the design view you need. If it does come out as a separate product I think it’s sort of a mistake (though maybe the only option) because it just means that many more apps to learn.

  28. Name it Flesh! (Flash-Flex) 🙂 ..or Fleshair?
    Anyway name it whatever you want just don’t make 4000 versions like Pro, Standard, Home edition, Office edition, WC edition.. Oh wait.. thats a policy of another company. Mmm damn.

Leave a Reply