How it works
How does the Screen Designer work?
Choose a layout
Panels, top tabs or left tabs, one to four columns, sections that collapse.
Add repeating and nested sections
Rows that repeat — people, addresses, years, items — with minimum and maximum counts, and sections inside rows.
Use smart fields
Dropdowns filled from lists, tables or live services; dependent dropdowns; lookups that fill other fields; OTP fields; action buttons.
Set rules without code
Show, hide, require or lock a field from other answers, built in a condition builder and tested with sample values.
Build documents in
Upload slots with size, type and count limits; values read from a document fill the form.
Edit safely
Undo and redo, an Issues list that blocks broken saves, duplicate a screen with all its links, AI and Excel shortcuts.
Connected through the AI Integration Engine
Link any trigger
Choose the event that starts a service call, such as changing a field, clicking a button or uploading a file. You can also run a call when the screen opens, before saving or when the workflow changes step. The link can use one service, several providers for that service or a sequence of calls.
Choose outcome handling
For each result, choose what the screen should do next. A successful check might mark a field as verified, while a failure might show a message, allow manual entry or stop the save. You can also lock or clear fields when the result requires it.
Preview mock outcomes
A mock is a prepared test reply that stands in for the real service. Select different mock scenarios to check the screen messages and field behaviour before the provider test environment is ready. This lets the team review both successful and unsuccessful paths.
Choose controls, compose screens and extend where needed
Input and action controls
Use text and number inputs, date pickers, dropdowns, searchable dropdowns, checkboxes, file uploads, mobile OTP fields and action buttons. Text inputs can use subtypes such as email or telephone. The runtime also supports multiline text and email fields through configuration. Embedded-content containers provide an extension point for specialised content.
Layouts and related entries
Use accordion panels, top tabs or left tabs with one to four columns. Sections can collapse, repeat with minimum and maximum entry counts, and contain nested sections.
Reusable child screens
Yes. Embed an existing child screen inside a section of another screen. Reuse its configured layout and fields instead of recreating them individually. Repeating and nested sections let you organise related entries within the parent screen.
Calculated fields
Yes. Calculated fields derive values from configured inputs. Portable numeric formulas run on web and mobile; for example, calculate a line total from quantity and unit price. Technical teams should review the formula language when configuring a calculation for both devices.
Specialised embedded components
Yes. Technical teams can use an embedded-content container and a lifecycle script to mount a specialised component in a web screen. This extension requires technical configuration. Android renders HTML content and links; it does not automatically run the same web component scripts.
Build your first app free
All platform features, hosted by us for 120 days. For testing and evaluation, subject to our Fair Use Policy.
Explore DynamicForm
Updated 16 November 2026