Skip to main content

Deploy App using your latest Custom Component version

2025.2+

A common use case is to ensure that every app using a custom component automatically uses the latest deployed version, without having to manually redeploy each app that uses it.

Custom components have a property called Same deployment. When this is set to false, you can deploy the custom component independently from the apps that use it.

Introducing In-App libraries

In-App libraries are apps that are used to deploy a library of custom components. This app will contain the custom component code that will be used when the component has the same deployment set to false. You can create these In-App libraries from the library page.

Example​

Consider an app MyApp that uses a custom component MyComponent from library MyLibrary in the form MyForm:

MyLibrary
└── MyComponent

MyApp
└── MyForm

Same deployment: true​

  • MyForm use the component MyComponent with same deployment true
  • When MyApp is deployed, MyComponent is packed together with the app.
MyApp
├── MyForm
└── MyComponent

Same deployment: false​

  • MyForm use the component MyComponent with same deployment false
  • When MyApp is deployed, the custom component MyComponent is not packed with the app. Instead, it is deployed separately as part of the library app MyLibraryInApp.
MyApp
└── MyForm

MyLibraryInApp
├── MyComponent
└── (rest of components from MyLibrary...)