Prototyping is often a part of the preproduction phase, and a crucial step for new game concepts. The game’s genius ideas are developed and tested to see whether they work in action. The focus in prototyping lies on functionality. Because development of a prototype is ‘lean and mean’, we can change fundamental game elements more easily. If production is ongoing, changing an idea is often hard and costly.
“You can use an eraser on the drafting table or a sledgehammer on the construction site”
– Frank Lloyd Wright
Feasibility Study
Some aspects of game development are technically challenging or even groundbreaking. That is why some concepts need a feasibility study before even turning them into a prototype. In such a study, we look at technical solutions for a certain concept. Then, we see whether it is possible, is acceptable for the user, fits in the budget, and fits in the game’s scope.
Paper Prototyping
For some game ideas it is recommended to abstain from digital development and to try them out on paper first. Actually, most games that are not timing-based could probably use some paper prototyping. A paper prototype could overlap with a functional wireframe or mockup (but on paper, of course).
(Rough) Prototype
A digital prototype made from inefficient throwaway code (which is, by all means, NOT to be used for the production phase!). A prototype most often focuses on the functional aspects of the game. It aims to prove that a concept works and is feasible from a development point of view. A prototype can usually be tested, and often has multiple iterations, depending on the size of the project.
Build
As a prototype is already a piece of software, we deliver this in a build. Such a build can be run on a specific platform. For example, builds ending on .apk can be run on Android devices and on Oculus Quest. Builds ending on .exe can be run on Windows.
After a concept was successfully tested, most developers opt to create a vertical slice.
Go to Vertical Slice
Back to Overview