MMKV for fast storage in React Native - UI Render Trace

Component - MMKV for fast storage

This React Native component demonstrates how to use MMKV, a fast key-value storage library, to save and retrieve data quickly on mobile devices. It shows a simple UI with a text input, a save button, and a display area for stored data.

Widget Tree

View
├── TextInput
├── Button
└── Text

The root View contains three children stacked vertically: a TextInput for user input, a Button to save the input, and a Text component to display the saved value.

Render Trace - 4 Steps

Step 1: View

Step 2: TextInput

Step 3: Button

Step 4: Text

State Change - Re-render

Trigger:User types text and presses the 'Save to MMKV' button

Before

inputValue is the typed text; storedValue shows previous saved data or empty

→

After

storedValue updates to the new inputValue saved in MMKV

Re-renders:The entire component rerenders, updating TextInput and Text with new values

UI Quiz - 3 Questions

What happens when you press the 'Save to MMKV' button?

A The app crashes because MMKV is not supported

B The input field clears but nothing is saved

C The typed text is saved to MMKV storage and displayed below

D The button changes color but no data is saved

Key Insight

Using MMKV in React Native apps allows developers to store data quickly and efficiently with minimal delay, improving app responsiveness. The UI reflects this by instantly showing saved data after pressing the save button, giving users immediate feedback.

Practice

1. What is the main purpose of using MMKV in a React Native app?

easy

A. To design app layouts

B. To store small data quickly and keep it after app closes

C. To handle network requests

D. To create complex animations

Solution

1. Step 1: Understand MMKV's role

   MMKV is designed for fast storage of small data in apps.

2. Step 2: Compare options

   Options A, B, and C relate to app layouts, animations, and networking, which are not MMKV's purpose.

3. Final Answer:

   To store small data quickly and keep it after app closes -> Option B

4. Quick Check:

   MMKV = fast persistent storage [OK]

Hint: MMKV is for fast data storage, not UI or network [OK]

Common Mistakes:

• Confusing MMKV with UI or animation libraries
• Thinking MMKV handles network calls
• Assuming MMKV is for large file storage

2. Which of the following is the correct way to save a string value using MMKV in React Native?

easy

A. MMKV.set('key', 'value')

B. MMKV.save('key', 'value')

C. MMKV.store('key', 'value')

D. MMKV.put('key', 'value')

Solution

1. Step 1: Recall MMKV save method

   The correct method to save data is set.

2. Step 2: Check other options

   Methods like save, store, and put are not valid MMKV methods.

3. Final Answer:

   MMKV.set('key', 'value') -> Option A

4. Quick Check:

   Use set() to save data [OK]

Hint: Use set() to save data in MMKV [OK]

Common Mistakes:

• Using incorrect method names like save or put
• Confusing MMKV with AsyncStorage syntax
• Forgetting to pass both key and value

3. What will be the output of this code snippet?

const MMKV = require('react-native-mmkv').MMKV;
const storage = new MMKV();
storage.set('name', 'Alice');
const result = storage.getString('name');
console.log(result);

medium

A. undefined

B. null

C. 'Alice'

D. Error: getString is not a function

Solution

1. Step 1: Analyze storage.set call

   The code saves the string 'Alice' with key 'name'.

2. Step 2: Analyze storage.getString call

   Retrieves the string stored under 'name', which is 'Alice'.

3. Final Answer:

   'Alice' -> Option C

4. Quick Check:

   getString('name') returns 'Alice' [OK]

Hint: getString returns saved string value [OK]

Common Mistakes:

• Expecting undefined if not awaited
• Confusing getString with get() method
• Assuming getString returns null if key exists

4. Identify the error in this MMKV usage code:

const storage = new MMKV();
storage.set('count', 5);
const value = storage.getString('count');
console.log(value);

medium

A. Using getString to read a number value

B. Missing await before storage.set

C. MMKV constructor requires parameters

D. set method only accepts strings

Solution

1. Step 1: Check data type saved

   The code saves a number 5 using set.

2. Step 2: Check retrieval method

   getString expects a string value, but 'count' stores a number, causing mismatch.

3. Final Answer:

   Using getString to read a number value -> Option A

4. Quick Check:

   getString expects string data [OK]

Hint: Match getString with string data only [OK]

Common Mistakes:

• Trying to getString for non-string data
• Assuming set is async and needs await
• Thinking MMKV constructor needs arguments

5. You want to save a user's theme preference ('dark' or 'light') and retrieve it safely after app restart using MMKV. Which code snippet correctly does this?

hard

A. const storage = new MMKV();
storage.set('theme', 'dark');
const theme = storage.getString('theme');

B. const storage = new MMKV();
storage.set('theme', 'dark');
const theme = storage.get('theme');

C. const storage = new MMKV();
storage.save('theme', 'dark');
const theme = storage.getString('theme');

D. const storage = new MMKV();
storage.set('theme', 'dark');
const theme = storage.getString('theme') ?? 'dark';

Solution

1. Step 1: Save theme preference correctly

   Use set to save the string 'dark' under 'theme'.

2. Step 2: Retrieve with fallback

   Use getString('theme') and fallback to 'dark' if null or undefined using ??.

3. Final Answer:

   const storage = new MMKV(); storage.set('theme', 'dark'); const theme = storage.getString('theme') ?? 'dark'; -> Option D

4. Quick Check:

   Use set() and getString() with nullish fallback [OK]

Hint: Use ?? for safe fallback when reading MMKV data [OK]

Common Mistakes:

• Using non-existent save() method
• Not providing fallback value on getString
• Using get() instead of getString for strings