Adobe gives web designers more power with Flash Catalyst

With two new products available in beta testing today — Flash Catalyst and Flash Builder 4 — Adobe is hoping to reinvent the way that websites and applications are built in the Flash format.

Flash sites (which may be most familiar to your average web surfer through the fancy sites that Hollywood studios put up to promote movies) are often the richest in multimedia and graphics, and they also tend to be carefully designed. However, Adobe Platform Product Manager Steven Heintz tells me that the process of designing a site (i.e., creating its look), and especially of communicating that design to the developer who actually builds that site, has some problems. Designers create a set of images, animations, and text instructions, and then a developer has to translate those materials into a real website.

With Flash Catalyst, however, designers can show a developer exactly what they have in mind, because they basically create the websites themselves. They create images in Adobe Photoshop or Adobe Illustrator, then import them into Catalyst, where they become standalone web pages. Then designers can use a fairly simple drag-and-drop interface to build in all the other interactions, like having different buttons light up when moused over, or specifying the transition between two different web pages. When they’re done, they have the equivalent of a basic web application.

After that, a developer can import the Flash file into Flash Builder 4, where they add more technical depth (if necessary), such as connecting the site to databases or other web services. But since they’re working from an already-functional Flash file, rather than a set of instructions, they can focus on the technical backend, rather than trying to interpret the design as well.

By the way, even though it’s numbered “4″, you may not have heard of Flash Builder before. That’s because it was previously called Flex Builer, but Heintz says that name has been causing some confusion about the relationship between Flash and Flex. Now Flash applications are all built using Flash tools (Flash Builder, Flash Catalyst, Flash Pro), and Flex only refers to the development framework. Okay, so that’s still a little confusing — but not as much as it used to be.

[photo:flickr/pedrosimoes]

Next Story: MashLogic adds funding, About.com founder, Twitter
Previous Story: Nvidia trumpets success of its Tegra cell phone processors

Bookmark and Share

Tags: ,

Photo of Anthony Ha

About the Author, Anthony Ha

Anthony is VentureBeat's assistant editor, as well as its reporter on enterprise technology, cloud computing, and tech policy. Before joining VentureBeat in 2008, Anthony worked at the Hollister Free Lance, where he won awards from the California Newspaper Publishers Association for breaking news coverage and writing. He attended Stanford University and now lives in San Francisco. Reach him at anthony@venturebeat.com. You can also follow Anthony on Twitter.

  • Albert Francis
    I keep thinking to myself: Will Adobe really miss the HTML5 train with all this Flash/Flex stuff? I understand they want to control the internet with their own technology, but the future is not headed in that direction and Adobe's very comfortable position with Flash will soon be seriously challenged with next generation browsers that will support HTML5.

    Wake up Adobe!?
  • Brandon
    So is this basically their answer to Expression Blend for Silverlight design?
  • flashlight er... silverlight
    OMG - yeah and The Beatles' Help was a response to the Monkees' Head...
  • Oh snap!
  • It's a good news for developer, who can import the Flash file into Flash Builder 4.
  • Flex is not "basically the development model that people use to build Flash applications". It's a framework with: (1) form like controls, (2) charting, (3) data handling, and (4) network communication capabilities, etc. Think of it like the Spring framework for Java development. You don't have to use Spring when using Java but it's fairly common to do so for certain types of applications. Similarly, Flex is one option for building Flash applications, but it is possible to build Flash applications without using the Flex framework. Flex is particularly good if you are building anything that works with data. But it's probably overkill if you are doing a media oriented site/application. The IDE that used to be called Flex Builder and is now Flash Builder can be used to build non-Flex applications and that's why they renamed it. As you point out, it clears up some confusion.

    Now, if you want confusion, the name of the Flex SDK is still confusing. It is essentially two things: (1) the compiler you use to convert your Flash or Flex designs into a form that can be run by the Flash player, and (2) the library files for the Flex framework. You can use the Flex SDK to build Flash applications that do not use Flex at all! These probably should be separate packages. One entitled the Flash SDK and the other entitled the Flex Framework.
  • Ah, that's super-helpful, thanks. I'll try to clean up the language in my post to make it more accurate.