On this page

For AI agents: a documentation index is available at /docs/llms.txt. Append .md to any page URL for markdown, or send Accept: text/markdown.

Mobile Guides and Surveys

Mobile guides and surveys deliver in-app experiences in iOS, Android, Flutter, and React Native apps through the Guides and Surveys mobile SDK. They share the same builder as web guides and surveys but support a smaller set of form factors, survey blocks, and settings. For SDK setup, go to the documentation for your platform: iOS, Android, React Native, Flutter.

Use mobile guides and surveys for in-app experiences in a native mobile product. Use web guides and surveys for browser-based products.

Supported form factors

Mobile apps support modal, popover, pin, tooltip, banner, carousel, and card embed form factors. Checklist is web-only.

The carousel form factor is mobile-only. Banners on mobile use overlay mode only. Some tooltip settings apply only on web.

For each form factor's settings and properties, go to Guide form factors and properties.

Survey blocks by form factor

All four survey blocks (rating, long answer, short answer, and list) work on mobile modals, popovers, and pins.

Long answer and short answer blocks on pins and popovers require a mobile SDK version with keyboard input UI support. Go to the mobile SDK changelog for the minimum version per platform.

Web-only settings

These settings appear in the guide or survey builder but apply only on web. Amplitude enforces them at save time and prevents them from being applied to mobile guides and surveys.

Guides and surveys that had these settings applied before enforcement began continue to work as configured.

SDK version dependency

The Guides and Surveys builder accepts a layout as soon as the backend validates it. Whether end users see the experience depends on the mobile app bundling an SDK version that supports it.

Configure your guide or survey now. It reaches end users once the host app ships an update with a compatible SDK version. For feature-to-version mapping, go to the mobile SDK changelog.

Was this helpful?