Why state and props drive component behavior in React Native - Quick Recap

Recall & Review

beginner

What are props in React Native?

Props are inputs to a React Native component. They are like function arguments and are passed from parent to child components to configure or customize them.

beginner

What is state in React Native?

State is data that a component keeps and manages itself. It can change over time, and when it changes, the component updates its UI to reflect the new state.

intermediate

How do props differ from state?

Props are passed from parent to child and cannot be changed by the child. State is managed inside the component and can be changed by it to update the UI.

intermediate

Why do changes in state or props cause a component to re-render?

React Native watches for changes in state or props. When they change, React updates the component's UI to show the latest data, keeping the app in sync with its data.

beginner

Give a simple example of how state drives behavior in a React Native component.

A button that toggles text between 'ON' and 'OFF' uses state to remember if it is on or off. When pressed, state changes and the text updates automatically.

What is the main role of props in React Native?

A To pass data from parent to child components

B To store data inside a component

C To change the component's internal state

D To handle user input events

Props are used to pass data from a parent component to its child components.

Which of the following can a React Native component change directly?

A Props

B State

C Both props and state

D Neither props nor state

A component can change its own state but cannot change its props directly.

What happens when state changes in a React Native component?

A Props are updated

B The component unmounts

C Nothing happens automatically

D The component re-renders to update the UI

Changing state causes React Native to re-render the component to reflect the new state.

Which statement is true about props?

A Props are immutable and set by the parent

B Props are mutable inside the component

C Props are used to store local data

D Props trigger state changes

Props are set by the parent and cannot be changed by the child component.

Why do React Native components use state and props?

A To handle network requests

B To style the component

C To manage and display dynamic data

D To create animations

State and props help components manage and show data that can change over time.

Explain in your own words why state and props are important for React Native components.

Think about how components get data and update what the user sees.

Describe a simple example where changing state updates the UI in a React Native app.

Consider a button that changes text when pressed.

Practice

1. What is the main role of state in a React Native component?

easy

A. To define the component's layout structure

B. To pass data from a parent component to a child component

C. To style the component with CSS-like rules

D. To hold data that can change over time inside the component

Solution

1. Step 1: Understand what state represents

   State is used to store data that can change during the life of a component, like user input or toggles.

2. Step 2: Differentiate state from props

   Props are for passing data from parent to child, not for internal changes.

3. Final Answer:

   To hold data that can change over time inside the component -> Option D

4. Quick Check:

   State = internal changing data [OK]

Hint: State holds changing data inside component [OK]

Common Mistakes:

• Confusing state with props
• Thinking state is for styling
• Believing state is static

2. Which of the following is the correct way to define a state variable using React hooks in a functional component?

easy

A. var count = useState(0);

B. let count = useState(0);

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

D. state = { count: 0 };

Solution

1. Step 1: Recall React hook syntax for state

   useState returns an array with the current value and a function to update it, usually destructured.

2. Step 2: Check each option

   const [count, setCount] = useState(0); correctly uses array destructuring with useState. Others misuse syntax or do not destructure.

3. Final Answer:

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

4. Quick Check:

   useState with destructuring = correct [OK]

Hint: useState returns [value, setter] array [OK]

Common Mistakes:

• Not destructuring useState result
• Using var or let instead of const
• Assigning useState directly to a variable

3. Consider this React Native component code:

function Greeting(props) {
  return Hello, {props.name}!;
}

function App() {
  return ;
}

What will be displayed on the screen?

medium

A. Hello, Alice!

B. Hello, name!

C. Hello, !

D. Error: props not defined

Solution

1. Step 1: Understand how props work in this example

   The Greeting component receives name as a prop from App with value "Alice".

2. Step 2: Check the rendered output

   The component returns Hello, {props.name}! which becomes "Hello, Alice!" on screen.

3. Final Answer:

   Hello, Alice! -> Option A

4. Quick Check:

   Props pass data = Hello, Alice! [OK]

Hint: Props pass data from parent to child [OK]

Common Mistakes:

• Assuming props is undefined
• Ignoring the passed name value
• Confusing props with state

4. What is wrong with this React Native code snippet?

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

medium

A. You cannot assign directly to the state variable; must use setCount

B. Button component does not have a title prop

C. useState is not imported

D. Text component cannot display numbers

Solution

1. Step 1: Identify how state updates should happen

   State variables are read-only; to change state, use the setter function like setCount.

2. Step 2: Check the onPress handler

   The code tries to assign directly to count, which is invalid and won't update the UI.

3. Final Answer:

   You cannot assign directly to the state variable; must use setCount -> Option A

4. Quick Check:

   State updates require setter function [OK]

Hint: Always use setter to update state, never assign directly [OK]

Common Mistakes:

• Trying to change state variable directly
• Forgetting to import useState
• Misusing Button props

5. You want a component to show a message that changes when a button is pressed. Which approach correctly uses state and props to achieve this?

function Message({ initial }) {
  const [text, setText] = useState(initial);
  return (
    
      {text}
       setText('Updated!')} />
    
  );
}

function App() {
  return ;
}

hard

A. This fails because Button cannot change state

B. This works because state holds the message and props provide the initial value

C. This fails because props cannot be used inside useState

D. This fails because Text cannot display state variables

Solution

1. Step 1: Analyze how props and state are used

   The component receives an initial message via props and stores it in state for changes.

2. Step 2: Check the button's onPress behavior

   Pressing the button calls setText to update the state, which updates the displayed message.

3. Final Answer:

   This works because state holds the message and props provide the initial value -> Option B

4. Quick Check:

   Props initialize state; state changes update UI [OK]

Hint: Use props for initial data, state for changes [OK]

Common Mistakes:

• Thinking props can change after initial render
• Trying to update props directly
• Assuming Button can't trigger state changes