Meta Developers

Design

Interaction model

The interaction model is the core of the experience and occurs after activation. It can be a single turn or multi turn interaction depending on the specific use case for your app. Despite the form of interaction, three principles should always be considered during the design:

Transparency: Your app should 1 transparently communicate what the system is doing to the user. Surprises can be a good thing in a game, but not when interacting with the system.
Preserve immersion: In immersive games, immersion is the goal and a significant part of the user experience. Don’t take the user out of that experience when interacting with them. This might mean using a more immersive voice, dialog, or situation in which the player communicates with the system.
Minimize Disruption: Ensure that you move smoothly from the game into an interaction model and then smoothly move out again. An interaction with the player may not be expected by them, but it shouldn’t feel out of character for the game. By minimizing the disruption that interactions can cause, the player will remain immersed, enjoying the game more, and be more likely to return to the game at a later time.

Single turn

This form of interaction consists of a single request. Typically there would also be a single response to conclude the interaction. It is generally used to complete a single task e.g. turning off the lights, getting stock updates, setting timers, etc. Synonymously, this interaction can be referred to as one-shot utterance or one-shot request.

Multi-turn

This form of interaction is usually conversation driven and consists of multiple interactions. It is generally used for scenarios that require interaction e.g. speaking to a non-player character, ordering something, guided activity, etc. During multi-turn interactions, it’s important that there is an option for users to dismiss the interaction or the system time out when there hasn’t been a reply for a certain amount of time.