Reality Composer Pro V3 · Skeleton & Sequencer editors
Context
Where the original Reality Composer spoke to a general audience, Reality Composer Pro speaks to developers already fluent in Swift and Xcode. It needed to feel like part of Apple's developer-tools ecosystem, not like a standalone creative app with its own invented conventions. V3 extended that model with a full animation-authoring layer: Skeleton, Animation, Sequencer, and Behavior Tree editors that had grown out of engineering-first UI, dense property lists built to expose every underlying option, with little visual structure to support how an animator actually thinks about a rig or a timeline.
It's also the project where my own background mattered most directly: I spent a decade rigging characters for film before Apple, as Rigging Lead on Arrival, Warcraft, and The Hunger Games: Catching Fire.
What I designed
- Led design for the Swift Package, Entity, and Component/System UX, the core model developers use to structure a scene as code-connected building blocks, and partnered directly with Apple's Developer Tools Human Interface team to keep interaction patterns and terminology consistent with Xcode
- Moved the Skeleton, Animation, Sequencer, and Behavior Tree editors from information-dense engineering UI into a scalable hierarchy/canvas/inspector model
- Designed custom state iconography and viewport selection affordances for joints and constraints in the Skeleton Editor: disabled, deleted, and error states
- Reduced editing friction in the Animation and Sequencer editors by adopting non-linear-editor patterns (drag, resize, retime, blending) borrowed from professional animation and video-editing tools
- Redesigned the Behavior Tree editor's Sequence Node connections to scale past 5–6 nodes with a single dynamic-output model, replacing manual ports
- Advocated for an explicit, industry-standard animation retargeting workflow over one buried inside an inspector panel, then led the redesign once it was adopted
- Designed and prototyped the RealityKit Component and System behind Keynote's immersive Environments transition: the same underlying technology reaching an audience well outside visionOS developers
Behavior Tree editor · dynamic-output node model
Outcome
Helped bring Reality Composer Pro to public-launch quality as part of visionOS's developer toolchain, then delivered its full animation-authoring layer, moving four interdependent editors from engineering-exposed controls toward interfaces built around how animators actually work. The RealityKit technology behind it also now powers a transition effect in Keynote.