Ask anything official about AppDefender.dev. I only answer from approved knowledge. I do not invent capabilities, and I do not enforce policy.
docs.appdefender.dev
AppDefender.dev documentation
Private Client-app security for React Native, Flutter, Ionic/Capacitor, Cordova, and Web. Launch Security Gate, Offline Threat Handling, ATS Lite/Full. Super Admin issues a private package and read token — never a public listing.
Architecture
AppDefender, CodeDefender, KeysDefender, CryptoEngine, OfflineThreatHandler, ApiDefender, ATS.
Native Security Bridge
Thin RN adapter. Native core owns ALLOW / RESTRICT / BLOCK.
Offline Threat Handling
Mandatory launch-gate engine. Cached policy + local detection. Network never overrides BLOCK.
CryptoEngine
SHA-256 / AES-256-GCM baseline. Client-configurable. SHA-1 is legacy only. No keys in JS.
KeysDefender
Google Maps, MoEngage, Juspay, Firebase, and payment keys. Envelope encryption. KP1 tokens. Native unwrap after ALLOW — never in JS.
Client integration
Private Bit install. RN, Flutter, Ionic, Cordova, and web. Your API still enforces.
React Native SDK
npm/yarn @appdefenderdev/sdk.react-native@1.0.5 — initialize, launchSecurityCheck, KeysDefender.initializeSDK.
Web SDK
npm/yarn @appdefenderdev/sdk.web@1.0.4 or CDN. Public App ID. Remote policy. No secrets in the page.
DLT, OTP, SMVDefender
TRAI DLT in the backend. SDK OTP with a public App ID only. SMSV + SMVDefender.
Client advisories
Advisory Center, notification engine, SDK lifecycle, application security health.
CXO deck
24-slide operator briefing — launch gate, crypto policy, Super Admin, pilot.