Framework components

The framework at a glance

GameBus consists of four main parts:

• GameBus Core — Used to configure interventions and deliver them to your target audience. Core manages participants, consent, app layouts, app content, access, and structured data about participant behavior.
• GameBus Stories — Add interactive content to Core. A Story can combine video, animations, quizzes, and minigames to create immersive experiences.
• GameBus Sync — Connect external services to Core. Sync can, for example, bring activity data from a physical activity tracker into GameBus.
• GameBus Docs — The site you are reading now. It explains how the GameBus framework works and provides guides for configuration, research, and development.

How the parts fit together

Core is the hub. It defines the app your target audience uses, including which layout, content, and features each participant can access.

At its heart, an intervention promotes a set of target behaviors. In GameBus, these are represented as Tasks. Core keeps track of those Tasks and records whether and when participants engage with them.

A Story can be used as one of those Tasks. For example, a Story might guide someone through planning when and where to practise a new behavior.

Sync links external services to Core. For example, it might send data from a physical activity tracker to GameBus. Core can then use that data to determine whether a participant completed a Task.

You can use Core on its own, or add Stories and Sync when your intervention needs them. The rest of the documentation explains how to configure and extend each part.