Module 0 · Dashboards vs Data Apps

A dashboard answers a fixed set of questions on a schedule. A data app is interactive software: viewers set parameters, explore scenarios, and (where granted) take actions — all against governed data, with the viewer’s own permissions enforced. Both are generated from conversation and stored as reviewable config, not hand-built UI code.

What a data app is made of — Under the hood (per the platform changelog): a React front end Ana builds from your description, server-side compute functions for live reads and write-back, and a private per-app database. Apps live in the Ontology with version history, run on persistent servers with real-time multiplayer, and are iterated through conversation or shared under role-based permissions.

Reach for a…	When	Example
Dashboard	Same view for everyone, refreshed on schedule	Weekly cost-of-care PMPM trend
Data app	Each viewer needs their own slice, inputs, or what-ifs	”Pick a region + scenario, see the projected impact”

Prompt

What can I build from this workspace beyond charts and dashboards? Explain what a data app is here, what it can and can't do in this beta, and show me one example structure based on my connected data.

You’ll see: Ana describe the app surface available in your workspace and sketch what an app over your data could look like — grounded in your actual tables.

✅ Checkpoint

You can say when a data app beats a dashboard in one sentence
Ana confirmed Data Apps is enabled in your workspace

​✅ Checkpoint

✅ Checkpoint