featbit-react-native-sdk

# FeatBit React Native SDK

Guidance for integrating FeatBit feature flags into React Native apps. This SDK is client-side and intended for single-user contexts (mobile, desktop, or embedded apps).

## Activates When

- The user asks about FeatBit React Native SDK setup or initialization.
- The user is integrating feature flags in React Native apps.
- The user needs to evaluate flags or wire up `withFbProvider`/`asyncWithFbProvider`.

## Overview

The React Native SDK builds on FeatBit’s React Client SDK (which depends on the JavaScript client SDK). Most React Client SDK functionality is available; the key difference is how initialization is done in React Native.

## Core Knowledge Areas

### 1) Installation and prerequisites

- Install: `npm install @featbit/react-native-sdk`
- Required values: environment secret (`sdkKey`), streaming URL, and events URL
- Docs for values:
  - https://docs.featbit.co/sdk/faq#how-to-get-the-environment-secret
  - https://docs.featbit.co/sdk/faq#how-to-get-the-sdk-urls
  - `customizedProperties` is an array of `{ name, value }` pairs for user attributes.

### 2) SDK initialization

- Build the config with `buildConfig({ options })`
- Initialize using one of:
  - `withFbProvider`
  - `asyncWithFbProvider`

### 3) Flag evaluation in components

- Use `useFlags()` to read flag values in components
- Example: show UI based on a flag value (e.g., `robot === 'AlphaGo'`)

### 4) Identifying users after initialization

- Use `useFbClient()` from `@featbit/react-client-sdk`, then call `fbClient.identify(user)`
- This pattern comes from the React Client SDK and applies to React Native when using the same hooks.

## Best Practices

1. **Create a single config instance**: Build config once with `buildConfig({ options })` and reuse it at app entry.
2. **Provide required user fields**: Ensure `user.keyId` and `user.name` are set in `options`.
3. **Keep secrets out of source**: Use environment variables or secure storage for `sdkKey` and URLs.
4. *