Skip to main content




Applies only to Reactive Web Apps
Service Studio version:

Maintain UI in dedicated modules

  • Edit
    Collaborate with us
    Edit this page on GitHub
  • Your team can benefit from having Screens and Blocks in separate UI Modules and then reusing those UI elements in other Modules. This is not only a good development practice, but also improves team collaboration, because there are less merge conflicts when working on different Modules simultaneously.

    To reuse Screens and Blocks between Modules, you need to meet the following requirements in your App.

    • The Themes need to be the same. This guarantees that UI looks the same. If the Themes are different, you get the Theme compatibility warning.
    • The UI elements (Screens, Blocks) need to be public. By setting these elements as public you make them available for referencing in other Modules.

    Current limitations

    Because of the architectural differences between Apps, there are some limitations when reusing Screens and Blocks between Modules and Apps. When you move Screens between Apps, Service Studio checks for these limitations.

    • Reusing Screens and Blocks is not available in Mobile Apps.
    • System Event On Application Ready runs every time you navigate between Screens in different Modules.