DynamicForm Start free trial
Step 8 of 15 · Render Engine · topic 1 of 3

Build · Render Engine

Design once. It is drawn on the web and on the phone.

Design once for web and mobile. Each renderer interprets the shared configuration, adapting the layout and controls for the device while applying configured rules, calculations and data relationships.

The same screen on laptop, tablet and phoneOne screen definition drawn three ways: three columns on a laptop, two on a tablet, one on a phone. Matching colours show the same section on each device.same definitionWeb · 3 columnsTablet · 2Phone · 1
One screen on laptop, tablet and phone, with colours linking each section across the devices.
In short

One configuration drives the web and Android application. Mobile presentation uses stacked fields and expandable sections, with repeating entries, nested sections and configured behaviour. Screen-definition changes do not require a new app version.

Connected through the AI Integration Engine

Use server-side integrations

The phone sends its service request through DynamicForm, and the server contacts the provider. The provider address, API key and access token stay on the server. Your team can use the same configured connection without placing provider credentials on the device.

Queue and receive

If you enable “Queue when offline”, service calls wait until the phone reconnects and then run without duplicates. For results that arrive later, the app checks again while the form is open and when it resumes, and keeps saved-form results in Updates. Optional push delivery needs additional setup and is switched off in the documented build. It carries only a reference to the result, without personal data, and does not show a phone notification-tray alert.

Explore integrations

Familiar work on Android

Use the same input choices on the phone. Android supports Date & Time, Radio buttons, Multi-select, Colour, Slider, Multi-line text and Email. Colour swatches make the selected colour visible.

Choose System, Light or Dark appearance for phone work. After the first sync, listed records remain available offline. End users use the same list pages online and offline, keeping the view familiar when connectivity changes. Each application can have its own branded Android app.

See the phone's sign-in location on a map. The route screen lets you open recorded points in Google Maps. Explore branding and app publishing for application identity and Maps key choices.

Scan and calculate

Scan barcode and QR fields with the phone camera. Browser scanning works where supported, and keyboard scanners work everywhere. The field captures the scanned value for the application.

Line totals update as lines change. Sums, counts, lowest and highest values match across web, phone and server. The server's value is stored.

Number series use branch counters and yearly, monthly or financial-year resets. Assigned numbers cannot be edited or reused. Offline records show “number given on sync”, so users know numbering will follow synchronisation.

Explore Rules and calculations for shared calculation behaviour.

Shared configuration, device-specific presentation

Adapt the layout

The mobile renderer interprets the shared screen configuration. Fields stack vertically, and panels and tab sections become expandable sections. Repeating entries and nested sections remain connected to their parent entry. The presentation changes to suit the device.

Carry the behaviour

The mobile runtime evaluates configured visibility, required-field and read-only rules, portable calculations and dropdown dependencies. Your team should preview and test the configured behaviour on both devices, especially when using technical extensions.

Build your first app free

All platform features, hosted by us for 120 days. For testing and evaluation, subject to our Fair Use Policy.

Updated 16 November 2026