Zustand as lightweight alternative in React Native - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Zustand in React Native development?

Zustand is a small, fast, and scalable state management library for React and React Native apps. It helps manage app state with minimal setup and boilerplate.

intermediate

How does Zustand differ from Redux?

Zustand is simpler and lighter than Redux. It requires less code, no reducers or actions, and uses hooks directly for state access and updates.

beginner

Show a basic example of creating a Zustand store.

import create from 'zustand';
const useStore = create(set => ({
  count: 0,
  increment: () => set(state => ({ count: state.count + 1 }))
}));

This creates a store with a count and an increment function.

beginner

Why is Zustand considered a lightweight alternative for state management?

Because it has a small bundle size, minimal API, no boilerplate code, and uses React hooks directly, making it easy and fast to use.

intermediate

What are some benefits of using Zustand in React Native apps?

Benefits include simple API, no need for context providers, easy to learn, good performance, and flexibility to manage local and global state.

Which of the following best describes Zustand?

A A lightweight state management library using hooks

B A UI component library for React Native

C A navigation library for React Native

D A testing framework for React Native apps

Zustand is a lightweight state management library that uses React hooks.

How do you update state in Zustand?

A By dispatching actions and reducers

B By calling set function inside the store

C By using context providers

D By using Redux middleware

Zustand updates state by calling the set function provided in the store definition.

Which hook do you use to access Zustand store state?

A useContext

B useEffect

C useState

D useStore (custom hook from Zustand)

Zustand provides a custom hook (usually named useStore) to access and update state.

What is a key advantage of Zustand over Redux?

A Simpler API with less setup

B Uses reducers and actions

C Requires more boilerplate code

D Requires middleware for async

Zustand has a simpler API and requires less setup compared to Redux.

Zustand can be used to manage which types of state?

A Only local component state

B Only global app state

C Both local and global state

D Only navigation state

Zustand can manage both local and global state in React Native apps.

Explain how Zustand simplifies state management in React Native compared to Redux.

Think about how you write less code and use hooks directly.

Describe a basic example of creating and using a Zustand store in a React Native app.

Focus on the minimal code needed to create and use the store.

Practice

1. What is the main purpose of Zustand in React Native apps?

easy

A. To manage app state in a simple and lightweight way

B. To create complex animations

C. To handle network requests

D. To style components with CSS

Solution

1. Step 1: Understand Zustand's role

   Zustand is designed to manage state, which means keeping track of data that changes in the app.

2. Step 2: Compare options to Zustand's purpose

   Options B, C, and D relate to animations, network, and styling, which are not Zustand's focus.

3. Final Answer:

   To manage app state in a simple and lightweight way -> Option A

4. Quick Check:

   Zustand = simple state management [OK]

Hint: Zustand is about state, not styling or animations [OK]

Common Mistakes:

• Confusing Zustand with animation libraries
• Thinking Zustand handles network calls
• Assuming Zustand is for styling

2. Which of the following is the correct way to create a Zustand store in React Native?

easy

A. const useStore = new Store({ count: 0, increment: () => count++ })

B. const useStore = create(set => ({ count: 0, increment: () => set(state => ({ count: state.count + 1 })) }))

C. const useStore = createStore({ count: 0, increment() { count++ } })

D. const useStore = createStore(() => ({ count: 0, increment: () => count++ }))

Solution

1. Step 1: Recall Zustand store syntax

   Zustand uses the create function with a callback that receives set to update state.

2. Step 2: Check each option's syntax

   const useStore = create(set => ({ count: 0, increment: () => set(state => ({ count: state.count + 1 })) })) matches Zustand's pattern with create and set. Options A, B, and D use incorrect functions or syntax.

3. Final Answer:

   const useStore = create(set => ({ count: 0, increment: () => set(state => ({ count: state.count + 1 })) })) -> Option B

4. Quick Check:

   Use create with set callback = const useStore = create(set => ({ count: 0, increment: () => set(state => ({ count: state.count + 1 })) })) [OK]

Hint: Zustand store uses create() with set callback [OK]

Common Mistakes:

• Using createStore instead of create
• Not passing set function
• Incorrect increment function syntax

3. Given this Zustand store code:

const useStore = create(set => ({ count: 0, increment: () => set(state => ({ count: state.count + 1 })) }))

function Counter() {
  const count = useStore(state => state.count)
  const increment = useStore(state => state.increment)
  increment()
  return {count}
}

What will be displayed when Counter renders?

medium

A. undefined

B. 1

C. 0

D. Error

Solution

1. Step 1: Understand state updates in render

   The increment function is called inside the component body, but React state updates are asynchronous and won't reflect immediately in the same render.

2. Step 2: Determine displayed count value

   Since increment updates state after render, the displayed count remains the initial 0 during this render.

3. Final Answer:

   0 -> Option C

4. Quick Check:

   State updates async, initial render shows 0 [OK]

Hint: State changes don't show immediately in same render [OK]

Common Mistakes:

• Assuming increment updates count instantly
• Expecting count to be 1 immediately
• Confusing state update timing

4. Identify the error in this Zustand store code:

const useStore = create(set => ({
  count: 0,
  increment: () => set({ count: count + 1 })
}))

medium

A. Using count without accessing state inside set

B. Missing initial count value

C. Using arrow function incorrectly

D. Not returning an object from create

Solution

1. Step 1: Check how count is used in set

   The increment function uses count directly, but count is not defined in that scope; it should access state.count.

2. Step 2: Correct usage of set with state

   set should receive a function with state parameter to get current count: set(state => ({ count: state.count + 1 })).

3. Final Answer:

   Using count without accessing state inside set -> Option A

4. Quick Check:

   Access state.count inside set callback [OK]

Hint: Use set(state => ...) to access current state [OK]

Common Mistakes:

• Using count variable directly instead of state.count
• Not passing function to set
• Ignoring state parameter in set callback

5. You want to add a reset function to this Zustand store that sets count back to zero. Which is the correct way?

const useStore = create(set => ({
  count: 0,
  increment: () => set(state => ({ count: state.count + 1 })),
  reset: ???
}))

hard

A. () => set(state => ({ count: null }))

B. () => set({ count: state.count - state.count })

C. () => set({ count: state.count * 0 })

D. () => set({ count: 0 })

Solution

1. Step 1: Understand reset goal

   The reset function should set count directly to zero, ignoring current state.

2. Step 2: Evaluate each option

   () => set(state => ({ count: null })) sets count to null (wrong). Options B and C reference state.count directly in set({ ... }) but state is undefined there (error). () => set({ count: 0 }) correctly sets { count: 0 } directly.

3. Final Answer:

   () => set({ count: 0 }) -> Option D

4. Quick Check:

   Reset sets count directly to zero [OK]

Hint: Reset sets count directly to 0 without state calculation [OK]

Common Mistakes:

• Using calculations instead of direct assignment
• Setting count to null instead of zero
• Overcomplicating reset function