A spatial game has to feel good in the player's hands. We develop VR and AR gameplay around a clear core interaction, then build the systems, environments and characters that give it purpose.
The first milestone is a playable slice, not an oversized feature list. It gives your team something concrete to evaluate before committing to levels, progression and full production.
We use the early build to test input, feedback, movement and the relationship between the player and the world. Comfort and readability are design constraints throughout production. A mechanic that works on a monitor may need a different approach in a headset.
02 / Production scope
A focused prototype that demonstrates the central interaction and defines what the player is trying to achieve.
Scoped development of levels, progression, player behaviour and real-time assets in the agreed engine.
Performance testing, device checks and release preparation against an agreed platform and acceptance checklist.
03 / Applications
Build around headset performance, controller or hand input and a clearly bounded play session.
Turn a campaign idea into a playable experience with a practical visitor onboarding and reset flow.
Connect digital interactions with a supported mobile or spatial context.
A VR game development brief benefits from two lists: what the next playable milestone must demonstrate, and what a commercial release will eventually require. Store assets, localisation, accessibility options, analytics and ongoing support should not disappear inside a vague promise to deliver a game. Establish the minimum target hardware and review how content affects frame-time budgets as the experience grows. If an external team owns publishing or backend services, define those interfaces early. This gives the prototype clear acceptance criteria without pretending that a good prototype is already a finished product.
You do not need a finished specification to start a conversation. Share the intended audience, the outcome you need and any existing material. Include a target date or platform constraint if you have one. We can use those details to discuss the right starting point and the questions a production scope needs to answer.
Tell us the core mechanic, target platform and what you need next: prototype, production support or a complete build.
Discuss your project05 / Before you brief us
Both can be discussed. The brief should distinguish full application ownership from a defined contribution such as gameplay prototyping or character production.
Yes. A contained slice can establish visual quality and gameplay behaviour, while exposing technical risks before a wider production commitment.
Only when specifically scoped. Networking, matchmaking, moderation, persistence and service operation introduce separate design and maintenance requirements.
No. We can prepare a build for agreed requirements, but platform review and approval remain with the platform operator.
06 / XR game development
Tell us the core mechanic, target platform and what you need next: prototype, production support or a complete build.
Prefer email?