Game Prototyping & Proofs of Concept

Test an interaction before funding the wider build. XGameDev develops scoped Unity, HTML5 and Construct prototypes that let your team assess a gameplay mechanic, presentation idea or technical risk on the intended platform.

Guac-n-Roll: three concepts before the final campaign game

What your prototype should answer

A gameplay prototype makes the controls, rules and feedback playable with a small amount of content. A technical proof tests a difficult dependency, such as an API, AR interaction or browser build. A vertical slice can demonstrate a selected part of the intended experience with agreed artwork and polish. We define the question first, then choose the smallest useful build. That includes deciding what evidence your reviewers need and which features can wait until production.

How a prototype engagement works

  1. Choose the question

    Describe the decision, intended users, platform and available code or assets.

  2. Set the playable boundary

    Agree interactions, representative content, review points, acceptance checks and who will test the build.

  3. Build and review

    Try the prototype and assess the interaction or technical result against the agreed question.

  4. Record the next decision

    Review findings, known limitations and source handover, then decide whether to revise, test again or plan production.

Three concepts for Knobby’s Guac-n-Roll

We explored three game concepts with Knobby before settling on Guac-n-Roll. Knobby supplied the artwork, Melanie built the chosen browser game in Construct 3, and we integrated PlayFab leaderboards.

Read about Guac-n-Roll

Questions about prototypes and playtesting

Does a playable mechanic take as long as a vertical slice?

A prototype can test the mechanic with placeholder art and a small amount of content. A polished vertical slice takes more production work, so we agree what reviewers need to see before estimating either.

Can you use our code, design or artwork?

Yes, after reviewing what is available and licensed. We agree which assets are placeholders and which work could carry into production.

Can we launch the prototype publicly?

Only when that is part of the scope. Public testing can require extra device coverage, accessibility, accounts, security and operational preparation.

What do we receive, and what comes next?

Agree the playable build, source access, instructions and findings before work starts. Production development, participant recruitment and later support are separate scope decisions.

Choose the first question to test

Share the mechanic or technical uncertainty, target platform and available assets. Include your budget and the decision the prototype needs to support.

Discuss your prototype