AppDefender.dev console is open for Client onboardinghello@appdefender.dev
Request access

Architecture

Standalone Native Security Bridge

AppDefender.dev is a standalone native security layer. React Native is only an integration surface. The Client never implements detection, policy, or KeysDefender.

Bridge diagram

                    CLIENT APP
              React Native Application
                       │
             ┌─────────▼─────────┐
             │ AppDefender RN SDK │
             │   Thin Adapter    │
             └─────────┬─────────┘
                       │
                 Native Bridge
                       │
              ┌────────▼─────────┐
              │ AppDefender.dev    │
              │ Native Security  │
              │      Core        │
              └────────┬─────────┘
                       │
          ┌────────────┼────────────┐
          ▼            ▼            ▼
       Android        iOS       Hardware/OS
       Security      Security     Security

Client integration

Install: npm install @appdefenderdev/sdk.react-native@1.0.5 or yarn add @appdefenderdev/sdk.react-native@1.0.5 (Bit .npmrc required).

import AppDefender from '@appdefenderdev/sdk.react-native';

AppDefender.initialize({
  appId: 'CLIENT_APP_ID',
  environment: 'production',
  dependencyCallback: (event) => {
    // Coordinate UI only. Native already enforced.
  },
});

const security = await AppDefender.launchSecurityCheck();
if (security.decision === 'BLOCK') {
  // Do not expose protected functionality
}

Public API

The bridge exposes capabilities, not sensors, C/C++ internals, or secure-storage material. Production without the native module fails closed. A callback never overrides BLOCK.

  • initialize
  • launchSecurityCheck
  • getSecurityState
  • onSecurityEvent
  • protectAction
  • getDependencyState
  • getKey (availability only — never AES key material)

React Native SDK