Pull-to-refresh in React Native - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is pull-to-refresh in mobile apps?

Pull-to-refresh is a gesture where you drag the screen down to refresh the content, like updating a list of messages or news.

beginner

Which React Native component helps implement pull-to-refresh?

The RefreshControl component is used with scrollable views like ScrollView or FlatList to add pull-to-refresh functionality.

intermediate

How do you know when the user is pulling to refresh in React Native?

You track a boolean state like refreshing that becomes true when the user pulls down and triggers the refresh action.

beginner

Why should you set refreshing back to false after refreshing?

Setting refreshing to false stops the loading spinner and lets the user know the refresh is done.

intermediate

What is a simple way to add pull-to-refresh to a list in React Native?

Use FlatList with the refreshControl prop set to a RefreshControl component that manages the refreshing state and onRefresh callback.

Which component do you use to add pull-to-refresh in React Native?

A RefreshControl

B TouchableOpacity

C TextInput

D Button

The RefreshControl component is designed for pull-to-refresh functionality.

What prop do you pass to RefreshControl to know when to stop refreshing?

A isRefreshing

B loading

C refreshState

D refreshing

The refreshing prop is a boolean that controls the spinner visibility.

Where do you usually add RefreshControl in React Native?

A Inside Button component

B Inside ScrollView or FlatList's refreshControl prop

C Inside View component without scroll

D Inside Text component

RefreshControl works with scrollable components like ScrollView or FlatList.

What happens if you forget to set refreshing to false after refresh?

A The spinner keeps spinning and user thinks loading continues

B The app crashes

C Nothing happens, refresh ends automatically

D The list clears

The spinner stays visible, confusing the user.

Pull-to-refresh is best described as:

A Tapping a button to refresh

B Swiping left to delete

C Dragging down to update content

D Pinching to zoom

Pull-to-refresh means dragging down to refresh content.

Explain how to implement pull-to-refresh in a React Native FlatList.

Think about the components and state you need to show and stop the spinner.

Why is it important to manage the refreshing state properly in pull-to-refresh?

Consider what happens if the spinner never stops.

Practice

1. What is the main purpose of using RefreshControl in a React Native app?

easy

A. To enable pull-to-refresh functionality in scrollable lists

B. To add animations to buttons

C. To handle navigation between screens

D. To style text components

Solution

1. Step 1: Understand the role of RefreshControl

   RefreshControl is a component used inside scrollable views to provide pull-to-refresh behavior.

2. Step 2: Identify its main purpose

   Its main purpose is to let users pull down on a list to trigger a refresh action, usually to update content.

3. Final Answer:

   To enable pull-to-refresh functionality in scrollable lists -> Option A

4. Quick Check:

   Pull-to-refresh = RefreshControl usage [OK]

Hint: RefreshControl is for pull-to-refresh in lists [OK]

Common Mistakes:

• Confusing RefreshControl with navigation or styling
• Thinking it adds animations to buttons
• Using it outside scrollable components

2. Which of the following is the correct way to use RefreshControl inside a ScrollView?

easy

A.

B.

C. } />

D. } />

Solution

1. Step 1: Recall correct RefreshControl usage

   The refreshControl prop expects a RefreshControl component with props refreshing and onRefresh.

2. Step 2: Match correct syntax

   <ScrollView refreshControl={<RefreshControl refreshing={refreshing} onRefresh={onRefresh} />} /> correctly passes refreshing and onRefresh inside <RefreshControl /> as a JSX element.

3. Final Answer:

   <ScrollView refreshControl={<RefreshControl refreshing={refreshing} onRefresh={onRefresh} />} /> -> Option D

4. Quick Check:

   refreshControl prop = RefreshControl component with correct props [OK]

Hint: Use refreshControl prop with RefreshControl JSX [OK]

Common Mistakes:

