Making VR Development in Unity More Approachable

Transforming complex, multi-screen internal Unity tools into a streamlined, single-screen B2B experience for non-technical users.

SkillsVR builds VR learning experiences for a wide variety of use-cases and industries. To keep their internal production efficient and adaptive, they created custom developer tools for the Unity game engine. I redesigned the visual scripting workflow of these internal tools to produce the SkillsVR’s Content Creation Kit (CCK), taking it from a cluttered internal tool to a modular B2B product that balances "new user" approachability with "power user" flexibility—all within a single laptop screen.

I started with competitive research beyond the VR space. I benchmarked workflows against tools with tangential use cases (Learning design tools, 3D modeling, video editing, etc) that target users might already know. The goal was to align our tool with mental models they already possessed, even if they had never touched Unity.

I tested low-fidelity workflows with representative users to validate our layout hypotheses. The results were definitive: while the horizontal layout caused visual friction, the vertical alignment felt significantly more intuitive. By mirroring familiar top-down design patterns, the vertical view allowed users to map logic to the 3D scene more effectively, drastically reducing cognitive load and becoming the final design choice.

I collaborated closely with 5 developers to ensure the tool didn't lose its "edge" for power users and designs were feasibly within Unity's constraints. We focused on:

• Naming Conventions: Standardizing terms and titles for visual scripting nodes so they were technically accurate for devs but intuitive for novices.

• Custom Panels: Designing 5 custom panels that align with Unity's modular layout.

• Node Categories: Grouping visual scripting node functionality into similar use-cases and functionality.

I delivered detailed, annotated mockups for all UI components. Following handoff, I provided active developer support, adapting designs when technical constraints arose to ensure the MVP retained its quality and aligned to goals.

• Unblocked Market Testing: Delivered the critical MVP required to shift from internal R&D to external B2B testing.

• Standardized Workflow: Created the first-ever formal design system and naming conventions for the CCK, reducing technical friction for both new users and developers.

• Empowered Non-Technical Users: Successfully enabled users with zero Unity experience to build VR scripts, proving the product’s core value proposition.