React Native state management

Keep changing data predictable and make every screen show the current source of truth.

Chapter goal: Keep changing data predictable and make every screen show the current source of truth.

Simple explanation

State is the current memory of an app or screen. A source of truth is the one place that owns the correct current value.

In React Native, this chapter is about deciding who owns changing data and who is allowed to update it. Start with the idea above. Then connect each symbol to a value or action in the example.

Do not try to remember every symbol. First ask what data the program has, what it does with that data, and what result it creates. Technical words become easier when you connect them to those three questions.

Why this topic is important

Unclear state causes stale screens, duplicated values, and changes that are difficult to trace. In React Native, the syntax may look different from other languages, but the thinking skill transfers: name the data, choose the right operation, and make the next step obvious.

When to use it

Manage state for counters, forms, authentication, carts, loading, errors, filters, and cached server data.

Example code

function Counter() {
  const [count, setCount] = useState(0);
  return <Button title={`Count: ${count}`} onPress={() => setCount(count + 1)} />;
}

Line-by-line explanation

• function Counter() { — This defines a reusable function. Its name describes the job that other code can call.
• const [count, setCount] = useState(0); — This stores or updates setCount]. The value on the right is worked out first, then saved under that name.
• return <Button title={\Count: ${count}`} onPress={() => setCount(count + 1)} />;` — This sends a result back to the code that called the function. Returning is different from printing.

What the output means

UI output: the button shows "Count: 0" first. Each press re-renders it with the next number.

The output is evidence that the program followed the instructions. If your result is different, read from the first line and write down how each value changes. That is debugging, not failure.

Mistake example

function Counter() {
  const [count, setCount] = null; // the same state is stored in more than one place
  return <Button title={`Count: ${count}`} onPress={() => setCount(count + 1)} />;
}

This version intentionally shows how the same state is stored in more than one place. The changed assignment stores a missing value, or a required line is removed, so later code cannot complete its job safely.

Fixed version

function Counter() {
  const [count, setCount] = useState(0);
  return <Button title={`Count: ${count}`} onPress={() => setCount(count + 1)} />;
}

The corrected version restores the real value or required operation. It fixes the chapter-specific problem: the same state is stored in more than one place.

Common mistakes

• Keeping the same state in several places.
• Changing state without notifying its readers.
• Using app-wide state for a value needed by one small component.

Warning: Change one part at a time. If you change many lines together, it becomes harder to learn which change caused the result.

Real use cases

• Update a Flutter widget after setState.
• Manage React state with hooks.
• Track server-owned player state safely in RedM.

Small real-project example

A name form owns its own typed value and only reveals the result after the user submits.

function NameForm() {
  const [name, setName] = useState("");
  const [submitted, setSubmitted] = useState(false);

  return (
    <View>
      <TextInput value={name} onChangeText={setName} placeholder="Your name" />
      <Button title="Save" onPress={() => setSubmitted(true)} />
      {submitted && <Text>Saved: {name}</Text>}
    </View>
  );
}

How the project example works

• name is the state this component owns; it starts empty.
• onChangeText updates name on every keystroke through setName.
• submitted is a second, independent piece of state for whether Save was pressed.
• The saved text only appears once submitted becomes true, proving state controls what renders.

Practice exercise

1. Add a reset action.
2. Keep one source of truth.
3. Explain which code owns the state and which code only reads it.

Tip: If the exercise feels too large, complete only steps 1 to 3. Small working code teaches more than a large unfinished project.

Mini quiz

1. What is a source of truth?
2. Who is allowed to change the state?
3. What causes a stale screen?

How to read AI-generated code

Do not copy AI code first. Read it like a detective. Find the data, follow the changes, and locate the final output. Ask AI to explain a line only after you have made your own guess.

• What data goes in?
• What values are stored?
• What calculation or decision happens?
• What is printed, displayed, saved, or returned?
• What can go wrong?
• Can you rename one value and still explain the code?

React Native reading check

Find the component inputs (props), changing values (state), event handlers, and effects. An effect that fetches data must also handle loading, failure, and a component that leaves the screen.

Before you move on

• I can explain this topic in my own words.
• I can read the small example without AI.
• I can change the example and predict the new result.
• I can find and fix one simple mistake.
• I can name one real project that uses this idea.

Next topic

Next, learn best practices and clean code. Before opening it, explain this chapter out loud in under one minute.