Custom Components let you surface content from your own app directly inside an Appcues mobile experience — a native view your developers build, dropped into a Flow step. Using one has two parts: your developers register the component in the app, then you add and configure it in the mobile builder.

Prerequisites

• A developer has registered the component in your app. The component's view and any actions it needs must be implemented in the app's code before it's available in the builder. Custom Components are supported on iOS and Android:
  • Android: Custom Component Configuring
  • iOS: Custom Component Configuring
• The app runs Appcues Mobile SDK 4.3.0 or later. On older SDKs the Custom Component block won't be available. If you don't see the option in the builder, this is the first thing to check.

Configure a component in Appcues (first use)

The first time a given component is used, configure it in Appcues so the builder knows about it.

1. In any mobile experience, add a block and select Custom Component.

2. Select Create new component. A modal appears where you enter the component's settings.

Add a Custom Component to an experience

1. In the mobile experience where you want the component, add a new block and select Custom Component.

2. Select one of the components you've configured to add it to the experience.

3. Select the added block to update the settings for that instance of the component.

Confirm it worked

• The configured component appears in the block list when you add a Custom Component block.
• Preview the Flow on a device and confirm the component renders with your app's native content.

If the Custom Component option isn't available

• Confirm the app runs Appcues Mobile SDK 4.3.0 or later.
• Confirm you're on iOS or Android — Custom Components aren't available on other platforms.

If the component doesn't render on your device

• Confirm a developer has registered the component in the app (see Prerequisites). A component that's configured in Appcues but not implemented in the app won't render.
• Confirm the component's identifier in Appcues matches the one registered in the app — casing and spacing must match.
• Use the Mobile Debugger to confirm the SDK is connected on the screen where you expect the component.

Still stuck?

Collect the following and contact support:

• The platform (iOS or Android) and the component identifier.
• Confirmation from your developers that the component is registered in the app.
• A screenshot or screen recording of the experience on the device.