
Motion has been a key element of Adobe Flash since its very beginning. The ability to animate objects on the web is integral to the technology and was originally one of its main selling points. As discussed in Designing for Flex – Part 1: Overview and discovering Flex, Flash originally used its animation capabilities to tell stories, whether to teach, to sell, or to entertain. But with Flex, the Flash platform has moved into application design, bringing all the communicative power of its motion technology with it.
Unfortunately, due to some high-profile mistakes, motion has received something of a bad reputation in application design and development circles. I say "unfortunately" because, when used properly, motion can be a powerful tool for making applications more useful, usable, and desirable. Using motion, you can eliminate the jerky jumps from screen to screen that disturb and deeply disorient users. However, improper use of motion will distract and annoy users, impeding them from reaching their goals.
This chapter covers:
The Designing for Flex series includes the following articles:
I suggest that you read the previous parts before proceeding with this part of the series.
Download all parts of the FIG series as PDF files that you can print and read offline: adobe_flex_interface_guide.zip (ZIP, 5.7MB)
This content is a public draft. Please give us feedback in the Flex Interface Guide Forum.

This work is licensed under a Creative Commons Attribution-Noncommercial 3.0 Unported License.
Rob Adams works for Adobe Systems, Inc. in San Francisco, California. He started at Macromedia, Inc. in 2004 and has worked on the Flash authoring tool, Flash Player, and Fireworks, but nowadays works primarily on the Flex product line. He is involved with the design of the core framework itself as well as the designer/developer tools such as Flex Builder and Creative Suite. Although his primary focus is on design research, he also does some design work, promotes sound design practices both within Adobe and without, and makes himself a general pain in the necks of the designers, product managers, and engineers he works with.