Prototypes – types and purpose

After we have collected requirements, analyzed them and transformed them into a concept, the functional specifications have been defined, user flows, first scribbles or wireframes exist, all these considerations can be refined in the next step. With the help of prototypes, we can now test and validate these conceptual approaches with users or even test the technical implementation.

The type of prototype that fits a project depends on the type of question one is trying to answer. Together with our clients, we therefore work out these questions and define goals to be achieved. The types of prototypes differ mainly in the level of detail of the elaboration. We therefore roughly distinguish between the following categories:

The low-fidelity prototype.

It serves us to answer structural questions and to verify functions. This type of prototype can be used at a very early stage of the project. Based on handmade scribbles or wireframes, which are extremely easily connected to a click dummy using our tooling, particularly short iterations are possible. This allows us to test and discard ideas in an uncomplicated way and to quickly follow up on valid approaches.

Medium fidelity prototype

This type of prototype is a refinement of the low-fidelity prototype. Here, the knowledge already gained is put into a rough visual design. In the form of static screens that are quickly connected to a click dummy using tools, we can get a more accurate picture of the concept and the final application, as well as test navigation and user interface elements. The medium-fidelity prototype is particularly suitable for conveying the look and feel of an application to clients, stakeholders and test subjects.

High-fidelity prototype

High-fidelity prototypes simulate an application so well that it looks almost real. The detailed visual interface is supplemented with functionalities. In this way, precise user and acceptance tests can be carried out. This type of prototype is mainly used in complex and highly sensitive applications.

Conclusion

Our experience shows: The benefits of prototypes are considerable. With the help of prototypes, weaknesses in concept, usability and problems in technical implementation can be identified at an early stage. Those who consider skipping this important step in product development run the risk of investing time and money in unnecessary subsequent optimizations and new developments. The later in the development process a comprehensive evaluation takes place, the higher the risk of not having used time and resources wisely.