Accessibility

Flex Article

 

Flex Application Performance: Tips and Techniques for Improving Client Application Performance


Table of Contents

  1. Introduction
  2. Architecting Flex Applications That Perform Well
  3. A Note About Flash Players
  4. Using Layouts, Hierarchy, and Containment Properly
  5. Examples of Common Container Redundancies to Avoid
  6. Using Deferred Instantiation to Improve Perceived Performance
  7. Handling Large Data Sets
  8. Playing Complex Effects Smoothly
  9. Achieving Great Performance with Runtime Styles
  10. Using Dynamically Repeating Controls for Better Performance
  11. Improving a Repeater Object's Performance
  12. Improving Performance of Charting Components
  13. Performance Tuning and Profiling Your Own Flex Application
  14. Using Runtime Shared Libraries (RSLs)
  15. Feedback and Support
Comments

Architecting Flex Applications That Perform Well

Ideally, performance is a topic that is in the back of your mind during every step of the development process—from application design to implementation and deployment. When creating a Flex application, think through the choice of containers and components that you use to ensure that the code is maintainable, organizationally clear, and performs well.

You can use the Flex navigator containers (Accordion, TabNavigator, and ViewStack) across all application types to organize content. The navigator containers organize content in a way that:

  • Minimizes users' confusion
  • Exhibits good user interface (UI) design principles for browser-based applications
  • Aids performance

More specifically, Flex navigator containers help you organize content easily into different child views and control the creation of these views with deferred instantiation. Organizing content into these child views spreads out creation time for each child view because Flex creates a specific child view the first time a user requests that view. The "Navigator Containers Have Built-in Deferred Instantiation" section later in this article explains why Flex navigator containers perform better with deferred instantiation and how you can leverage deferred instantiation to make your application more robust.

Dashboard-style applications have also resulted in successful deployments. This type of application organizes content into modular, self-contained views that offer a more intuitive approach to application organization. Like the navigator containers, this approach performs well because it organizes complex views, with Flex creating them when the user drills down. Flex does not have to size, measure, and draw the views in the background, so it creates the selected view more quickly.

Page 2 of 12
Previous Page
Next Page