Formo for Flash/Animate Users

If your hands already know Flash or Animate, most of what you already know still applies here, just under different names in a few places, and different in a couple of others worth knowing about rather than glossing over.

The concept cheat-sheet

Where the analogy holds exactly

F5, F6, F7 are exactly where you left them — hold, duplicate keyframe, blank keyframe, same three keys, same behavior, on brush layers. The Animate in Formo guide covers this in full.

Onion skinning works the way you’d expect: past and future poses ghosted behind your current frame, built from your stroke geometry rather than a simplified stand-in. Covered fully in the Onion skinning guide.

The Pencil/Brush tool’s spirit carries over directly — rough freehand strokes becoming clean vector shapes — but goes considerably further: real pressure and tilt on a stylus, four nib shapes, and a stroke that regenerates from your original gesture any time you adjust its settings, rather than being locked in the moment you draw it. Covered in full in Brush & Freehand Drawing.

Where it’s close, but worth knowing the real difference

Symbol → Component. The core idea matches (build once, place many, edit the original to update every instance), but Formo’s component slots (custom per-instance properties) and multi-clip Timeline (an instance choosing which of several named animation states to play, closer to a Graphic symbol’s frame-picker behavior) work a bit differently under the hood than Animate’s Movie Clip/Graphic/Button distinction. Covered in full in Frames, Groups, and Components.

Bone tool → Skeleton rigging. Real FK and IK exist, and the core interaction — drag a hand or foot, the rest of the limb follows — is the same idea. It’s a newer system than Animate’s mature, decades-refined bone tool, so don’t expect identical polish on the interactive feel yet.

Where the model is different, not just renamed

ActionScript → reactive properties and formulas. This is the one worth not glossing over: Formo doesn’t have a scripting language sitting in a separate code panel the way ActionScript does. Instead, any property on any object can be bound directly to a formula: a small expression, typed right on the property itself, that recalculates live as whatever it references changes. Objects can also carry Events and Methods (a click handler, a callable function like Rect1.hit()), reachable from formulas elsewhere in the document. It’s powerful, but a different mental model than writing ActionScript in a dedicated code view. If you’re coming from ActionScript expecting a familiar scripting surface, expect an adjustment here more than anywhere else on this page.

Publish → Export. Animate’s .swf was one format for one purpose. Formo doesn’t have a single equivalent: you export to video or GIF when you want the file itself as the artifact, or to HTML when you want something interactive that keeps its reactive properties alive in the browser. Pick the target based on what you’re shipping, not a single universal "publish" step.

What doesn’t map at all

A few Animate staples don’t have a Formo equivalent, and it’s clearer to say so than to force a comparison: Motion/Classic/Shape tweens as separate named systems (Formo keyframes any property directly with a single easing model instead), Scenes as a project-organizing concept, and mask layers in the Animate sense (Formo has a related but different frame self-clip feature instead, not arbitrary layer-on-layer masking).