Skip to content

Export

Purpose

Owns animation export orchestration workflows for Snap Studio Pro.

This territory coordinates animation frame planning, batch export execution, directional animation export workflows, post-processing routing, spritesheet/GIF assembly coordination, progress tracking, and export lifecycle management.

Animation.Export is intentionally orchestration-heavy.

Owns

  • Animation export orchestration
  • Batch animation export workflows
  • Directional animation export coordination
  • Animation frame planning
  • Animation export progress tracking
  • Animation post-processing coordination
  • GIF/spritesheet assembly routing
  • Animation export timing/metrics
  • Animation export validation workflows

Does NOT Own

  • Low-level rendering implementation
  • Texture compositing
  • File encoding implementation
  • Preview scene lifecycle ownership
  • Animation playback ownership
  • Panel UI layout ownership
  • Render pipeline implementation

Allowed Dependencies

Export may depend on:

  • Capture systems
  • Preview systems
  • Directional capture workflows
  • Export assembly systems
  • Infrastructure runners/progress systems
  • Animation sampling systems
  • Rendering abstractions where required

Export is allowed to coordinate across multiple systems.

Notes

This folder is one of the heaviest workflow orchestration territories in Snap Studio Pro.

This is intentional.

Animation export workflows naturally coordinate: - clip iteration - frame planning - directional capture - progress reporting - capture execution - spritesheet generation - GIF assembly - export timing - post-processing

The goal is workflow clarity, not minimal orchestration.

Animation.Export owns: - how exports are coordinated - how export jobs progress - how export stages interact

Capture systems own: - frame/image generation

Rendering systems own: - low-level rendering implementation

Preview systems own: - live preview coordination

This separation is important for long-term maintainability.

Large orchestration services are acceptable here when they represent real production workflows rather than hidden implementation detail.

Future Candidates

  • Continue separating export planning from capture implementation.
  • Avoid allowing rendering implementation into Animation.Export.
  • Maintain clear ownership of progress tracking and export lifecycle coordination.
  • Continue preferring explicit workflow stages over hidden side-effect pipelines.
  • Avoid over-abstracting export orchestration when the workflow itself is inherently complex.