How to think in Mateu

Mateu is a spec-driven system.

👉 You are not building screens.
You are defining a model that becomes a UI.

The shift

No frontend.
No API layer.
No duplication.

Just one model.

Core idea

• classes = screens
• fields = state
• methods = actions

Everything else is generated.

Key principle

The UI is a projection of your model.

What this means

• no manual rendering
• no sync problems
• no duplicated logic

What to do

• define state
• define behavior
• define structure

Mateu handles the rest.

👉 Next: Build a full backoffice →