Callback props in React Native - UI Render Trace

Component - Callback props

This React Native component shows how a parent passes a function (callback) to a child. The child calls this function when a button is pressed. This lets the parent know about the child's action and update its own state.

Widget Tree

App
├─ View (container)
│  ├─ Text (display message)
│  └─ ChildButton (custom component)
│     └─ Button (pressable)

The root App component contains a View that holds a Text and a ChildButton component. ChildButton renders a Button. When the Button is pressed, ChildButton calls the callback function passed from App.

Render Trace - 3 Steps

Step 1: App

Step 2: ChildButton

Step 3: Button

State Change - Re-render

Trigger:User taps the 'Click me' button

Before

message = 'Press the button'

→

After

message = 'Button was clicked!'

Re-renders:App component and its children re-render to update the displayed message

UI Quiz - 3 Questions

What happens when the button inside ChildButton is pressed?

A The callback function passed from App is called

B ChildButton changes its own state

C The button label changes automatically

D Nothing happens

Key Insight

Using callback props in React Native lets parent components control state changes triggered by child components. This pattern keeps state in one place and allows clear communication from child to parent.

Practice

1. What is the main purpose of using callback props in React Native components?

easy

A. To manage component state internally

B. To style components dynamically

C. To allow child components to communicate events back to parent components

D. To fetch data from an API

Solution

1. Step 1: Understand callback props role

   Callback props are functions passed from parent to child to notify the parent about events.

2. Step 2: Identify communication direction

   They let children send information or events back to parents, enabling communication.

3. Final Answer:

   To allow child components to communicate events back to parent components -> Option C

4. Quick Check:

   Callback props = child-to-parent communication [OK]

Hint: Callback props let children tell parents about events [OK]

Common Mistakes:

• Thinking callback props manage styling
• Confusing callback props with state management
• Assuming callback props fetch data

2. Which of the following is the correct way to pass a callback prop named onPress from a parent to a child component in React Native?

easy

A.

B.

C. handlePress />

D.

Solution

1. Step 1: Recall JSX prop syntax

   Props are passed as attributes with values inside curly braces for functions.

2. Step 2: Match correct syntax

   uses onPress={handlePress}, which is valid JSX syntax.

3. Final Answer:

   <ChildComponent onPress={handlePress} /> -> Option A

4. Quick Check:

   JSX props use = and curly braces for functions [OK]

Hint: Use = and curly braces to pass functions as props [OK]

Common Mistakes:

• Using colon : instead of =
• Using arrow => inside prop
• Adding parentheses () in prop name

3. Given the code below, what will be logged when the button is pressed?

function Parent() {
  const handleClick = () => console.log('Clicked!');
  return <Child onPress={handleClick} />;
}

function Child({ onPress }) {
  return <Button title="Press me" onPress={onPress} />;
}

medium

A. Nothing happens

B. Clicked!

C. Error: onPress is not a function

D. Button title is logged

Solution

1. Step 1: Trace callback prop usage

   The Parent passes handleClick as onPress prop to Child.

2. Step 2: Check Child button onPress

   The Child uses onPress prop as the button's onPress handler, so pressing calls handleClick.

3. Final Answer:

   Clicked! -> Option B

4. Quick Check:

   Button press triggers parent's callback [OK]

Hint: Child calls parent's function on event [OK]

Common Mistakes:

• Assuming onPress is undefined
• Thinking button title logs
• Ignoring callback function call

4. Identify the error in this React Native code snippet:

function Parent() {
  const handlePress = () => alert('Pressed');
  return <Child onPress={handlePress()} />;
}

function Child({ onPress }) {
  return <Button title="Click" onPress={onPress} />;
}

medium

A. alert cannot be used in React Native

B. Child component is missing props destructuring

C. Button component does not support onPress

D. handlePress is called immediately instead of passed as a function

Solution

1. Step 1: Analyze prop passing

   In onPress={handlePress()}, the function is called immediately, passing its result (undefined) instead of the function.

2. Step 2: Understand correct usage

   We should pass the function itself without calling it: onPress={handlePress}.

3. Final Answer:

   handlePress is called immediately instead of passed as a function -> Option D

4. Quick Check:

   Pass function reference, not call it [OK]

Hint: Pass function, don't call it when passing as prop [OK]

Common Mistakes:

• Calling function instead of passing reference
• Thinking alert is invalid in React Native
• Ignoring destructuring in Child

5. You want a child component to notify the parent when a text input changes, but only if the input length is more than 3 characters. How should you implement the callback prop pattern to achieve this?

hard

A. Pass a callback prop from parent; child calls it only when input length > 3

B. Child manages input state and updates parent state directly

C. Parent listens to child's internal state without callback

D. Use a global variable to share input value between components

Solution

1. Step 1: Understand callback prop usage for conditional events

   The parent passes a function as a prop to the child to receive input changes.

2. Step 2: Implement conditional call in child

   The child calls the callback only if the input length is more than 3, controlling when to notify the parent.

3. Final Answer:

   Pass a callback prop from parent; child calls it only when input length > 3 -> Option A

4. Quick Check:

   Child controls event call; parent receives updates [OK]

Hint: Child calls parent callback only when condition meets [OK]

Common Mistakes:

• Letting child update parent state directly
• Ignoring conditional logic in child
• Using global variables for communication