Package Ecosystem
Packages are the force multiplier. Install via the Platform Panel and use immediately. The install order
for the core three is strict: AppBuilder → CRUD → Workflow.
The catalogue
AppBuilder core
The foundation for every Zango app. Gives you a full React UI with a sidebar, login screens, page routing, and theming — all wired up out of the box. Add or rename pages from the App Panel without touching code. Read the docs →
CRUD core
Turns any Zango model into a full management screen — sortable table, search, add/edit form — in about twenty lines of Python. The package you'll use most, since most business apps are fundamentally CRUD. Read the docs →
Workflow
Add status-driven lifecycles to any record: define states, control who can move between them, and get a full audit trail automatically. Install after CRUD. Read the docs →
Communication
Send SMS, email, and make calls from your app. Plug in a provider (like Infobip for SMS or an SMTP server for email) and start messaging users from code or the dashboard. Read the docs →
Packages compose. Pair the Communication package with a workflow done method (when a
case is approved, send the user an SMS), or call it from an AI agent's @tool function.
What you skip
Without packages, a typical business app starts with two or three weeks of work before you write a single line of domain logic. Auth flows. A nav shell with permission-aware routing. A data table that sorts, filters, and paginates. A form system with validation. A status machine. An audit log. A notification dispatch layer.
All of it generic. All of it necessary. None of it the thing you were hired to build.
Install the core three packages and that entire layer exists before you've defined your first model. The first thing you write is the thing that matters — the business logic, the domain rules, the screens your users will actually see.