MMKV for fast storage in React Native - Deep Dive

Overview - MMKV for fast storage

What is it?

MMKV is a fast and efficient key-value storage library for mobile apps. It stores data in a way that is quicker than traditional storage methods like AsyncStorage. MMKV helps apps save and retrieve small pieces of data, like user settings or tokens, very fast. It works on both Android and iOS platforms.

Why it matters

Mobile apps need to save data quickly to keep the user experience smooth and responsive. Without fast storage like MMKV, apps might freeze or slow down when saving or loading data. This can frustrate users and make apps feel slow or unreliable. MMKV solves this by making data storage almost instant, improving app speed and reliability.

Where it fits

Before learning MMKV, you should understand basic React Native concepts and how AsyncStorage works for storing data. After MMKV, you can explore advanced state management and offline data syncing techniques that rely on fast local storage.

Mental Model

Core Idea

MMKV is like a super-fast, tiny filing cabinet inside your phone that stores and finds your app’s important notes instantly.

Think of it like...

Imagine you have a small desk drawer where you keep your most-used pens and notes. Instead of searching through a big messy drawer every time, this small drawer is organized and right at your fingertips, so you can grab what you need immediately. MMKV is that small drawer for your app’s data.

┌───────────────┐
│   App Data    │
├───────────────┤
│  Key-Value    │
│  Storage      │
│  (MMKV)       │
├───────────────┤
│ Fast Access   │
│  (Memory +    │
│   Disk)       │
└───────────────┘

Build-Up - 7 Steps

1

Foundation

What is MMKV Storage

Concept: Introducing MMKV as a fast key-value storage solution for mobile apps.

MMKV is a storage library created by Tencent that uses memory-mapped files to store data. It is designed to be faster than AsyncStorage by reading and writing data directly in memory and syncing with disk efficiently. It supports storing strings, numbers, booleans, and more.

Result

You understand MMKV is a storage tool that helps apps save small pieces of data quickly and reliably.

Knowing MMKV is built for speed helps you appreciate why it can improve app performance compared to older storage methods.

2

Foundation

Basic Usage in React Native

Concept: How to install and use MMKV in a React Native app for simple data storage.

To use MMKV, install the react-native-mmkv package. Then create an MMKV instance and use its methods like set, getString, and delete to store and retrieve data. For example, you can save a user token and read it back quickly.

Result

You can write and read data using MMKV in your React Native app with simple commands.

Understanding the simple API lets you replace slower storage methods with MMKV easily.

3

Intermediate

How MMKV Achieves Speed

🤔Before reading on: do you think MMKV stores data only in memory or only on disk? Commit to your answer.

Concept: MMKV uses memory-mapped files to combine fast memory access with persistent disk storage.

MMKV maps a file on disk into memory, so reading and writing data happens in memory instantly. Changes are synced to disk efficiently in the background. This avoids slow file I/O operations common in other storage methods.

Result

You understand MMKV’s internal technique that makes it much faster than traditional file-based storage.

Knowing MMKV’s memory-mapping explains why it can read/write data so quickly without losing persistence.

4

Intermediate

Data Types and Serialization

🤔Before reading on: do you think MMKV can store complex objects directly or only simple types? Commit to your answer.

Concept: MMKV supports basic data types natively and requires serialization for complex objects.

MMKV can store strings, numbers, booleans, and byte arrays directly. For objects or arrays, you need to convert them to JSON strings before saving and parse them back when reading. This keeps storage simple and fast.

Result

You know how to handle different data types with MMKV correctly.

Understanding serialization needs prevents bugs and data corruption when storing complex data.

5

Intermediate

Handling Multiple MMKV Instances

Concept: MMKV allows creating multiple storage instances for different data scopes.

You can create separate MMKV instances with different IDs to isolate data, like one for user settings and another for app cache. This helps organize data and avoid conflicts.

Result

You can structure your app’s storage better by using multiple MMKV instances.

Knowing how to separate data scopes improves app maintainability and security.

6

Advanced

Encryption and Security Features

🤔Before reading on: do you think MMKV encrypts data by default or requires extra setup? Commit to your answer.

Concept: MMKV supports optional encryption to protect sensitive data.

MMKV can encrypt stored data using a key you provide. This protects user information like tokens or passwords from being read if the device is compromised. Encryption is optional and must be enabled explicitly.

Result

You can secure your app’s stored data using MMKV’s encryption features.

Knowing encryption options helps you build safer apps that protect user privacy.

7

Expert

Performance Considerations and Limits

🤔Before reading on: do you think MMKV is suitable for storing large files or only small key-value pairs? Commit to your answer.

Concept: MMKV is optimized for small to medium key-value data, not large files or databases.

While MMKV is very fast for small data, it is not designed to replace databases or file storage for large blobs. Using it for big data can cause memory pressure or slowdowns. For large data, use dedicated file storage or databases.

Result

You understand when MMKV is the right tool and when to choose other storage solutions.

Knowing MMKV’s limits prevents misuse that can degrade app performance or cause crashes.

Under the Hood

