• Use runtime fil­ters spar­ingly. If you can turn it into a ras­ter graph­ic with those fil­ters, it will likely be a smooth­er anim­a­tion. This will be a del­ic­ate bal­ance between file size and performance
  • Use motion tweens instead of shape tweens whenev­er possible.
  • Don’t have trans­par­ent things on top of trans­par­ent things. When trans­par­en­cies over­lap, the pro­cessor usage multiplies.
  • Keep your frames per second at or below 30. I’ve seen many applic­a­tions try­ing to run at 60+ fps. I usu­ally set my applic­a­tions at around 24.
  • Use eas­ing only where you need it.
  • Learn about cacheAs­Bit­map. This can speed things up or make them slower, it depends on the con­text. If you have an anim­a­tion, keep cacheAs­Bit­map as false, the cached bit­map will have to be regen­er­ated every time the anim­a­tion changes, so this isn’t worth it. How­ever, on a vec­tor graph­ic that does­n’t change with­in itself, cacheAs­Bit­map might be a good choice.

via adobe.com