# Flows

Flows are now a first-class part of your Buzzy app definition.

A flow describes how users and systems move through your app's processes to complete goals, including key states, decision points, and transitions.

Why this matters:

* Flows define functionality and behavior, not just screen content.
* Flows provide stronger context for Buzzy AI when generating blueprint and screens.
* Flows help identify missing datamodel requirements earlier (for example status or lifecycle fields).

Use Flows together with:

* Brief: functional and business requirements.
* Datamodel: entities, fields, and relationships.
* Blueprint: overall app/sitemap structure.
* Theme: visual design system context.

Related guides:

* [Functional Design: Flows](https://docs.buzzy.buzz/the-ultimate-guide-for-vibe-coding-an-application-with-ai/design-fundamentals/functional-design#id-1.-flows)
* [Buzzy AI](https://docs.buzzy.buzz/working-with-buzzy/buzzy-ai)
* [Datatables, Fields & Data](https://docs.buzzy.buzz/the-building-blocks/datatables-fields-and-data)