Bird
Raised Fist0
React Nativemobile~10 mins

FlatList basics (data, renderItem, keyExtractor) in React Native - UI Render Trace

Choose your learning style10 modes available
Component - FlatList basics (data, renderItem, keyExtractor)

This component shows a list of items using React Native's FlatList. It takes data, draws each item with renderItem, and uses keyExtractor to give each item a unique ID for smooth updates.

Widget Tree
FlatList
 ├─ View (container)
 │   ├─ Text (item 1)
 │   ├─ Text (item 2)
 │   ├─ Text (item 3)
 │   └─ ...
The FlatList is the main widget showing a scrollable list. Inside it, each item is rendered as a Text component inside a View container. The list scrolls vertically by default.
Render Trace - 5 Steps
Step 1: FlatList
Step 2: renderItem
Step 3: renderItem
Step 4: renderItem
Step 5: keyExtractor
State Change - Re-render
Trigger:Adding a new fruit item to the data array
Before
data=[{id:'1',name:'Apple'},{id:'2',name:'Banana'},{id:'3',name:'Cherry'}]
→
After
data=[{id:'1',name:'Apple'},{id:'2',name:'Banana'},{id:'3',name:'Cherry'},{id:'4',name:'Date'}]
Re-renders:FlatList re-renders only the new item 'Date' and updates the list display.
UI Quiz - 3 Questions
Test your understanding
What does the keyExtractor function do in FlatList?
AIt decides how to display each item
BIt gives each list item a unique ID for React to track
CIt sorts the list items alphabetically
DIt adds a scroll bar to the list
Key Insight
FlatList efficiently renders long lists by only drawing visible items and using unique keys to track changes. This keeps the app smooth and fast even with many items.

Practice

(1/5)
1. What is the main purpose of the keyExtractor prop in a React Native FlatList?
easy
A. To handle user taps on list items.
B. To define how each item should be displayed on the screen.
C. To specify the data source for the list.
D. To provide a unique key for each list item to help React identify items.

Solution

  1. Step 1: Understand the role of keyExtractor

    The keyExtractor is used to give each item a unique key, which helps React track which items changed, added, or removed.
  2. Step 2: Differentiate from other props

    renderItem defines how to show items, data is the list source, and tap handling is done separately.
  3. Final Answer:

    To provide a unique key for each list item to help React identify items. -> Option D
  4. Quick Check:

    keyExtractor = unique keys [OK]
Hint: Keys uniquely identify items in lists [OK]
Common Mistakes:
  • Confusing keyExtractor with renderItem
  • Using index as key without keyExtractor
  • Thinking keyExtractor handles item display
2. Which of the following is the correct syntax to define a FlatList with data and renderItem props?
easy
A. {item}} />
B. {item}} />
C. {item}} />
D. {data}} />

Solution

  1. Step 1: Check prop names

    The correct props are data for the list and renderItem for rendering each item.
  2. Step 2: Check renderItem function parameter

    renderItem receives an object with item property, so it should be ({item}) => ....
  3. Final Answer:

    <FlatList data={items} renderItem={({item}) => <Text>{item}</Text>} /> -> Option A
  4. Quick Check:

    Correct props and destructuring = C [OK]
Hint: Use data and renderItem with ({item}) parameter [OK]
Common Mistakes:
  • Using wrong prop names like 'items' or 'render'
  • Not destructuring item in renderItem
  • Passing item directly without braces
3. Given this code snippet, what will be displayed on the screen?
const data = [{id: '1', name: 'Apple'}, {id: '2', name: 'Banana'}];

<FlatList
  data={data}
  keyExtractor={item => item.id}
  renderItem={({item}) => <Text>{item.name}</Text>}
/>
medium
A. A blank screen because keyExtractor is missing.
B. A list showing 'Apple' and 'Banana' as text items.
C. An error because renderItem is not a function.
D. A list showing '1' and '2' as text items.

Solution

  1. Step 1: Analyze data and keyExtractor

    Data has two objects with ids and names. keyExtractor returns item.id, which is correct.
  2. Step 2: Analyze renderItem output

    renderItem shows item.name, so it will display 'Apple' and 'Banana'.
  3. Final Answer:

    A list showing 'Apple' and 'Banana' as text items. -> Option B
  4. Quick Check:

    renderItem shows item.name = Apple, Banana [OK]
Hint: renderItem shows item.name, so names appear [OK]
Common Mistakes:
  • Thinking keyExtractor missing causes blank screen
  • Confusing item.id with item.name in renderItem
  • Assuming renderItem is missing or wrong
4. What is wrong with this FlatList usage?
const data = [{id: 'a'}, {id: 'b'}];

<FlatList
  data={data}
  renderItem={({item}) => <Text>{item.id}</Text>}
/>
medium
A. FlatList requires a style prop to render.
B. renderItem should not use destructuring for item.
C. Missing keyExtractor prop, which may cause warnings or errors.
D. data should be an array of strings, not objects.

Solution

  1. Step 1: Check for keyExtractor

    The code does not provide a keyExtractor, so React Native will warn because keys are needed for list items.
  2. Step 2: Validate other props

    renderItem correctly destructures item, data can be objects, and style is optional.
  3. Final Answer:

    Missing keyExtractor prop, which may cause warnings or errors. -> Option C
  4. Quick Check:

    keyExtractor missing = warning [OK]
Hint: Always add keyExtractor for unique keys [OK]
Common Mistakes:
  • Ignoring missing keyExtractor warnings
  • Thinking renderItem destructuring is wrong
  • Believing style prop is mandatory
5. You want to display a list of users with unique IDs, but your data array has duplicate IDs. How should you modify the keyExtractor to avoid key conflicts in FlatList?
const users = [
  {id: '1', name: 'Alice'},
  {id: '1', name: 'Bob'},
  {id: '2', name: 'Charlie'}
];

<FlatList
  data={users}
  keyExtractor={item => item.id}
  renderItem={({item}) => <Text>{item.name}</Text>}
/>
hard
A. Change keyExtractor to combine id and index: (item, index) => item.id + index
B. Remove keyExtractor and use default keys.
C. Use only index as keyExtractor: (item, index) => index.toString()
D. Keep keyExtractor as item.id because duplicates don't matter.

Solution

  1. Step 1: Identify duplicate keys problem

    Using only item.id causes duplicate keys for '1', which React warns against.
  2. Step 2: Fix keyExtractor to ensure uniqueness

    Combining item.id with index creates unique keys like '11', '12', '20'.
  3. Final Answer:

    Change keyExtractor to combine id and index: (item, index) => item.id + index -> Option A
  4. Quick Check:

    Unique keys prevent warnings = Change keyExtractor to combine id and index: (item, index) => item.id + index [OK]
Hint: Combine id and index for unique keys [OK]
Common Mistakes:
  • Ignoring duplicate keys causing warnings
  • Using only index loses stable keys
  • Removing keyExtractor causes errors
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard