Engines, tooling and UI, from a studio that maintains the tools.
Unity and MonoGame engineering backed by the libraries other teams build on. A board seat at the MonoGame Foundation, the original uGUI extension library maintained since 2015 and recently launched sister library for the Unity UI Toolkit. And three published Unity books.
What we do
Unity development and UI systems
Unity 6 with URP, Addressables, UI Toolkit and uGUI. The controls come from libraries we maintain.
MonoGame and console pipelines
Six-platform project templates with ahead-of-time compiled console builds for Xbox and DirectX 12.
Engine tooling and release automation
Package publishing to OpenUPM and npm, reusable GitHub Actions and self-hosted runners.
Developer education
Documentation sites, tutorial series and starter kits that lower the barrier for teams adopting an engine.
What this has produced
Told by organisation type and date. Client and product names are withheld. Business partners are named.
Builds for every target from day one
A project template covering six platforms, a documentation site, a 3D tutorial series and two starter kits.
Xbox GDKX, DirectX 12, NativeAOTControls Unity teams do not have to write
The uGUI library with 101 controls, and a UI Toolkit successor with 25 controls and 22 templates released in 2026.
1.7k GitHub starsA WebXR game built on a framework, not an engine
A discovery game for standalone headsets in the browser, written against a cross-platform framework so the game holds only game. Story and economy designed as systems, logic tested on the desk, portability measured rather than assumed.
62 tests, no headset neededDemonstration: Pale Signal →See it running.
Working systems that show this practice in use. Capabilities and results are described; how they are built is not.
The rest of the practice
Tell us about the estate, the device or the problem.
Email a few lines about what you are trying to do. We will reply with what we would look at first.