React Native (preview)
The React Native target turns the application you have described, its forms, logic, theme and integrations, into a mobile app built on Expo. You use the same workflow as for a web application, with a mobile app as the output.
Status: preview
The target generates working apps from real Intended Designs today, but it does not yet cover every zAppDev feature. See What is supported today.
What you get
- Forms become screens. The master page becomes the app shell, and its menu becomes a slide-out navigation drawer. Partial views are reused as components.
- Your logic runs on the device. Controller actions, class operations, conditional formattings and calculated expressions are translated to TypeScript and run in the app. Show, hide, enable and disable rules react as the user types, including inside repeaters.
- Your theme comes with you. Colours, sizes, spacing, borders and typography, including the colour and size roles your controls use.
- Your translations come with you. The app picks the language of the device and falls back to your default language.
- Connected to your services. REST interfaces defined in your Intended Design become typed service clients, including the custom URLs and headers you configured.
- Built for phones. Logic in the Intended Design can use the device's GPS location, and image controls can use the camera and photo library. Local storage keeps data on the device between sessions.
- Extend it with your own code. Attach TypeScript files and npm packages to the Intended Design as an external library and call them from your logic.
Controls available
| Category |
Controls |
| Text and display |
Label, hyperlink, icon, image |
| Input |
Text box, text area, password box, switch, dropdown, date, time and month pickers |
| Actions |
Button |
| Layout |
Container (flex), form group, tabs, modal, repeater, partial view |
| Data visualisation |
Charts (pie, doughnut, line, bar), map with data-driven points |
| Navigation |
Menu drawer |
How it works
- Describe your application in Studio, as usual.
- Build. Select the React Native target and click Build.
- Run the app from the link Studio gives you, or browse its source code in Studio.
The result is a standard Expo project, so it can be run on Android and iOS with the usual Expo tooling.
Stack at a glance
The frameworks and components this preview target builds on, with their versions. The app is a client only: logic, data access and security stay on the application backend, which the app calls.
|
|
| Application Type |
Mobile Application |
| Platform |
iOS / Android |
| Language |
TypeScript |
| Framework |
Expo SDK 57 / React Native 0.86 |
| Tiers |
Layers |
Frameworks |
Components |
Patterns |
Tools |
| 1 |
2 |
4 |
3 |
1 |
2 |
1 Client Tier
| Area |
Technology |
| Client |
TypeScript 6.0, React 19.2 |
User Interface Layer
| Framework |
Version |
Notes |
| React Native |
0.86 |
|
| Expo |
57 |
|
| Expo Router |
57 |
File based routing |
| Component |
What it is |
| Screens |
One declarative React Native screen per form, with a typed view model |
| Runtime |
Control library, form state, localization and navigation shared by all screens |
Communication Layer
| Framework |
Version |
Notes |
| HTTPS / JSON |
|
|
| Component |
What it is |
| Action Transport |
Executes form controller actions and datasets on the application backend |
What is supported today
The target suits data-entry, lookup and field-style apps that work against REST services.
- It generates the mobile client only. There is no generated server or database. Data lives in your REST services or on the device.
- REST integration covers reading and submitting data (GET and POST). SOAP and database interfaces are not available.
- Not every control is available yet. Grids and list controls with built-in sorting and filtering are not supported: use repeaters. Some chart types (radar, polar, bubble, area, scatter, horizontal bar) are not available.
- Some action options are not applied yet, including validation before an action, confirmation prompts and external login providers.
- One master page per application.