MMKV uses memory-mapped files, which means it links a file on disk directly into the app’s memory space. When the app reads or writes data, it accesses memory directly instead of going through slower file read/write calls. Changes are synced to disk asynchronously to keep data safe. This approach reduces CPU usage and speeds up data access.

Why designed this way?

Traditional storage methods like AsyncStorage rely on JSON files or SQLite, which involve slow parsing or disk I/O. Tencent designed MMKV to use memory mapping to avoid these bottlenecks. This design balances speed and persistence, making it ideal for mobile apps needing quick data access without complex databases.

┌───────────────┐       ┌───────────────┐
│   App Memory  │◄──────│ Memory-Mapped │
│  (Read/Write) │       │    File       │
└───────────────┘       └───────────────┘
         │                      │
         │ Sync changes         │
         ▼                      ▼
   ┌───────────┐          ┌───────────┐
   │  MMKV     │─────────▶│  Disk     │
   │  Library  │          │  Storage  │
   └───────────┘          └───────────┘

Myth Busters - 4 Common Misconceptions

Quick: Does MMKV automatically encrypt all stored data? Commit to yes or no.

Common Belief: MMKV encrypts all data by default to keep it safe.

Reality: MMKV does not encrypt data unless you explicitly enable encryption with a key.

Why it matters: Assuming data is encrypted by default can lead to storing sensitive info insecurely, risking user privacy.

Quick: Can MMKV replace a full database for all app data? Commit to yes or no.

Common Belief: MMKV can be used as a full database replacement for any data size.

Reality: MMKV is optimized for small key-value pairs, not large datasets or complex queries like databases.

Why it matters: Using MMKV for large data can cause performance issues and app crashes.

Quick: Does MMKV data persist after app uninstall? Commit to yes or no.

Common Belief: Data stored in MMKV stays on the device even after uninstalling the app.

Reality: MMKV data is stored in app-specific storage and is deleted when the app is uninstalled.

Why it matters: Expecting data to persist after uninstall can cause confusion in user data recovery scenarios.

Quick: Is MMKV usage identical on Android and iOS? Commit to yes or no.

Common Belief: MMKV works exactly the same way on Android and iOS without any platform differences.

Reality: While MMKV API is consistent, underlying implementations differ slightly due to platform constraints.

Why it matters: Ignoring platform differences can cause subtle bugs or unexpected behavior in cross-platform apps.

Expert Zone

1

MMKV’s memory-mapped files mean that data access speed depends on OS memory management, which can vary by device and OS version.

2

Using multiple MMKV instances can improve data isolation but may increase memory usage; balancing instance count is key for performance.

3

MMKV’s encryption adds CPU overhead; choosing when to encrypt data requires balancing security and app responsiveness.

When NOT to use

Avoid MMKV for storing large binary files, complex relational data, or when you need advanced querying capabilities. Use SQLite, Realm, or file storage instead for those cases.

Production Patterns

In production, MMKV is often used for caching user tokens, feature flags, app settings, and small offline data. It is combined with state management libraries to keep UI in sync with fast local storage.

Connections

Memory-Mapped Files

MMKV builds on the memory-mapped file concept used in operating systems.

Understanding memory-mapped files from OS theory helps grasp why MMKV is so fast and efficient.

Caching in Web Browsers

Both MMKV and browser caches store small data locally for fast access.

Knowing how browser caches work clarifies the role of MMKV as a local cache for mobile apps.

Human Short-Term Memory

MMKV’s fast memory access is like how humans keep important info in short-term memory for quick use.

This connection helps appreciate why keeping data in fast-access memory improves app responsiveness.

Common Pitfalls

#1 Trying to store large JSON objects directly without serialization.

Wrong approach:

mmkv.set('user', {name: 'Alice', age: 30}); // wrong, object not serialized

Correct approach:

mmkv.set('user', JSON.stringify({name: 'Alice', age: 30}));

Root cause:

MMKV only stores strings and primitive types directly; complex objects must be converted to strings.

#2 Assuming MMKV data persists after app uninstall.

Wrong approach:

// Expect data to remain
const token = mmkv.getString('token'); // after reinstall, token is null

Correct approach:

// Use server or backup to restore data after reinstall
// Do not rely on MMKV persistence beyond app lifecycle

Root cause:

MMKV stores data in app sandbox which is cleared on uninstall.

#3 Not enabling encryption for sensitive data.

Wrong approach:

mmkv.set('password', '12345'); // stored unencrypted

Correct approach:

const secureMMKV = new MMKV({encryptionKey: 'my_secret_key'});
secureMMKV.set('password', '12345');

Root cause:

Encryption is optional and must be explicitly enabled to protect data.

Key Takeaways

MMKV is a fast key-value storage library that uses memory-mapped files for quick data access in mobile apps.

It is much faster than traditional storage like AsyncStorage because it reads and writes data directly in memory.

MMKV supports basic data types natively and requires JSON serialization for complex objects.

Encryption is optional and must be enabled explicitly to secure sensitive data.

MMKV is ideal for small to medium data storage but not suitable for large files or complex databases.