Install Userflow React Native SDK with AI

The Userflow React Native Installation Skill installs the Userflow React Native SDK into your app through your AI coding agent. The agent reads your codebase, works out where initialization, identification, and screen tracking belong, writes the code, and checks the result.

It works with Expo (including Expo Router) and bare React Native apps. Installing on a website instead? Use Install with AI.

Before you start

You'll need:

• A Userflow account with access to Settings → Environments

• An AI coding agent with access to your project files — Claude Code, Cursor, GitHub Copilot, Codex, Windsurf, and others all work

• A React Native app on version 0.76 or later, or an Expo app on Expo SDK 57 or earlier, for iOS or Android

• A development build to test in. Expo Go can't run the SDK

• No Userflow MCP server required

Step 1: Get your client token and scheme ID

Userflow issues a separate client token for each environment. Take the token for the environment this build targets — a Production token in a Staging build will mix content and users across both.

1. Open Settings in Userflow, then select Environments.

2. Copy the client token for the environment you're installing into.

You'll also need the environment's scheme ID. It lets you pair a device with the Builder and open preview links in your app.

Keep both nearby — your agent will ask for them. If your environment uses identity verification, don't share your secret key with the agent. It belongs only on your backend.

Step 2: Add the skill to your agent

Quickest route—paste this into your agent's chat. Nothing to install:

Install Userflow in this React Native app.
Use the Userflow React Native installation skill:
https://raw.githubusercontent.com/userflow/ai-skills-library/refs/heads/main/skills/install-userflow-react-native-sdk-with-ai/SKILL.md

To add it permanently with the Claude Code plugin or skills.sh, see Add Userflow coding skills to your agent. In Claude Code, run /userflow:install-userflow-react-native-sdk-with-ai once it's added.

Download:

Step 3: Run the skill

Open your coding agent with access to your project and ask it to install Userflow.

The skill reads your codebase before it asks you anything, then confirms what it found — Expo or bare React Native, your router, where users sign in and out, and which field to use as the user ID. Once you confirm, it writes the installation.

Expect it to ask for your client token and scheme ID, whether your environment uses identity verification, and — if you already run Userflow on the web — whether the user ID matches.

What the skill does

• Reads your codebase first, so you're not answering questions your code already answers — framework, router, package manager, and auth flow.

• Installs versions that fit your app, so the SDK and its native dependencies work with your Expo or React Native version.

• Identifies only signed-in users. Identification runs after sign-in and when a signed-in user reopens the app, and resets on sign-out. Anonymous users aren't identified, which protects your Monthly Active User count.

• Sets up screen tracking for Expo Router or React Navigation, so flows can target the right screens.

• Lets you select elements on your device. It adds a build step so you can pick tooltip targets on a paired device in the Builder, without adding an ID to each element.

• Asks before anything destructive, such as cleaning native folders or upgrading Expo or React Native.

• Leaves a note in AGENTS.md recording how Userflow is installed, so future agent sessions extend the setup instead of installing it a second time.

The default installation is deliberately minimal. Anonymous identification, groups, event tracking, and identity verification are added only if you ask for them — or, for identity verification, if your environment requires it.

If you don't have codebase access

Tell the skill you're scoping the work for a developer. Instead of writing code, it produces a USERFLOW_RN_INSTALL_SPEC.md file containing the install commands, where the token and scheme ID come from, the exact code with your user ID field named, and a verification checklist.

The spec is self-contained, so your developer can implement it without seeing your conversation.

Step 4: Verify the installation

The agent runs the checks it can in your codebase. Then:

1. Rebuild and launch the native app. A Metro reload isn't enough.

2. Sign in as a test user and check the dev console shows no [Userflow] warnings.

3. In the Builder, open Preview → Pair a device, scan the QR code, then press Preview. Your app shows a "Preview mode" bar.

4. Select a tooltip target on the device.

That last check matters most. If you can select an element on the device, pairing and on-device element selection are both working.

Troubleshooting

The app won't run in Expo Go

Expected. The SDK needs a development build. Ask your agent to run one for iOS or Android.

Pairing or preview links don't open the app

Check that the scheme ID is set, then rebuild the native app. Deep-link changes only take effect after a rebuild.

You can't select an element on the device

Restart Metro with a cleared cache and try again. If it still fails, ask your agent to confirm the Userflow build step is in place.

The app reports an invalid token

The client token doesn't match the environment. Check that each build uses the ct_ token for its own environment.

Still stuck

Search your device logs for [Userflow], ask your coding agent to explain what it installed, or contact Userflow support.

The skill writes real code into your project. Review what your agent produces before merging or shipping a build. Human oversight is recommended for every installation.