Targets¶
A target (formally, an implementation strategy) is a program that turns your Intended Design into a running application for one stack. It encodes how that stack is built: the patterns, the architecture, the libraries and the security. The Intended Design stays the same. The target decides what is produced from it.
What a target does¶
When you build, the engine checks and optimises the whole Intended Design, then hands it to the target you chose. The target produces the code, the database and the interface for its stack. It is a program, not advice to be interpreted: it runs as part of the build and applies its patterns to every file.
Available targets¶
| Target | Produces | Status |
|---|---|---|
| Enterprise Web | The full-stack target: a .NET server and an Angular client, with a database | Available |
| React Native | A mobile client built on Expo, from the same forms, logic and theme | Preview |
You choose the target for an application in the Configuration editor, where it is labelled Implementation Strategy, and which also shows the settings that target offers.
Kept current as a service¶
A target is maintained as a service and kept up to date with the versions of the frameworks and libraries it uses. To adopt an update, build again: there is no reasoning or inference step, only a build.
Rebuilding can change generated code
An updated target can produce different code for the same Intended Design. Review the result of a rebuild, and run your unit tests, before you deploy it.
Your own target¶
Because a target is a program, an organisation can encode its own architecture, standards and expertise in one, and every Intended Design can then be built with it. Contact the zAppDev team for the current way to create and use your own target.
Why it matters¶
- Your Intended Design stays the same when the target changes.
- Knowledge is applied by a program, to every file of every application built with the target.
- Generated files are overwritten on every build, so changes belong in the Intended Design or in the language, not in the generated code.
In this section¶
-
The full-stack target: a .NET server, an Angular client and the database.
-
A mobile target that produces an Expo app. It generates the client only.
-
Choose the target of an application in the Configuration editor.
-
How the Intended Design is checked and optimised before a target produces the code.
Where to start¶
- Read What a target does above, then the Enterprise Web page to see exactly what is produced.
- Choose the target of your application in the Configuration editor.
- Build and download the result. See Download and export.
Related¶
- AI and MCP: agents work on the same Intended Design that the target turns into code.
- Glossary: one term per concept.