Skip to content

WIP

Purpose

Owns experimental, unstable, or actively evolving editor UI panels inside Snap Studio Pro.

This territory exists as an isolated sandbox for testing new workflows, UI concepts, experimental production tooling, and incomplete editor systems before they are promoted into stable panel territories.

Owns

  • Experimental panel workflows
  • Prototype editor UI
  • In-progress workflow tooling
  • Temporary validation panels
  • Opt-in experimental UX systems
  • Rapid iteration editor tooling

Does NOT Own

  • Stable production architecture
  • Guaranteed workflow/API stability
  • Core preview lifecycle ownership
  • Rendering pipeline ownership
  • Shared infrastructure ownership

Allowed Dependencies

WIP panels are intentionally allowed more flexibility than stable panel territories.

However, WIP should still avoid: - leaking unstable dependencies outward - tightly coupling experiments into stable workflows - mutating core architecture unnecessarily

Notes

WIP is intentionally less strict than the rest of the editor architecture.

The goal is: - experimentation - rapid iteration - workflow validation - production tooling research

Systems here may eventually: - move into stable panel territories - be rewritten completely - be removed entirely

That is expected.

WIP should remain opt-in wherever practical and should avoid becoming a hidden dependency for stable production workflows until the design is proven.

Future Candidates

  • Promote stable workflows into proper panel territories once architecture settles.
  • Keep experimental dependencies isolated.
  • Avoid allowing WIP panels to become permanent hidden production systems.