The Jetpack Compose low-code plugin is available starting with Android SDK 3.6.0. It supports the following capabilities:
- Self-serve tagging in Pendo's Visual Design Studio
- Tagging Pages
- Tagging Features
- Retroactive analytics
- Page view events
- Feature click events
- Guides
- Lightbox guides activated by a Page view
- Lightbox guides activated by a Feature click
- Tooltip guides
For installation instructions, go to Github.
Get started with Jetpack Compose low-code solution
If you're currently using the Jetpack Compose Track Event solution, see the installation guide on Github. All existing Track Events will continue to function as usual. The low-code solution doesn't replace Track Events. It only adds more information on top of them.
Tag Pages and Features in Jetpack Compose
There are several ways to tag Pages and Features in Jetpack Compose.
If you can't tag certain Features, refer to Current limitations with modal components and Current limitations with dynamic components, and verify that the element you're tagging is clickable.
If you're still unable to tag a Page or Feature, contact Pendo Support.
Current limitations with modal components
Feature identification and click analytics aren't supported for additional windows, including modals, ModalBottomSheets, panels, dialogs, and pop-ups.
Tooltip guides also aren't supported in these components.
Pop-ups aren't detected as new screens, so elements inside them can't be tagged.
For Drawer or ModalBottomSheetLayout, follow step 3.2 in the installation guide to configure Modifier.pendoStateModifier(componentState) correctly. You must update bottomSheetState or drawerState when you no longer want Pendo to detect the page.
When Drawer or ModalBottomSheetLayout is open, elements from the background screen might still be detected by Pendo. This can result in extra click analytics and "ghost elements" when capturing these screens. We plan to resolve this before the general release of Jetpack Compose.
Current limitations with dynamic components
Screens with continuous animations won't detect content until the animation stops. Use the screenContentChangeAPI to detect content changes.