40
votes

I've tried looking everywhere for a concise list of the advantages and disadvantages of using Flex vs. Flash.

Coming from a programming background, I absolutely love Flex. It's easy to pick up, and since it can use flash classes, why would I want to use Flash without flex?

Flex:

Pros:

  • good for RIA development
  • provides many user-input options out of the box
  • Build in lay-outing system
  • the MXML is easier for non-programmers
  • You can quickly combine components to create small applications
  • components can provide an advantage in large-scale projects because of their modular nature.
  • can be developed using linux
  • has a nice component lifecycle for validation, etc.

Cons:

  • increases the size of your .swf
  • Customizing the look of components can take a lot longer than anticipated, depending on the visual style you're looking for
  • when you find out you need a custom component that doesn't exist, you might need to go back to Flash to do the real programming work and packaging of the component
  • The "flexibility" of Flex means you will be reading a lot of documentation
  • Bugs in the Flex framework
  • You eventually will need to compromise with the architecture of the Flex framework

Flash

Pros:

  • good for making movies/animations
  • Timeline can be easier for designers/animators to conceptualize
  • when working from scratch, provides a great deal of control.
  • easier for someone with a programming background
  • You can program whatever you like; no compromises with existing frameworks

Cons:

  • only provides basic user input (text box) out of the box.
  • timeline can be daunting for programmers (although you can quite safely ignore it)
  • Development of certain types of applications will be slower than with Flex
  • can't be developed using linux
  • user input validation must all be handled in the code. No built-in validation.
  • need to implement your own lay-outing system

Please correct me if I missed anything said so far.

12

12 Answers

17
votes

Flash and Flex both use the same underlying rendering engine, just with different front-ends. Flash is better suited for making movies and animations. Flex is better for application development.

9
votes

From a programmer's viewpoint, the big difference between Flash and Flex is not so much which IDE/application you use for programming, but whether you program in ActionScript (AS) only, or use the Flex framework and MXML to program your applications.

I would say pure ActionScript is better for programming (whether you use Flash IDE or Flex IDE is not that relevant), and MXML is better for non-programmers to combine the components programmed in AS.

I would add to your list these pros/cons:

Flex:

Pros:

  • Easier for non-programmers to get into application development
  • You can quickly combine components to create small applications
  • Components can provide an advantage in large-scale projects

Cons:

  • Customizing the look of components can take a lot longer than anticipated, depending on the visual style you're looking for
  • When you find out you need a custom component that doesn't exist, you might need to go back to Flash to do the real programming work and packaging of the component
  • The "flexibility" of Flex means you will be reading a lot of documentation
  • Bugs in the Flex framework
  • You eventually will need to compromise with the architecture of the Flex framework

Flash (or Flex IDE in ActionScript project mode):

Pros:

  • Easier for someone with a programming background ;)
  • You can program whatever you like; no compromises with existing frameworks

Cons:

  • Timeline can be daunting for programmers (although you can quite safely ignore it)
  • Development of certain types of applications will be slower than with Flex

In short: pick the right tool for the right task.

8
votes

Flex is a library of code written in ActionScript3, so it adds lots of capabilities and standard-library-like stuff to Flash. The downside is that it a is a huges amount code that gets included into your application. If you use any Flex at all in your app, the download size of the SWF goes up by 100's of K.

If your application has any kind of user interface widgets, then you almost have to use Flex as Flash itself only has the most basic things like text boxes. Flex has a whole XML GUI with layouts, data binding and XML setup etc.

Doing that in flash, you end up having to write from scratch things like list boxes...

6
votes

In my opinion, the most important feature of the Flex framework is the component lifecycle, which provides a really elegant model for validation/invalidation of properties, component size, and hierarchical rendering.

The benefit to developers is that it creates discrete application phases for business logic and rendering, avoiding expensive geometry & rendering code until the last possible moment before drawing a frame.

Here's a really good presentation, explaining how it works:

http://tv.adobe.com/#vi+f15384v1002

The model is so well-designed that the component lifecycle remains almost entirely invisible during the majority of Flex development, when you're using the framework default components and containers. You only need to learn the inner-workings when you start developing your own components.

Developing in the Flash environment, or in pure Actionscript, you don't get any of that. Anyone developing pure AS3 applications either needs to code very carefully to separate business logic from rendering, or will suffer severely decreased performance.

4
votes

[...] why would I want to use Flash without flex?

Flex is a new product, whereas Flash existed from the Macromedia days. Designer, animators and most anybody who is not brought up on a staple diet of programming education will probably find Flash easier to master than most other such solutions.

3
votes

Target is different. Flex is more dedicated for programmer while Flash is more friendly to Artist / web designer.

3
votes

Flash is the IDE used (generally) to create animations and things that work well on a timeline.

Flex works better for creating internet applications which have interactions more akin to a desktop.

Why use Flash? Well, if you need to do something more specifically attached to a timeline, of course!

2
votes

I see Flex as more of a solution for doing RIA applications where you need to develop application based solutions. There's quite a lot you get right out of the box with using Flex but it also comes at a price in terms of file size, granularity, etc.

If on the other hand you are working on a totally custom solution such as a game then perhaps Flash is the way to go because you can start fresh with a blank canvas. Many people still use Flash because they don't need all the app based bells and whistles of the Flex platform.

2
votes

I like the freedom of Flash, and its really simple to embed assets in Flash, a little more confusing to do in Flex.

One thing that I love about flex is the ability to make a fluid application with minimal effort. Which would take forever in Flash.

Anything you can do in flex you can do in flash, just may take a lot longer to do. You can't do everything in flex that you can do in flash though.

Flex takes care of all the UI programming for you and lets you focus on the business logic, with flash you will spend a majority of time programming the UI.

2
votes

You can develop Flex applications under Linux easily but with Flash you simply can't.

1
votes

Another solution that was not suggested at here, will be to use them both. You can add flex components to flash movie clips using ContainerMovieClip. And you can add flash movie clips to flex components using SpriteVisualElement. Another thing that wasn't mentioned was lay-outing your application. It will be flex pros against flash disadvantage, because you got build in flex lay-outing system. But again when you are using them both, you can layout your movie clips with flex lay-outing system.

Also flex become Apache top-level project. And it become more and more excepted by the community now.

0
votes

Flash and Flex are 2 complete different things, one is a design tool with support for action script, the other one is a framework that also has action script but is maily built around MXML which is a XML based UI definition "Language".