• Passing props directly to ScrollView instead of RefreshControl
• Calling RefreshControl as a function instead of JSX
• Using wrong prop names like refresh or refreshHandler

3. Given this code snippet, what will happen when the user pulls down the list?

const [refreshing, setRefreshing] = React.useState(false);

const onRefresh = React.useCallback(() => {
  setRefreshing(true);
  setTimeout(() => setRefreshing(false), 2000);
}, []);

return (
  <ScrollView refreshControl={
    <RefreshControl refreshing={refreshing} onRefresh={onRefresh} />
  }>
    <Text>Pull down to refresh</Text>
  </ScrollView>
);

medium

A. The spinner never shows because refreshing is false

B. The spinner shows for 2 seconds, then hides automatically

C. The spinner shows indefinitely and never hides

D. The app crashes due to missing dependencies

Solution

1. Step 1: Understand the refreshing state changes

   When the user pulls down, onRefresh sets refreshing to true, showing the spinner.

2. Step 2: Analyze the timeout effect

   After 2 seconds, setRefreshing(false) hides the spinner automatically.

3. Final Answer:

   The spinner shows for 2 seconds, then hides automatically -> Option B

4. Quick Check:

   refreshing true then false after timeout = spinner shows then hides [OK]

Hint: Refreshing true shows spinner; false hides it [OK]

Common Mistakes:

• Assuming spinner never hides without manual reset
• Thinking refreshing starts as true initially
• Confusing useCallback dependencies causing crashes

4. Identify the error in this pull-to-refresh implementation:

const [refreshing, setRefreshing] = React.useState(false);

function onRefresh() {
  setRefreshing(true);
  fetchData();
  setRefreshing(false);
}

return (
  <FlatList
    data={data}
    refreshControl={<RefreshControl refreshing={refreshing} onRefresh={onRefresh} />}
    renderItem={({item}) => <Text>{item}</Text>}
  />
);

medium

A. onRefresh should be async but is not

B. refreshControl prop should be refreshControl (lowercase c)

C. setRefreshing(false) is called immediately, hiding spinner too soon

D. FlatList does not support RefreshControl

Solution

1. Step 1: Check refreshing state timing

   The function calls setRefreshing(false) immediately after fetchData(), without waiting for data to load.

2. Step 2: Understand spinner behavior

   This causes the spinner to hide right away, not showing the loading state properly.

3. Final Answer:

   setRefreshing(false) is called immediately, hiding spinner too soon -> Option C

4. Quick Check:

   Refreshing state must stay true until data loads [OK]

Hint: Keep refreshing true until data fetch completes [OK]

Common Mistakes:

• Calling setRefreshing(false) too early
• Misnaming refreshControl prop
• Assuming FlatList can't use RefreshControl

5. You want to add pull-to-refresh to a SectionList that fetches new data asynchronously. Which approach correctly ensures the spinner shows during fetch and hides after completion?

const [refreshing, setRefreshing] = React.useState(false);

const onRefresh = async () => {
  // What goes here?
};

hard

A. setRefreshing(true); await fetchData(); setRefreshing(false);

B. await fetchData(); setRefreshing(true); setRefreshing(false);

C. setRefreshing(false); await fetchData(); setRefreshing(true);

D. setRefreshing(true); fetchData(); setRefreshing(false);

Solution

1. Step 1: Set refreshing true before fetching

   Call setRefreshing(true) to show spinner before starting data fetch.

2. Step 2: Await fetchData and then set refreshing false

   Use await fetchData() to wait for data, then call setRefreshing(false) to hide spinner after completion.

3. Final Answer:

   setRefreshing(true); await fetchData(); setRefreshing(false); -> Option A

4. Quick Check:

   Show spinner before await, hide after await [OK]

Hint: Set refreshing true before await, false after await [OK]

Common Mistakes:

• Setting refreshing false before fetch completes
• Not awaiting fetchData causing spinner to hide early
• Switching order of setRefreshing calls