The approach¶
zAppDev offers a way to build full-stack, multi-tier, agent-ready applications. You describe the application as an Intended Design and write all its logic across all tiers in the same way, so the whole application can be checked before any code is produced. The engine produces the code for each tier, for the target you choose. AI helps you create the Intended Design, and every change to it is checked.
People do not hold an application in their heads as files. They hold purposes, business concepts, rules and screens, and the links between them. The six views give a tool the same shape, so what people understand and what the tool holds line up.
The six views¶
Each view answers one question. Together they describe the whole application.
| View | Question it answers | In zAppDev |
|---|---|---|
| 1 · Intent | Why does this application exist? | Goals, constraints and principles. |
| 2 · Domain | What is the business made of? | Business objects, associations and enums |
| 3 · Logic | What happens, and when? | Operations, actions and rules in the language |
| 4 · UX/UI | What do people see and do? | Forms, themes and navigation |
| 5 · Integration | How does it talk to the world? | Services, API adapters, MCP and automation flows |
| 6 · Data | Where is it kept and moved? | Persistence, data mappings and reports |
Four properties¶
- Separate. Intent, domain, logic, UX/UI, integration and data are six views, each with its own vocabulary.
- Connected. Elements link across views, so you can always ask what depends on what, and why.
- Modular. Change one view without rewriting the others. Swap the target and keep the Intended Design.
- Strategic. The Intended Design carries purpose, so people and AI work against the goal, not just the syntax.
One connected graph¶
Every element of the Intended Design is related to others, so the whole application forms one connected graph. Studio can answer what would break if an element changed, where it is used, and whether the whole Intended Design is still valid before any code is produced. See Intended Design.
The whole stack, checked as one¶
A full-stack application usually spans several technologies: a database, a server, a web or mobile client, and the API between them. Each has its own language and tools, so nothing sees the whole application at once, and keeping the tiers consistent is left to the team.
In zAppDev the engine reads the whole Intended Design, so it can check the database, the server and the client together. A rule written once in the logic reaches every tier, and a change that would leave one tier out of step is reported by the checks.
MCP opens all of it to AI agents. They can read the Intended Design, change it, validate it and build it, and they work through the engine, not around it.
Why this matters with AI¶
AI makes writing code cheap. The hard part is knowing the result fits together across a database, a server and a client written in different languages. Here an AI change is one change to one Intended Design, and the engine checks it across every tier.
The approach with AI¶
Each view is described in its own terms, so an agent works on one view at a time. A change to one view is kept apart from the others, and every change is checked before any code is produced. See AI and MCP.
Where to go next¶
- Intended Design: what the Intended Design contains and how it behaves.
- The engine and Targets: how the Intended Design becomes code.
- Hello World tutorial: build a connected application, view by view.