Why useState hook in React Native? - Purpose & Use Cases

The Big Idea

Discover how a tiny hook can save you from endless manual UI updates!

The Scenario

Imagine building a mobile app where you have to update the screen every time a user types in a form or taps a button, but you do it by manually changing the display each time.

The Problem

Manually updating the screen is slow, easy to forget, and causes bugs because you have to track every change yourself and update the UI perfectly each time.

The Solution

The useState hook lets you store and update values easily, and React Native automatically updates the screen when those values change, so you don't have to do it yourself.

Before vs After

✗ Before

let count = 0;
function increment() {
  count++;
  updateScreen(count);
}

✓ After

const [count, setCount] = React.useState(0);
function increment() {
  setCount(count + 1);
}

What It Enables

It enables building interactive apps that respond instantly to user actions without messy manual updates.

Real Life Example

Think of a like button in a social app that updates the number of likes immediately when tapped, without you having to write extra code to refresh the display.

Key Takeaways

Manually updating UI is error-prone and slow.

useState hook manages state simply and updates UI automatically.

This makes building interactive React Native apps easier and more reliable.

Practice

1. What does the useState hook do in a React Native component?

easy

A. It fetches data from an external API automatically.

B. It styles the component with CSS properties.

C. It allows the component to remember and update values over time.

D. It creates a new screen in the app navigation.

Solution

1. Step 1: Understand the purpose of useState

   The useState hook is designed to let components keep track of values that can change, like user input or toggles.

2. Step 2: Compare options with useState's role

   Only It allows the component to remember and update values over time. correctly describes this behavior. Styling, fetching data, or navigation are handled by other tools.

3. Final Answer:

   It allows the component to remember and update values over time. -> Option C

4. Quick Check:

   useState manages state = A [OK]

Hint: Remember: useState stores and updates values inside components [OK]

Common Mistakes:

• Confusing useState with styling or navigation
• Thinking useState fetches data automatically
• Believing useState creates new screens

2. Which of the following is the correct way to declare a state variable called count with initial value 0 using useState?

easy

A. const [count, setCount] = useState;

B. const [count, setCount] = useState(0);

C. const count, setCount = useState(0);

D. const count = useState(0);

Solution

1. Step 1: Recall useState syntax

   The correct syntax uses array destructuring: const [state, setState] = useState(initialValue);

2. Step 2: Check each option

   const [count, setCount] = useState(0); matches the correct syntax. const count = useState(0); misses destructuring, C uses comma incorrectly, and A misses parentheses.

3. Final Answer:

   const [count, setCount] = useState(0); -> Option B

4. Quick Check:

   useState syntax = D [OK]

Hint: Use array destructuring with useState and provide initial value [OK]

Common Mistakes:

• Not using array destructuring
• Forgetting parentheses after useState
• Using commas instead of brackets

3. What will be displayed on the screen after the button is pressed twice in this React Native component?

import React, { useState } from 'react';
import { View, Text, Button } from 'react-native';

export default function Counter() {
  const [count, setCount] = useState(0);
  return (
    
      {count}
       setCount(count + 1)} />
    
  );
}

medium

A. 2

B. 0

C. 1

D. Error: setCount is not a function

Solution

1. Step 1: Understand initial state and button action

   The initial count is 0. Each button press calls setCount(count + 1), increasing count by 1.

2. Step 2: Calculate count after two presses

   After first press: count = 1. After second press: count = 2. The displayed text updates accordingly.

3. Final Answer:

   2 -> Option A

4. Quick Check:

   Two increments from 0 = 2 [OK]

Hint: Each press adds 1 to count starting from 0 [OK]

Common Mistakes:

• Thinking count stays 0 without update
• Confusing initial value with updated value
• Expecting error due to misunderstanding setCount

4. Identify the error in this React Native code using useState:

import React, { useState } from 'react';
import { View, Text, Button } from 'react-native';

export default function Example() {
  const [value, setValue] = useState;
  return (
    
      {value}
       setValue('Hello')} />
    
  );
}

medium

A. useState is missing parentheses to call it as a function.

B. The setter function name should be getValue, not setValue.

C. The initial state value must be a number, not undefined.

D. The Button component cannot have an onPress prop.

Solution

1. Step 1: Check useState declaration

   The code uses useState without parentheses, so it does not call the function to get state and setter.

2. Step 2: Understand consequences

   Without calling useState(), value and setValue are undefined, causing errors when used.

3. Final Answer:

   useState is missing parentheses to call it as a function. -> Option A

4. Quick Check:

   useState() must be called with () [OK]

Hint: Always call useState with parentheses: useState() [OK]

Common Mistakes:

• Forgetting parentheses after useState
• Misnaming setter function
• Assuming Button lacks onPress prop

5. You want to toggle a boolean state isVisible between true and false each time a button is pressed. Which is the best way to update the state using useState to ensure the toggle works correctly even if updates happen quickly?

const [isVisible, setIsVisible] = useState(false);

hard

A. setIsVisible(!isVisible);

B. setIsVisible(true);

C. setIsVisible(false);

D. setIsVisible(prev => !prev);

Solution

1. Step 1: Understand state updates with previous value

   When toggling, using the previous state ensures correct flipping even if updates queue quickly.

2. Step 2: Compare update methods

   setIsVisible(prev => !prev); uses a function to get previous state and invert it, which is reliable. setIsVisible(!isVisible); uses current state which may be stale. Options B and D set fixed values, not toggling.

3. Final Answer:

   setIsVisible(prev => !prev); -> Option D

4. Quick Check:

   Use functional update for toggling state [OK]

Hint: Use functional update: setState(prev => !prev) for toggles [OK]

Common Mistakes:

• Using current state directly causing stale updates
• Setting fixed true or false instead of toggling
• Not using functional update for quick repeated changes