Adobe Certified Professional - Adobe Animate common mistakes
Adobe Certified Professional - Adobe Animate · Understand the traps and how to avoid them.
Starting a new file with whatever document type the New Document dialog already shows, then discovering at delivery time that the client needs HTML5 Canvas rather than ActionScript 3.0.
The dialog pre-selects the last-used preset, so candidates click Create without reading the Document Type list and only notice the mismatch when publish options look wrong.
What to do instead
Before drawing anything, open File > New and deliberately choose the type that matches the delivery target, then confirm it in the Properties panel's Target field while nothing is selected.
Drawing and importing all artwork first, then changing stage width, height, frame rate and background colour at the end.
Stage settings feel cosmetic, so they get postponed; resizing later shifts every object, tween path and registration point and forces rework.
What to do instead
With nothing selected, set stage dimensions, background and frame rate in the Properties panel before importing art, and record the required values from the project brief in a text layer or notes panel.
Dragging imported artwork straight onto the stage and copying it for each use, leaving the Library almost empty and the file bloated.
Dragging files from the desktop onto the stage is quicker than importing to the Library, and the duplication only becomes visible as file size at publish time.
What to do instead
Use File > Import > Import to Library, drag instances from the Library panel, and convert repeatedly used art into graphic or movie clip symbols so each asset is stored once and updates everywhere.
Importing print-resolution bitmaps (300 dpi, CMYK) supplied by the client and simply scaling them down on stage.
Candidates reuse supplied assets without checking pixel dimensions or colour mode, while Animate works in RGB at final on-screen size.
What to do instead
Resample or export bitmaps at the pixel size they will occupy on stage and convert CMYK to RGB before importing, then verify width and height against the stage in the Properties panel.
Selecting an instance on stage and editing it while intending to change every occurrence, or double-clicking into a symbol when only one instance should change.
The Property inspector and the double-click gesture both accept edits, so it is easy to lose track of whether you are changing an instance or its symbol master.
What to do instead
Select the instance for instance-only attributes (alpha, tint, instance name); double-click to enter symbol edit mode for changes that must appear in all instances, and check the breadcrumb bar above the stage to confirm which context you are in.
Losing track of which layer and frame is active and drawing on top of an existing tween span, so new strokes get absorbed into the animation or disappear.
Frames on adjacent layers look alike when the playhead sits mid-timeline, and the subtle highlight on the selected layer's span is easy to miss.
What to do instead
Lock finished layers as you complete them, insert a new layer above the animation before drawing, and read the layer name and frame span shown in the Timeline header before committing a stroke.
Creating a motion tween on a layer holding two or more separate objects, or drawing extra shapes inside a span that already has a motion tween.
A motion tween animates one symbol instance per layer; Animate quietly converts the extra art into another tween or drops the tween, so the problem shows up only during playback.
What to do instead
Convert the object to a symbol first, give every animated object its own layer, then right-click the frame and choose Create Motion Tween; add any new artwork on a fresh layer.
Applying a shape tween to grouped artwork, a symbol instance, an imported bitmap or live text.
Shape tweens interpolate raw vector outlines only, so the frame span turns dotted and the published animation shows a static object instead of a morph.
What to do instead
Select the art and use Modify > Break Apart repeatedly until the Properties panel reports a shape rather than a group or symbol, and break text apart into fills before tweening it.
Building classic tweens, shape tweens, 3D rotation or IK rigs in a document that will be delivered as HTML5 Canvas.
The toolbox and menus look identical across document types, and Animate only flags the incompatibility at publish time, where the exported file simply drops or flattens the animation.
What to do instead
Confirm the document type first, then rebuild the timing with motion tweens or frame-by-frame animation, and check the target format's unsupported-features list before starting the timeline.
Using File > Publish immediately without a test preview, so the animation loops forever or the art is cropped and off-centre at different browser widths.
Animate inserts no stop action and the default HTML template centres and clips the stage, so looping and responsive behaviour are only discovered after delivery.
What to do instead
Add a stop() action on the final keyframe, then use File > Publish Preview > HTML and check Center stage and Make Responsive in Publish Settings' HTML/JS options at the target sizes before sending the files.