React Native offerwall

From install to the first open.

Place the entry point in your rewards screen. Await initialization, check availability and remove reward listeners when the screen unmounts.

3. Connect your opt-in entry point

Replace the placeholders in your own app. Catch SDK errors in the calling screen, handle unavailable inventory and refresh balances from your server.

import RapidoReach, { RapidoReachEventEmitter }
  from '@rapidoreachsdk/react-native-rapidoreach';

export async function initializeRewards(refreshBalance) {
  await RapidoReach.initWithApiKeyAndUserId(
    'YOUR_API_TOKEN', 'YOUR_USER_ID'
  );
  const listener = RapidoReachEventEmitter.addListener(
    'onReward', () => refreshBalance()
  );
  return () => listener.remove(); // Call on unmount.
}

export function openRewards(showEmptyState) {
  RapidoReach.isSurveyAvailable((available) => {
    if (available) RapidoReach.showRewardCenter();
    else showEmptyState();
  });
}

Inspect the wall. Try the return flow.

These are screenshots of the public web playground, captured October 15, 2026. They show sample survey cards shared as a visual reference, not screenshots of a React Native native build or a guarantee of inventory.

React Native reward journeySimulation

This local interaction illustrates presentation states. It does not call the SDK, load live surveys or issue rewards.

AvailableLoadingEmptyOffline

Ready to explore

A survey is available in this simulated placement.

Open simulated reward center

Open the public widget playground ↗

The playground previews layout and themes. To validate React Native SDK behavior, use the package example and your own development app on a supported device.

Get the React Native package / example

Make the first reward traceable.

React Native acceptance checklist

1. Install and rebuild each native target; test a fresh install rather than only a hot reload.
2. Navigate away and back repeatedly to detect duplicate event subscriptions.
3. Refresh the server balance after a reward event and after returning from the wall.
4. Test loading, no inventory, offline, invalid credentials and retry. Reopen for the same user and verify attribution stays consistent.
5. Confirm your backend handles duplicate and invalid callback hashes, then review reversal handling before enabling live traffic.

Find the failing boundary.

Choose another integration path.