App Studio vs. Atlas Forms
Both tools let you build UI without writing code — but they solve different problems. Use this guide to decide which is the right tool for your use case.
The Short Answer
Use Atlas Forms when...
You need a single-purpose data entry form — a structured set of fields that users fill in and submit. Atlas Forms are self-contained and workflow-native.
Use App Studio when...
You need a complete application experience — multiple views, navigation, data browsing, dashboards, and forms working together in a cohesive UI.
Feature Comparison
| Capability | Atlas Forms | App Studio |
|---|---|---|
| Data entry fields | Native — rich field library | Via Form Widget (embeds Atlas Form) |
| Multi-step forms | Built-in sections and steps | Via multi-page Atlas Form in a widget |
| Field validation | Native — per-field rules | Delegated to embedded Atlas Form |
| Data grids / tables | Limited (read-only display) | Full DataGrid widget — sort, filter, paginate |
| Charts and KPIs | Not supported | Chart, Metric, Timeline widgets |
| Navigation / routing | Not supported (single form) | Full sidebar navigation and URL routing |
| Workflow integration | Form submit triggers workflow | Any widget action triggers workflow |
| Role-based page visibility | Form-level access only | Per-page and per-widget visibility rules |
| Responsive design | Auto-responsive fields | Configured per breakpoint |
| Custom JavaScript | Field compute rules | Sandboxed per-widget Custom JS |
| Embeddable in other tools | Yes — via form player | Yes — via iframe or App Studio widget |
| Standalone deployment | Yes | Yes |
The Complementary Pattern
Atlas Forms and App Studio are not competing tools — the most powerful apps combine both. App Studio provides the application shell: navigation, data browsing, dashboards, and layout. Atlas Forms handle data input with their rich field types and built-in validation.
App Studio DataGrid Widget
User browses a list of records (e.g., open support tickets) in a DataGrid. The DataGrid shows summary columns and supports sorting/filtering.
App Studio Navigation
Clicking a row triggers a navigate action to the detail AppPage, passing the record's ID as a URL parameter.
App Studio Detail AppPage
The detail page loads with {{ route.id }}. A Metric widget shows KPIs for this record. Tabs switch between views.
Atlas Form Widget (inside App Studio)
An "Edit" tab contains a Form Widget pointing to an Atlas Form (formId: "support-ticket-edit"). The form is pre-filled with {{ route.id }} data. On submit, the Atlas Form fires its own workflow trigger.
Decision Guide
| Scenario | Recommended Tool |
|---|---|
| Employee onboarding form with 20 fields | Atlas Forms |
| HR portal with employee list, detail pages, and forms | App Studio + Atlas Forms embedded |
| Approval form in a workflow HIL step | Atlas Forms (workflow-native) |
| Operations dashboard with KPIs and data tables | App Studio |
| Multi-step wizard for creating a project | Atlas Forms (multi-step support) |
| Admin panel managing tenants, users, and settings | App Studio |
| Customer feedback form embedded in an email | Atlas Forms (standalone form player) |
| Internal CRM with leads, activities, and notes | App Studio |
To embed an Atlas Form inside an App Studio pane, use the Form Widget and set formId to the Atlas Form's ID. The form renders with its own layout and validation — App Studio just provides the container and handles routing around it.