Native Datastore

Store persistent key-value data in encrypted native OS storage. Nativine embeds native iOS UserDefaults / Keychain and Android EncryptedSharedPreferences / Room bridges, bypassing web LocalStorage size limits and domain isolation restrictions.

1. Overview & Native Capabilities

Browser LocalStorage can be cleared by Safari/Chrome OS cleanup policies or domain changes. Nativine's Native Datastore plugin provides un-clearable, encrypted hardware storage:

• Encrypted Auth Tokens: Store Sensitive JWT auth tokens, refresh keys, and user settings inside iOS Keychain & Android KeyStore.
• Cross-Domain Data Persistence: Access stored keys even if your application navigates across different web domains or sub-domains.
• Un-clearable Storage: Data stored in Native Datastore persists across web view clears and browser cache resets.

2. No-Code App Builder Setup Guide

Nativine App Builder Configuration

1. Open the Nativine App Builder at /web-to-app-converter-pro.
2. Click Add-ons & Plugins in the left builder menu and locate Native Datastore.
3. Toggle Native Datastore to ON (or click Enable), then click Config.
4. Configure your required settings, permissions descriptors, or target web parameters.
5. Click Save Config and navigate to the Builds tab to compile your mobile application.

3. Native JS Bridge API Reference

To read, write, or remove key-value items in Native Datastore from JavaScript, call nativine.datastore.setItem():

// Store value in encrypted datastore
nativine.datastore.setItem({
  key: 'auth_session_token',
  value: 'eyJhbGciOiJIUzI1NiIsInR5c...',
  isEncrypted: true
});

// Retrieve value
nativine.datastore.getItem({
  key: 'auth_session_token',
  callback: 'onTokenRetrieved'
});

function onTokenRetrieved(result) {
  console.log("Stored Token:", result.value);
}

Parameters

4. Frequently Asked Questions (Q&A)