expo-sqlite/kv-store

This is the default storage adapter: Expo's SQLite-backed key/value store behind src/lib/storage.ts. I'd keep it unless you have a reason not to - it runs in Expo Go and gives you sync reads on native, so the built-in stores hydrate before first paint. Pick mmkv if you're already on a dev build and want the fastest possible reads, and async-storage only when a library hard-requires it. Whichever one you choose, callers only ever import storage from @/lib/storage; the StorageAdapter interface and createMemoryStorage() for tests live in core src/lib/storage-adapter.ts.

SetupCopy Anchor Link

bun run setup --storage kv-store

That's it - setup writes src/lib/storage.ts (createKvStoreStorage() plus the active storage) and adds the expo-sqlite dependency and its config plugin through .readynative.json → app.config.ts.

UsageCopy Anchor Link

import { storage } from "@/lib/storage";

await storage.setItem("readynative:draft", JSON.stringify(draft));
const raw = await storage.getItem("readynative:draft");
await storage.removeItem("readynative:draft");

storage.getItemSync?.("readynative:draft"); // native only

The built-in stores (src/stores/create-store.ts), zustand persist / Jotai atomWithAppStorage and i18n all go through this adapter, so you rarely call it directly.

GotchasCopy Anchor Link

• Expo Go works.
• getItemSync is native-only - on web it's undefined, so always have an await path.
• Values are strings; serialize objects yourself (the built-in stores already do).
• Swapping stacks: bun run setup --storage mmkv or --storage async-storage replaces src/lib/storage.ts and nothing else. Keys stay the same readynative:* strings, but the data lives in a different backend, so existing values do not move - users start fresh on theme mode, onboarding and language. No migration ships.

Remove itCopy Anchor Link

Every app needs a storage option, so there is no none to fall back to - you switch instead. While modules/ exists (a tree set up with --keep-modules), one call does it:

bun run setup --storage mmkv --yes --keep-modules

A finalized tree can't switch: clone a fresh copy of your tier repo, run setup there with the new option and port your code across - see Can I change a module after setup?.

ReferenceCopy Anchor Link

Everything below is generated from modules/storage/kv-store/module.json - the same file bun run setup reads, so it is what actually lands in your repo.

InstallCopy Anchor Link

bun run setup --storage kv-store

Module id: storage/kv-store (the default for this category).

DependenciesCopy Anchor Link

Config pluginsCopy Anchor Link

Merged into app.config.ts through .readynative.json (modules.app):

• expo-sqlite

PrivacyCopy Anchor Link

Required-reason APIs: UserDefaults (CA92.1), FileTimestamp (C617.1).

FilesCopy Anchor Link