FlatList optimization techniques in React Native - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set a unique key for each item in FlatList.

React Native

const MyList = () => {
  return (
    <FlatList
      data={data}
      keyExtractor={item => item.[1]
      renderItem={({item}) => <Text>{item.name}</Text>}
    />
  );
};

Drag options to blanks, or click blank then click option'

Aid

Bindex

Ckey

Dvalue

Attempts:

3 left

💡 Hint

Common Mistakes

Using index as key can cause rendering issues when list changes.

Using a non-unique property causes duplicate keys.

The keyExtractor needs a unique id for each item to optimize rendering.

2fill in blank

medium

Complete the code to avoid re-rendering items unnecessarily by using memoization.

React Native

const RenderItem = React.memo(({item}) => {
  return <Text>{item.name}</Text>;
});

const MyList = () => {
  return (
    <FlatList
      data={data}
      renderItem={({item}) => <[1] item={item} />}
      keyExtractor={item => item.id}
    />
  );
};

Drag options to blanks, or click blank then click option'

AItem

BView

CRenderItem

DText

Attempts:

3 left

💡 Hint

Common Mistakes

Using plain Text component causes all items to re-render.

Using a component not memoized loses optimization benefits.

Using React.memo wrapped component prevents unnecessary re-renders of list items.

3fill in blank

hard

Fix the error in FlatList by completing the missing prop to improve performance with large lists.

React Native

<FlatList
  data={data}
  renderItem={renderItem}
  keyExtractor={item => item.id}
  [1]
/>

Drag options to blanks, or click blank then click option'

AonEndReachedThreshold={0.5}

Brefreshing={false}

Chorizontal={true}

DinitialNumToRender={10}

Attempts:

3 left

💡 Hint

Common Mistakes

Using unrelated props does not fix initial rendering performance.

Not setting this prop can cause slow startup on big lists.

initialNumToRender controls how many items render initially, improving performance on large lists.

4fill in blank

hard

Fill both blanks to optimize FlatList by avoiding extra re-renders and improving scroll performance.

React Native

<FlatList
  data={data}
  renderItem={renderItem}
  keyExtractor={item => item.id}
  [1]={true}
  [2]={50}
/>

Drag options to blanks, or click blank then click option'

AremoveClippedSubviews

Brefreshing

CmaxToRenderPerBatch

DscrollEnabled

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing refreshing or scrollEnabled with performance props.

Not using these props can cause laggy scrolling.

removeClippedSubviews removes offscreen items to save memory, and maxToRenderPerBatch limits how many items render per batch for smooth scrolling.

5fill in blank

hard

Fill all three blanks to implement getItemLayout for fixed-height items to speed up FlatList scrolling.

React Native

<FlatList
  data={data}
  renderItem={renderItem}
  keyExtractor={item => item.id}
  getItemLayout={(data, index) => ({
    length: [1],
    offset: [2] * index,
    index: [3]
  })}
/>

Drag options to blanks, or click blank then click option'

A50

Blength

Cindex

D100

Attempts:

3 left

💡 Hint

Common Mistakes

Using variable names instead of values for length and offset.

Not providing getItemLayout causes slower scroll performance.

getItemLayout helps FlatList calculate item positions quickly. Here, each item has fixed height 50, offset is 50 times index, and index is passed through.

Practice

1. What is the main purpose of using keyExtractor in a React Native FlatList?

easy

A. To define the layout height of each item

B. To provide a unique key for each list item to improve rendering performance

C. To set the initial number of items to render

D. To enable pull-to-refresh functionality

Solution

1. Step 1: Understand the role of keys in lists

   Keys help React Native identify which items changed, added, or removed, improving rendering speed.

2. Step 2: Identify what keyExtractor does

   keyExtractor returns a unique key for each item, which is essential for efficient list updates.

3. Final Answer:

   To provide a unique key for each list item to improve rendering performance -> Option B

4. Quick Check:

   Unique keys = keyExtractor [OK]

Hint: Keys uniquely identify items for smooth list updates [OK]

Common Mistakes:

• Confusing keyExtractor with initialNumToRender
• Using index as key causing performance issues
• Thinking keyExtractor sets item layout

2. Which of the following is the correct way to set initialNumToRender in a FlatList?

easy

A. <FlatList initialNumToRender='10' />

B. <FlatList initialNumToRender={"10"} />

C. <FlatList initialNumToRender={10} />

D. <FlatList initialNumToRender>10</FlatList>

Solution

1. Step 1: Understand prop types in React Native

   Numeric props must be passed as numbers, not strings.

2. Step 2: Check each option's syntax

   <FlatList initialNumToRender={10} /> passes a number correctly with curly braces. Options A and C pass strings incorrectly. <FlatList initialNumToRender>10</FlatList> is invalid JSX syntax.

3. Final Answer:

   <FlatList initialNumToRender={10} /> -> Option C

4. Quick Check:

   Numeric props use curly braces [OK]

Hint: Use curly braces for numbers in JSX props [OK]

Common Mistakes:

• Passing numbers as strings in props
• Using invalid JSX syntax for props
• Confusing prop names with event handlers

3. Given this FlatList snippet, what will be the effect of adding getItemLayout?

const getItemLayout = (data, index) => ({length: 50, offset: 50 * index, index});

<FlatList
  data={data}
  renderItem={renderItem}
  keyExtractor={item => item.id}
  getItemLayout={getItemLayout}
/>

medium

A. Improves scroll performance by letting FlatList skip measurement of item sizes

B. Causes a runtime error because getItemLayout is missing required props

C. Makes FlatList render all items at once

D. Disables scrolling in the list

Solution

1. Step 1: Understand getItemLayout purpose

   It tells FlatList the size and position of each item upfront, avoiding costly layout calculations during scroll.

2. Step 2: Analyze the provided getItemLayout function

   The function returns fixed length and offset based on index, which is valid and improves performance.

3. Final Answer:

   Improves scroll performance by letting FlatList skip measurement of item sizes -> Option A

4. Quick Check:

   getItemLayout = faster scroll [OK]

Hint: Fixed item sizes speed up scrolling [OK]

Common Mistakes:

• Assuming getItemLayout causes errors without checking signature
• Thinking it renders all items immediately
• Believing it disables scrolling

4. You notice your FlatList is lagging when scrolling. Which of these fixes addresses a common mistake causing this?

medium

A. Implementing getItemLayout with fixed item sizes

B. Setting initialNumToRender to a very high number

C. Removing keyExtractor and using array index as key

D. Using inline anonymous functions in renderItem

Solution

1. Step 1: Identify common causes of lag in FlatList

   Using unstable keys or rendering too many items initially can cause lag.

2. Step 2: Evaluate each option's effect

   Removing keyExtractor and using array index as key worsens performance by using unstable keys. Setting initialNumToRender to a very high number renders too many items at once. Using inline anonymous functions in renderItem causes re-renders due to new function references. Implementing getItemLayout with fixed item sizes improves performance by optimizing layout calculations.

3. Final Answer:

   Implementing getItemLayout with fixed item sizes -> Option A

4. Quick Check:

   Fixed layouts = less lag [OK]

Hint: Avoid inline functions and use getItemLayout [OK]

Common Mistakes:

• Using array index as key causing re-renders
• Setting initialNumToRender too high
• Ignoring getItemLayout optimization

5. You have a large list with items of varying heights. Which combination of FlatList optimizations is best to improve performance without layout errors?

hard

A. Use getItemLayout with fixed height and no keyExtractor

B. Use keyExtractor with index as key and getItemLayout assuming fixed height

C. Set initialNumToRender very high and skip keyExtractor

D. Use keyExtractor with unique IDs and initialNumToRender set to a small number, but avoid getItemLayout

Solution

1. Step 1: Understand challenges with varying item heights

   Fixed height assumptions in getItemLayout cause layout errors if items vary in size.

2. Step 2: Evaluate options for best practice

   Use keyExtractor with unique IDs and initialNumToRender set to a small number, but avoid getItemLayout. This uses unique keys and limits initial render count, avoiding getItemLayout to prevent errors. Use keyExtractor with index as key and getItemLayout assuming fixed height uses index keys and fixed height, causing bugs. Set initialNumToRender very high and skip keyExtractor renders too many items and lacks keys, hurting performance. Use getItemLayout with fixed height and no keyExtractor lacks keys and assumes fixed height, causing errors.

3. Final Answer:

   Use keyExtractor with unique IDs and initialNumToRender set to a small number, but avoid getItemLayout -> Option D

4. Quick Check:

   Unique keys + small initial render + no fixed layout [OK]

Hint: Avoid getItemLayout if item heights vary [OK]

Common Mistakes:

• Using index as key causing re-renders
• Assuming fixed height for variable items
• Rendering too many items initially