Runtime loading and publishing

Runtime loading should be explicit: fetch or import the JSON, create the loader, load, play or pause, validate, and dispose when the owning page state ends.

Loader choices

• RuntimeLoader exposes a compact runtime result for production embedding and parameter/data/state-machine access.
• FmtionLoader exposes the fuller loader lifecycle, save/snapshot/restore methods, DOM and Canvas integration, debug graph registration, and migration behaviors.
• Both load(file) methods are async and return a result with playback and cleanup behavior.

RuntimeLoader result

• RuntimeLoadResult includes canvas, parameters, play(), pause(), string/enum/color getters and setters, onPropertyChange(), data-table helpers, event on/off/once, skeleton and state-machine getters, setDebugOverlay(), metadata, and dispose().
• Metadata reports name and whether the loaded file has Canvas, parameters, and data tables.

Publishing loop

• Publish the source file and the page together so selectors, mounts, and assets agree.
• Run static schema validation before load and debug.validate() after load.
• Verify public desktop and mobile pages, including first frame, scroll range, resize, and disposal if the page has route transitions.

Verified runnable examples

This guide points to proof-backed sample coverage. The full ledger lives in Generated examples and proof log.

DOM: Scroll fade reveal

• Source: faster-motion/demo/tests/dom/catalog/scroll-animations/fade-reveal/fade-reveal.domgraph.fmtion
• Expected output: Sections fade and translate into place as their trigger elements enter the configured viewport range.
• Validation: Schema validation passed. Runtime proof reports zero structural/runtime issues and 17 loaded nodes.
• Desktop proof: generated-assets/faster-motion-docs/proofs/screenshots/dom-fade-reveal-desktop.png
• Mobile proof: generated-assets/faster-motion-docs/proofs/screenshots/dom-fade-reveal-mobile.png

Canvas: Fill rule diagnostic

• Source: faster-motion/demo/tests/canvas/fillrule-diagnostic/fillrule-diagnostic.fmtion
• Expected output: A contained Canvas scene renders paired path cases so nonzero and evenodd fill handling can be compared visually.
• Validation: Schema validation passed. Runtime proof reports zero blocking runtime issues and 10 rendered objects; the accepted metadata note is preserved in the proof ledger.
• Desktop proof: generated-assets/faster-motion-docs/proofs/screenshots/canvas-fillrule-diagnostic-desktop.png
• Mobile proof: generated-assets/faster-motion-docs/proofs/screenshots/canvas-fillrule-diagnostic-mobile.png

Guide-specific sample target: Runtime loading sample with fetch, load, play, parameter update, validate, and dispose.

Faster Motion docs

Use this local map together with the left navigation. The source-backed content tree controls the main article order; this section keeps related pages one click away.

Start

• Faster Motion docs map
• Faster Motion documentation overview
• Get started with Faster Motion
• Faster Motion concepts
• .fmtion file format

DOM animation

• DOM animation guide
• DOM selectors and targets
• Scroll animation
• Pointer, hover, and drag inputs
• Text, SVG, and path animation
• Responsive gates and parameter overrides

Canvas animation

• Canvas animation guide
• Canvas area lifecycle
• Canvas objects, assets, and rendering
• Canvas inputs and state machines

3D and procedural

• Canvas 3D and procedural guide
• 3D scenes, cameras, and lights
• Procedural geometry and fields
• Particles and physics

Reference

• Node reference index
• Node categories reference
• Runtime loading and publishing
• Runtime API reference
• Debugging and preflight
• Debug API reference
• Validation errors and warning codes
• Faster Motion production checklist
• Faster Motion recipes overview