Startups and founders
You have a concept that needs a playable build to pitch investors, and may not have an internal team yet. A playable build can demonstrate the concept and support conversations with investors.
Work with startups
Rapid Prototyping and MVP Development
Test your game idea or technical approach with a focused Unity prototype. We agree what the build needs to demonstrate, put it in reviewers' hands and use the findings to plan what comes next.
Proving the foundation for Bookwood
Developed by Ocean View Games with GamerCat Studio.
Bookwood is an interactive fiction platform for iOS, Android and Steam, built to hold a growing library of stories rather than ship as one linear game. GamerCat Studio brought us in early to prove the technical foundation before that library scaled.
We built the content pipeline around Unity Addressables and Cloud Content Delivery, so new books can be added and updated without rebuilding the app or growing the base install. That architecture was validated before full production, not after.
An unfinished brief is fine. The first conversation helps establish scope.
What are you starting with?
Rapid prototyping serves different needs depending on where you are in your journey.
Publishers evaluating concepts
You have multiple concepts and need rapid prototypes to decide which to greenlight. We can build several in parallel, each testing a different mechanic or market hypothesis.
Work with publishersStudios testing new directions
Your core team is busy on the main title but you want to explore a new genre, platform or mechanic without pulling engineers off production.
See how it worksFrom concept to playable build
The process is built to answer your most important question as fast as possible.
1. Discovery
We define the core mechanic, the target platform and the success criteria. What question does this prototype need to answer, and what outcome counts as a pass?
2. Build and test
Rapid development using our framework modules, with a playable build every week, then structured playtests and on-device profiling until the core mechanic feels right.
3. Assess
An honest review of what the prototype proved and what questions remain, with a costed production roadmap and a clear proceed, pivot or stop recommendation.
Prototypes that went further
Validation work delivered by Ocean View Games.
Three scopes, three questions
Each scope is sized to answer a specific question before you commit further.
Playable prototype
Core mechanic, playable and polished, with basic UI, a single-platform build and placeholder art. Answers: does this game feel good to play?
Minimum viable product (MVP)
Core loop complete with basic progression, monetisation hooks, analytics and a multi-platform, soft-launch-ready build. Answers: will players come back?
Vertical slice
A complete polished section at final quality, with full art, audio and UI, for publisher pitches, funding rounds and greenlight decisions.
Pre-built framework modules
Input, cameras, UI scaffolding, analytics, ad mediation and monetisation hooks, all production-grade, plugged in as your prototype needs them.
Cross-platform from the start
Mobile, PC or WebGL, with WebGL often fastest for sharing since reviewers play in a browser with nothing to install.
Built to evolve
Reusable systems can carry into production. Experimental code may need replacing once the prototype has answered its question; we explain that at handover.
Working together
Start with a conversation about what the prototype needs to demonstrate, who it is for and which questions it has to answer.
Discovery settles the single core mechanic and the success criteria, so the build stays focused on proving one thing well.
David and Adam stay close to the engineering. We reuse suitable framework modules and identify which experimental parts need further work before production.
You get a playable build every week, and an honest assessment at the end with a costed roadmap for full production.
Meet the teamFrequently Asked Questions
A prototype tests a specific mechanic or technical question. An MVP includes the minimum connected systems needed to test the experience with users. A vertical slice demonstrates a small section at the intended production quality. We choose the scope around the decision you need to make.
Suitable framework modules and tested systems can carry forward. Experimental code may need replacing or hardening for production. We identify those parts at handover so the next phase can be scoped realistically.
Yes. We review the available assets and use them where they help answer the prototype's question. Otherwise, placeholder art can keep the build focused while final art production is planned separately.
Yes. We narrow the prototype to the networking behaviour or player interaction that needs testing. Player numbers, authority and hosting requirements affect the scope, so we agree them before implementation.
We can target iOS, Android, PC or browsers. A browser build can make sharing easier, while device-specific controls or performance questions may need a native build on the actual hardware.
We agree the core question, playable scope, target platform, assets and review process. Keeping the experiment focused helps control the work. Any further production is estimated separately from the findings.
Yes. We can agree confidentiality before you share private design documents or technical details.
Need to prove an idea before full production?
Tell us what you need the prototype to demonstrate, who it is for and which questions you need it to answer.
Tell us about your project