- Ensure compatibility between your app’s components and the underlying system.
- Optimize resource usage based on the component type (interactive, task, or service).
- Enable proper process management and component isolation.
Guidelines for defining runtime modules
When defining runtime modules in your app manifest, follow these guidelines.Interactive components
The runtime module you use depends on your React Native version:- React Native 0.72
- React Native 0.83
Example manifest entry
Task or service components
For task or service components, you can use the same runtime modules as interactive components if the task or service shares the same process with the interactive component.headless runtimes. These have a smaller memory footprint.
- React Native 0.72
- React Native 0.83
Example manifest entry
Process group consistency
Components in the same process group must use the sameruntime-module.
Version consistency
Always use the same KeplerScript version (indicated by the number after the@ symbol) for all runtime modules in your manifest. For example, you can’t mix version 2 and version 1 runtime modules in the same manifest.
