Stack Navigator in React Native - UI Render Trace

Component - Stack Navigator

A Stack Navigator manages a stack of screens in a mobile app. It lets users move forward to new screens and go back to previous ones, like pages in a book.

Widget Tree

StackNavigator
├─ Screen: Home
└─ Screen: Details

The StackNavigator holds multiple Screen components. Initially, the Home screen is shown. When navigating, the Details screen is pushed on top, covering Home.

Render Trace - 5 Steps

Step 1: StackNavigator

Step 2: Screen: Home

Step 3: User taps 'Go to Details' button

Step 4: Screen: Details

Step 5: User taps back button

State Change - Re-render

Trigger:User taps 'Go to Details' button on Home screen

Before

Stack contains only Home screen

→

After

Stack contains Home screen at bottom, Details screen on top

Re-renders:StackNavigator and Details screen re-render to show new screen

UI Quiz - 3 Questions

What happens when you navigate from Home to Details in a Stack Navigator?

A Both screens show side by side

B Home screen is replaced by Details screen

C Details screen is pushed on top of Home screen

D Home screen is removed from the stack

Key Insight

Stack Navigator mimics a real stack of pages, letting users move forward and back smoothly. Understanding this helps design intuitive app navigation flows.

Practice

1. What is the main purpose of a Stack Navigator in React Native?

easy

A. To fetch data from an API

B. To style components with CSS

C. To manage screen navigation like a stack of pages

D. To handle user input events

Solution

1. Step 1: Understand navigation concepts

   Stack Navigator organizes screens so you can move forward and back like a stack of pages.

2. Step 2: Identify the correct purpose

   It is not for styling, fetching data, or handling input but for navigation.

3. Final Answer:

   To manage screen navigation like a stack of pages -> Option C

4. Quick Check:

   Stack Navigator = navigation management [OK]

Hint: Stack Navigator stacks screens for forward/back navigation [OK]

Common Mistakes:

• Confusing navigation with styling
• Thinking it handles data fetching
• Assuming it manages user input

2. Which of the following is the correct way to wrap your app with a stack navigator?

easy

A.

B.

C.

D.

Solution

1. Step 1: Recognize correct nesting

   The NavigationContainer must wrap the entire navigator, which contains Stack.Navigator and its screens.

2. Step 2: Check each option's structure

   Only <NavigationContainer><Stack.Navigator><Stack.Screen name="Home" component={HomeScreen} /></Stack.Navigator></NavigationContainer> correctly wraps Stack.Navigator inside NavigationContainer and includes Stack.Screen.

3. Final Answer:

   <NavigationContainer><Stack.Navigator><Stack.Screen name="Home" component={HomeScreen} /></Stack.Navigator></NavigationContainer> -> Option A

4. Quick Check:

   NavigationContainer wraps Stack.Navigator [OK]

Hint: NavigationContainer wraps Stack.Navigator, which holds screens [OK]

Common Mistakes:

• Placing Stack.Screen outside Stack.Navigator
• Wrapping Stack.Screen directly in NavigationContainer
• Incorrect nesting order of components

3. Given this code snippet, what screen will be shown first when the app runs?

const Stack = createStackNavigator();

function App() {
  return (
    
      
        
        
      
    
  );
}

medium

A. Profile screen

B. Error: No initial screen defined

C. Home screen

D. Settings screen

Solution

1. Step 1: Identify default initial screen

   By default, the first Stack.Screen listed is the initial screen shown.

2. Step 2: Check the order of screens

   The first screen is named "Profile", so the app shows ProfileScreen first.

3. Final Answer:

   Profile screen -> Option A

4. Quick Check:

   First Stack.Screen = initial screen [OK]

Hint: First Stack.Screen listed is the initial screen [OK]

Common Mistakes:

• Assuming Settings is first because of alphabetical order
• Thinking Home screen appears without definition
• Believing an error occurs without initial screen prop

4. What is wrong with this code snippet?

const Stack = createStackNavigator();

function App() {
  return (
    
      
    
  );
}

medium

A. Stack.Screen name must be lowercase

B. Missing NavigationContainer wrapping the navigator

C. HomeScreen component must be imported from react-native

D. Stack.Navigator cannot have only one screen

Solution

1. Step 1: Check for NavigationContainer

   React Navigation requires NavigationContainer to wrap the navigator for proper navigation context.

2. Step 2: Verify other parts

   Screen names can be uppercase, components can be custom, and one screen is allowed.

3. Final Answer:

   Missing NavigationContainer wrapping the navigator -> Option B

4. Quick Check:

   NavigationContainer is required [OK]

Hint: Always wrap Stack.Navigator inside NavigationContainer [OK]

Common Mistakes:

• Omitting NavigationContainer causes navigation failure
• Thinking screen names must be lowercase
• Assuming only built-in components can be screens

5. You want to navigate from the Home screen to the Details screen using a Stack Navigator. Which code snippet correctly performs this navigation inside a button press handler?

function HomeScreen({ navigation }) {
  return (
     ???}
    />
  );
}

hard

A. navigation.push(Details)

B. navigation.popToTop('Details')

C. navigation.goBack('Details')

D. navigation.navigate('Details')

Solution

1. Step 1: Understand navigation methods

   navigation.navigate('ScreenName') moves to a screen, pushing it on the stack if needed.

2. Step 2: Compare options

   push(Details) has a syntax error (missing quotes around screen name); goBack and popToTop are for going back, not forward.

3. Final Answer:

   navigation.navigate('Details') -> Option D

4. Quick Check:

   Use navigate() to go forward to a screen [OK]

Hint: Use navigation.navigate('ScreenName') to move forward [OK]

Common Mistakes:

• Using goBack to go forward
• Using popToTop incorrectly
• Confusing push and navigate methods