Skip to main content

Android project requirements

System requirements:
  • minSdk = 26 (Android 8.0)
  • compileSdk = 34
The SDK library was build using:

Installing the library

  1. Add the maven repository in your project’s settings.gradle.kts file:
  1. Add the library as a dependency in your app/build.gradle.kts file:

Library dependencies

Impactful dependencies:

Public API

The SDK library is managed through the FlowxSdkApi singleton instance, which exposes the following methods:

Configuring the library

To configure the SDK, call the init method in your project’s application class onCreate() method:

Parameters

• Providing the access token is explained in the authentication section.
• The custom components implementation is explained in its own section.
• The implementation for providing a custom view for the header of the Stepper component is detailed in its own section.
• Collecting analytics events from the SDK is explained in its own section.
• Handling the start of a new process while in a running process is explained in its own section.

Sample

The configuration properties that should be passed as SdkConfig data for the config parameter above are:

Custom validators

The custom validators map is a collection of lambda functions, referenced by name (i.e. the value of the key in this map), each returning a Boolean based on the String which needs to be validated. For a custom validator to be evaluated for a form field, its name must be specified in the form field process definition.
By looking at the example from above:
if a form element should be validated using this lambda function, a custom validator named "exact_25_in_length" should be specified in the process definition.

Using the library

Authentication

To be able to use the SDK, authentication is required. Therefore, before calling any other method on the singleton instance, make sure that the access token provider is set by calling:
The lambda passed in as parameter has the ai.flowx.android.sdk.FlowxSdkApi.Companion.AccessTokenProvider type, which is actually a functional interface defined like this:
Whenever the access token changes based on your own authentication logic, it must be updated in the renderer by calling the setAccessTokenProvider method again.

Theming

Prior setting up the theme, make sure the access token provider was set.
Check the authentication section for details.
To be able to use styled components while rendering a process, the theming mechanism must be invoked by calling the suspend-ing setupTheme(...) method over the singleton instance of the SDK:

Parameters

If the themeUuid parameter value is empty (""), no theme will be fetched, and the mechanism will rely only on the fallback file, if set.

If the fallbackThemeJsonFileAssetsPath parameter value is null, there will be no fallback mechanism set in place, meaning if fetching the theme fails, the redered process will have no style applied over it’s displayed components.
The SDK caches the fetched themes, so if a theme fetch fails, a cached version will be used, if available. Otherwise, it will use the file given as fallback.

Sample

The fallbackThemeJsonFileAssetsPath always search for files under your project’s assets/ directory, meaning the example parameter value is translated to file://android_asset/theme/a_fallback_theme.json before being evaluated.
Do not start or resume a process before the completion of the theme setup mechanism.

Changing current locale settings

The current locale and language can be also changed after the initial setup, by calling the changeLocaleSettings function:

Parameters

Do not change the locale or the language while a process is rendered.
The change is successful only if made before starting or resuming a process.

Sample

For locale, use the format BCP 47. BCP 47 is the standard for representing language and region codes, here is a link to the BCP 47 specification. An example of BCP 47 is en-us (language code - en and region code - us).

Start a FlowX process

Prior starting a process, make sure the authentication and theming were correctly set up
After performing all the above steps and all the prerequisites are fulfilled, a new instance of a FlowX process can be started, by using the startProcess function:

Parameters

The returned @Composable function must be included in its own Activity, which is part of (controlled and maintained by) the container application.

This wrapper activity must display only the @Composable returned from the SDK (i.e. it occupies the whole activity screen space).

Sample

Resume a FlowX process

Prior resuming process, make sure the authentication and theming were correctly set up
To resume an existing instance of a FlowX process, after fulfilling all the prerequisites, use the continueProcess function:

Parameters

The returned @Composable function must be included in its own Activity, which is part of (controlled and maintained by) the container application.

This wrapper activity must display only the @Composable returned from the SDK (i.e. it occupies the whole activity screen space).

Sample

Custom components

The container application should decide which custom component view to provide using the componentIdentifier configured in the UI designer. A custom component receives data to populate the view and actions available to execute, as described below.
It can also be validated and provide data back into the process when executing an action.
To handle custom components, an implementation of the CustomComponentsProvider interface should be passed as a parameter when initializing the SDK:

Sample

CustomComposableComponent

The implementation for providing a custom component is based on creating and binding a user defined @Composable function, through the CustomComposable interface:
The returned CustomComposable object is an interface defined like this:
The value for the data parameter received in the populateUi(data: Any?) could be:
  • Boolean
  • String
  • java.lang.Number
  • org.json.JSONObject
  • org.json.JSONArray
The appropriate way to check and cast the data accordingly to the needs must belong to the implementation details of the custom component.
Both validation and providing data back into process are optional, and, based on the needs, it may be included in the implementation or not.

Sample

Among multiple existing custom components, there may be one that:
  • allows the input of a value representing an age
  • the value should be validated (e.g. to be at least 35 years old)
  • the value will be passed back into the process

Execute action

The custom components which the container app provides may contain FlowX actions available for execution.

These actions are received through the actions parameter of the populateUi(actions: Map<String, CustomComponentAction>) method.

In order to run an action (i.e. on a click of a button in the custom component) you need to call the executeAction method:

Parameters

Get a substitution tag value by key

All substitution tags will be retrieved by the SDK before starting the process and will be stored in memory. Whenever the container app needs a substitution tag value for populating the UI of the custom components, it can request the substitution tag using the method above, by providing the key. It returns:
  • the key’s counterpart, if the key is valid and found
  • the empty string, if the key is valid, but not found
  • the unaltered string, if the key has the wrong format (i.e. not starting with @@)

Get a media item url by key

All media items will be retrieved by the SDK before starting the process and will be stored in memory. Whenever the container app needs a media item url for populating the UI of the custom components, it can request the url using the method above, by providing the key. It returns the URL string of the media resource, or null, if not found.

Custom header view for the STEPPER component

The container application can opt for providing a custom view in order to be used, for all the Stepper components, as a replacement for the built-in header.
The custom view receives data to populate its UI, as described below.
To provide a custom header for the Stepper, an implementation of the CustomStepperHeaderProvider interface should be passed as a parameter when initializing the SDK:

Sample

CustomComposableStepperHeader

To provide the custom header view as a @Composable function, you have to implement the CustomComposableStepperHeader interface:
The returned ComposableStepperHeader object is an interface defined like this:
The value for the data parameter received as function argument is an interface defined like this:

Sample

Collecting analytics events

To be able to collect analytics events from the SDK, an implementation for the AnalyticsCollector functional interface may be provided when initializing the SDK:
where the Event looks like this:

Sample

The implementation can be passed as a lambda, like:
The value property represents the identifier set in the process definition.For action type events there are some additional properties provided:
  • component - The type of component triggering the action
  • label - The label of the component, if available. (E.g. title of a button or label of a form element)
  • screen - The identifier of the screen containing the component, if set

Handling “Start of a new process”

When an action of type START_PROJECT is executed, the onNewProcessStarted lambda provided in the FlowxSdkApi.getInstance().init(...) function is invoked. This callback provides the UUID of the newly started process, which can be used to resume the process by calling the FlowxSdkApi.getInstance().continueProcess(...) method. It is the responsibility of the container application’s developer to implement the necessary logic for displaying the appropriate UI for the newly started process.

Sample

One way to handle this is to send a broadcast message to notify the Activity currently displaying the running process. The Activity should handle the broadcast to reload and display the newly started process identified by processInstanceUuid (received in the broadcast intent).

Known issues

Last modified on July 24, 2025