Help

Dynamic content

Dynamic content SDK allows you to render API-driven UI components. It also allows to show personalized content to the user based on the DynamicContentUser sent.

Start using Dynamic content SDK

The platform module includes the Dynamic content SDK. It is composed of these modules:

Dynamic content SDK allows multiple customisations, check the most common customisations.

Koin modules

Dynamic content dependencies are injected using Koin. The platform module injects all the necessary Koin modules. These are the Koin module included:

  • dynamicContentDataModule
  • dynamicContentDomainModule
  • dynamicContentPresentationModule

Keywords definition

  • Slot: placeholder where a DynamicComponent will be displayed on a non full dynamic content screen.
  • SlotId: String constant that defines the slot's position on the screen. It can takes values such as "top" or "scroll-bottom".
  • DynamicComponent: a Composable that can be displayed.
  • ComponentType: String constant that specifies the type of DynamicComponent received via the API.
  • DynamicModifier: similar to Compose Modifiers, it allows you to decorate any DynamicComponent.
  • SlotsContent: domain model that holds all the DynamicComponents received via an API.
  • DynamicContext: a generic Map that holds the slot state to be submitted to BE.

Poq SDK screens with Dynamic content support

These are the screens, and their supported slots ids, which support Dynamic content:

  • Account: scroll-top and scroll-bottom
  • Cart: scroll-top and scroll-bottom
  • Categories: scroll-top and scroll-bottom
  • NativeCheckout: scroll-top
  • OrderScreen: scroll-top and scroll-bottom
  • ProductList: scroll-top
  • ProductDetail: before-links, after-links and scroll-bottom