Skip to content
AVERIQ
LanguageRUEN
Discuss a project

Games and interactives

An interactive in which a person acts, instead of scrolling

A game or an interactive is needed when the meaning is in the action: to learn, to explore, to compete, to handle the product. I build 2D and 3D scenes, browser games, and applied mechanics, with clear controls and a scope you can continue.

What it takes on

Who it is for

  • Teams with a training or promo experience

    A person should take an action and understand the product, not finish watching a video.

  • Authors of games

    There are rules and a reference. You need a scope that can be played and developed, not concept art.

  • Brands with a difficult subject

    A thing or a space is easier to show through interaction than through ten renders.

A promotional page for a game, a description, and a request are a website. Game production starts where there are controls, rules, and a response.

What can be built

How it looks in practice

  1. 01

    You need to test whether the rule holds attention

    Before art production, a grey but honest scene is built: controls, a goal, a loss. If it is dull now, expensive graphics will not save it.

  2. 02

    The product is shown on the site

    A visitor turns something, assembles it, or walks a short scenario. An ordinary request stays beside it, for people who do not need the game.

  3. 03

    Training for staff

    A simulator repeats a mistake that is expensive to make in real life. The score and the hints matter more than visual noise.

How development goes

  1. 01

    The rule and the goal

    What the player does, and how they know it worked.

  2. 02

    Prototype

    A playable scene without an extra shell.

  3. 03

    Controls and camera

    Gestures, a keyboard, limits, and the feel of the response.

  4. 04

    The content of the scope

    Levels, objects, and states that are part of the handover.

  5. 05

    The shell

    Menu, sound, pause, and saves, if this version needs them.

  6. 06

    Build

    A file or a page you can give to players.

Technologies

You receive a playable build, the sources, a description of the controls, and a list of what is in the current scope and what stayed out of frame.

Demonstrations on this topic

How to commission it

Questions

Can we start with a prototype, rather than a full game?

Yes, and that is usually what is needed. A prototype answers whether the mechanic works. Levels, art, and a meta-game make sense after that answer.

Do you make the graphics as well?

The interface and the composition of the scene, yes. A large illustration production, and 3D assets for characters, are better budgeted separately, so the mechanic and the content are not mixed into one undefined sum.

Will the game be in the browser or in a store?

As we decide from the task. The browser is faster to show to a client. An app store is needed if the experience should live on the phone, apart from the site.

Can a scene be placed inside an existing site?

Yes. The scene loads on its own. It does not drag the whole site with it, and it respects a system setting that refuses extra animation.

What counts as a finished handover?

The scene can be completed under the agreed rules, the controls are explained, known dead ends are closed, and the sources are in the repository. “It almost plays” is not a handover.

Related reading

  • Interfaces

    Screens and rules you can develop from, without guessing.

  • Websites

    A clear storefront for the service, and a path to a request, a catalog, or an account.

  • Services

    A working scenario in the browser: an account, data, roles, and a next step.