Mobile forms best practices mobile-forms-best-practices
For mobile and offline form use cases, the recommended approach is to build your own native app and fetch form definitions via the Headless Adaptive Forms API. This gives you full control over the mobile experience and ensures ongoing support as mobile platforms evolve.
Recommended approach recommended-approach
Build a native mobile application (iOS or Android) that:
-
Fetches the headless form definition – Use the Headless Adaptive Forms APIs to retrieve the form JSON on demand (for example, when the user opens a form or navigates to it in your app). You can list available forms and then fetch the form definition by ID.
-
Renders the form in your app – Use your preferred UI framework (for example, React Native, or native views) to render the form from the JSON. You can use the Forms Web SDK and existing Headless adaptive forms React components where they fit your stack, or build your own renderer that consumes the same JSON structure.
-
Optionally supports offline – Implement local storage and sync in your app. For example, cache form definitions when online, save drafts locally, and submit or sync data when the device is back online.
This approach keeps your app maintainable as Android and iOS change, and uses the supported Headless Adaptive Forms platform for form authoring, validation, and submission.
Getting started getting-started
- AEM Headless adaptive forms overview – Capabilities and concepts.
- Headless adaptive forms APIs – List, fetch, validate, and submit forms programmatically.
- Architecture – How Headless adaptive forms work and how front-end apps consume them.
For step-by-step integration, see Create and publish a headless form and the Developer portal.