Please note:
- Early Access: Support for Compose Multiplatform (CMP) is currently in Early Access.
- Release Notes: Looking for Fullstory CMP release notes? Find them in the Releases section below.
Fullstory's Compose Multiplatform support is built on top of the functionality of the existing platform capture SDKs. Compose on Android is fully supported already through the Fullstory Android SDK. The fullstory-cmp Gradle plugin described here adds capture support for Compose Multiplatform, specifically for iOS. We also include a fullstory-cmp-api library for CMP to provide consistent access to Fullstory APIs from shared Kotlin code.
This article will cover the following:
Setup
To set up Fullstory for a Compose Multiplatform app, integrate the Fullstory Android and iOS SDKs, then apply the fullstory-cmp plugin. Android Compose capture uses the Fullstory Android SDK. iOS Compose capture uses the fullstory-cmp plugin alongside the Fullstory iOS SDK.
Integrate the Fullstory Android and iOS SDKs
Before you apply the fullstory-cmp plugin, set up the Fullstory SDK for each platform your app targets.
-
Set up Android: Follow the Getting Started with Android Data Capture and Getting Started with Jetpack Compose help documentation. Also see Automatic Selectors for Jetpack Compose. Those guides show Gradle snippets in Groovy. In a Compose Multiplatform project, add the same configuration in Kotlin DSL in your
.ktsfiles. Apply the Androidfullstoryplugin in your Android app module, as shown in the Android guide. - Set up iOS: Follow the Getting Started with iOS Data Capture help documentation for setting up Fullstory's iOS integration.
Continue Compose Multiplatform setup
After you set up the Fullstory Android and iOS SDKs, complete these steps to finish setting up your Compose Multiplatform app.
-
Update CMP: Determine the version of
fullstory-cmpyou are adding and update CMP to the corresponding version if needed (each version offullstory-cmpis tied to a specific version of CMP). Check that the two match before you apply the plugin. -
Add the Fullstory Maven repository: This is the same
https://maven.fullstory.comrepository the Android guide uses. If you added it to bothpluginManagementanddependencyResolutionManagementinsettings.gradle.ktswhile setting up Android, skip this step. Otherwise, add it only to the block that is missing it. Declare the repository once in each block:pluginManagement { repositories { maven { url = uri("https://maven.fullstory.com") } } } dependencyResolutionManagement { repositories { maven { url = uri("https://maven.fullstory.com") } } } -
Apply the
fullstory-cmpplugin:fullstory-cmpadds Compose Multiplatform capture on iOS. It does not replace the Androidfullstoryplugin from Set up Android. Keep both. Applyfullstory-cmpin the rootbuild.gradle.kts:plugins { id("fullstory-cmp") version "1.12.2" } -
Link against FullStory for dynamic frameworks (iOS only): If your app's shared Kotlin module is built as a dynamic framework, update the framework block to link against the iOS FullStory framework. In the shared module's
build.gradle.kts:kotlin { <iosTarget>.binaries.framework { ... linkerOpts( "-F", "path/to/directory/containing/FullStory.framework", // FrameworkSearchPath "-framework", "FullStory" ) } }
Fullstory CMP API
Fullstory provides a Kotlin library for accessing APIs on both platforms from shared code. It can be used to update selectors and privacy rules for Composables via Modifiers or interact with other existing Fullstory APIs like shutdown, restart, and event. The APIs safely no-op for platform targets other than Android or iOS, like desktop and wasm.
To use the API, add the library as a dependency to your Kotlin module's build.gradle.kts:
dependencies {
implementation("com.fullstory.cmp:fullstory-cmp-api:1.12.2")
}Then use any of the available APIs from your shared code. For example:
import com.fullstory.cmp.api.fsEvent
import com.fullstory.cmp.api.fsUnmask
...
Button(
modifier = Modifier.fsUnmask(),
onClick = {
fsEvent("customEvent", mapOf("stringProp" to "value", "intProp" to 4))
}
) { ... }Linking
The fullstory-cmp-api library is designed to not break your application even when fullstory-cmp or Fullstory is disabled. However, it does expect certain Fullstory symbols to be present even when capture is disabled or un-instrumented.
iOS
The iOS implementation is self-contained for Modifier API methods like fsUnmask, but other methods (like fsEvent) delegate to the FullStory framework.
If you include this library in a static framework, no additional configuration is needed as long as the app includes the FullStory framework.
When this library is included in a dynamic framework, follow the directions in Link against FullStory for dynamic frameworks (iOS only) above to link against the FullStory framework. If the framework may be included in an application without the FullStory framework, use -weak_framework instead of -framework, and make sure to only call Modifier APIs. A future release will make all APIs safely no-op when Fullstory is not present.
Android
The Android implementation delegates to the com.fullstory:compose library for Modifier API methods like fsUnmask and to com.fullstory:instrumentation-full for other methods (like fsEvent).
These dependencies are compileOnly, so make sure to add those libraries as dependencies when using the corresponding APIs if your module or library may be used in applications without Fullstory Compose support.
How CMP Capture Works on iOS
For Android, Compose instrumentation and capture is supported fully through the existing Android SDK and Gradle plugin, which supports the full range of Compose versions up to a certain maximum based on the Fullstory version.
For iOS, support is added through a fork of CMP, so each version of fullstory-cmp is tied to a specific version of Compose Multiplatform. Changes within the fork are minimal, and all existing public APIs are left unaffected to provide full binary compatibility with the original artifacts.
The fullstory-cmp Gradle plugin substitutes forked iOS artifacts into your project and can be turned on or off. This lets you add or remove the fork if the need arises, without changing code to work around divergent APIs.
When the FullStory framework performs a scan at runtime, it recognizes Compose views when the app was built with the plugin enabled and captures them. When the plugin is not enabled, the Compose views are not recognized by the framework and are skipped.
Limitations (iOS)
iOS capture through fullstory-cmp does not yet support everything that Android Compose capture does. Keep the following limitations in mind:
- Version pairing: Fullstory CMP support is tied to a specific version of CMP. They must be updated together.
- In-code privacy: Selector-based privacy is not yet supported. Privacy is controlled in-code only. Selectors may be configured and viewed in playback, but any privacy rule created in the web application is not respected at capture time.
- Synchronous scanning: Asynchronous scanning is not yet supported. Async settings, including slice time, do not affect the scanning of Compose content.
Releases
Each fullstory-cmp release lists the Gradle plugin and API library coordinates, the Compose Multiplatform version it supports, and the minimum Fullstory iOS framework version.
1.12.2
Release date: October 22, 2026
Release config:
- Gradle plugin:
id("fullstory-cmp") version "1.12.2" - API library:
implementation("com.fullstory.cmp:fullstory-cmp-api:1.12.2")
Supported versions:
- Compose Multiplatform: 1.12.2
-
FullStoryiOS framework: 1.75.0+
New features:
- Added support for capturing Paths (both drawing and clipping).
- Added capture of custom fonts.
1.12.0
Release date: September 3, 2026
Release config:
- Gradle plugin:
id("fullstory-cmp") version "1.12.0" - API library:
implementation("com.fullstory.cmp:fullstory-cmp-api:1.12.0")
Supported versions:
- Compose Multiplatform: 1.12.0
-
FullStoryiOS framework: 1.74.0+
New features:
- Initial CMP capture support