Bird
Raised Fist0
React Nativemobile~8 mins

SectionList for grouped data in React Native - Build, Publish & Deploy

Choose your learning style10 modes available
Build & Publish - SectionList for grouped data
Performance Impact

Using SectionList efficiently handles large grouped lists by rendering only visible sections and items. This helps maintain a smooth frame rate near 60fps on most devices. However, complex section headers or heavy item components can increase memory use and reduce scrolling smoothness. Battery usage is moderate but can rise if many re-renders occur.

Optimization Tips

To keep scrolling smooth at 60fps, use keyExtractor for stable keys and getItemLayout if item heights are fixed. Avoid inline functions in render props to prevent unnecessary re-renders. Use React.memo for item and header components. Limit the complexity of section headers and avoid heavy images or animations inside list items.

App Size and Startup Time

SectionList is part of React Native core, so it adds no extra bundle size. Grouping data for SectionList is done in JavaScript and does not affect native binary size. However, large data sets can increase JavaScript memory usage and slightly delay initial render if data processing is heavy. Lazy loading or pagination can reduce startup delays.

iOS vs Android Differences

SectionList uses native components under the hood: UITableView on iOS and RecyclerView on Android. iOS generally has smoother default scrolling and better header stickiness. Android may require extra tuning for sticky headers and can have slight differences in scroll physics. Testing on both platforms is important to ensure consistent behavior.

Store Review Guidelines

Ensure your SectionList content respects accessibility guidelines: use accessible labels and roles for headers and items. Avoid excessive memory use that can cause app crashes. Follow platform UI guidelines for list appearance and interaction. Both Apple App Store and Google Play require apps to be responsive and not freeze during scrolling.

Self-Check Question

Your app takes 5 seconds to load a screen with a SectionList. What is likely wrong?

  • Data grouping or processing is done synchronously on the main thread, blocking UI.
  • Rendering complex headers or items without memoization causes slow rendering.
  • Missing keyExtractor leads to inefficient re-renders.
  • Loading too many items at once without pagination or virtualization.
Key Result
SectionList efficiently renders grouped data with good performance and moderate memory use. Optimizing keys, memoization, and item layout keeps scrolling smooth. It adds no bundle size but requires careful data handling to avoid slow startup. iOS and Android have subtle differences in scrolling behavior. Accessibility and responsiveness are key for store approval.

Practice

(1/5)
1. What is the main purpose of using SectionList in React Native?
easy
A. To display a list of items grouped by sections with headers
B. To create a grid layout of images
C. To handle user input forms
D. To navigate between screens

Solution

  1. Step 1: Understand SectionList usage

    SectionList is designed to show lists grouped by sections, each with a header and items.
  2. Step 2: Compare options with SectionList purpose

    Options B, C, and D describe other UI or functionality unrelated to grouped lists.
  3. Final Answer:

    To display a list of items grouped by sections with headers -> Option A
  4. Quick Check:

    SectionList = grouped list display [OK]
Hint: SectionList groups items with headers, unlike FlatList [OK]
Common Mistakes:
  • Confusing SectionList with FlatList
  • Thinking SectionList is for navigation
  • Assuming SectionList creates grids
2. Which of the following is the correct way to define the sections prop for a SectionList?
easy
A. [{ title: 'Fruits', data: ['Apple', 'Banana'] }, { title: 'Veggies', data: ['Carrot'] }]
B. ['Fruits', 'Apple', 'Banana', 'Veggies', 'Carrot']
C. { title: 'Fruits', items: ['Apple', 'Banana'] }
D. [{ header: 'Fruits', items: ['Apple', 'Banana'] }]

Solution

  1. Step 1: Recall SectionList sections structure

    Each section is an object with a title and a data array of items.
  2. Step 2: Check options for correct keys and structure

    [{ title: 'Fruits', data: ['Apple', 'Banana'] }, { title: 'Veggies', data: ['Carrot'] }] matches the required format. Options B, C, and D use wrong keys or structure.
  3. Final Answer:

    [{ title: 'Fruits', data: ['Apple', 'Banana'] }, { title: 'Veggies', data: ['Carrot'] }] -> Option A
  4. Quick Check:

    sections = array of {title, data} objects [OK]
Hint: Sections need title and data keys exactly [OK]
Common Mistakes:
  • Using wrong keys like 'items' or 'header'
  • Passing a flat array instead of array of objects
  • Confusing data array with section title
3. Given this code snippet, what will be displayed as section headers?
const sections = [
  { title: 'A', data: ['Apple', 'Apricot'] },
  { title: 'B', data: ['Banana'] }
];

<SectionList
  sections={sections}
  renderItem={({ item }) => <Text>{item}</Text>}
  renderSectionHeader={({ section }) => <Text>{section.title}</Text>}
/>
medium
A. No headers will be shown
B. Apple and Banana as headers
C. Only A as header, B is ignored
D. A and B as headers above their items

Solution

  1. Step 1: Understand renderSectionHeader usage

    The renderSectionHeader renders the title of each section as header.
  2. Step 2: Identify section titles in data

    Sections have titles 'A' and 'B', so these will be shown as headers above their items.
  3. Final Answer:

    A and B as headers above their items -> Option D
  4. Quick Check:

    Section titles = headers [OK]
Hint: Section headers come from section.title, not items [OK]
Common Mistakes:
  • Thinking items become headers
  • Assuming only first section shows header
  • Forgetting to use renderSectionHeader
4. What is wrong with this SectionList usage?
const sections = [
  { title: 'Numbers', data: 12345 }
];

<SectionList
  sections={sections}
  renderItem={({ item }) => <Text>{item}</Text>}
  renderSectionHeader={({ section }) => <Text>{section.title}</Text>}
/>
medium
A. The title property must be an array
B. The data property should be an array, not a number
C. renderItem should be renderSectionFooter
D. sections should be a flat array, not array of objects

Solution

  1. Step 1: Check the type of data property

    The data property must be an array of items, but here it is a number (12345).
  2. Step 2: Understand consequences of wrong data type

    This will cause runtime errors because SectionList expects an array to iterate over.
  3. Final Answer:

    The data property should be an array, not a number -> Option B
  4. Quick Check:

    data must be array [OK]
Hint: data must always be an array, never a single value [OK]
Common Mistakes:
  • Passing a single value instead of array to data
  • Confusing title type with data type
  • Using wrong render method names
5. You want to display a SectionList with sections for weekdays and weekend, but only show days that start with 'S'. How should you prepare the sections data?
hard
A. [{ title: 'Weekdays', data: ['Monday', 'Tuesday', 'Wednesday', 'Thursday', 'Friday', 'Saturday', 'Sunday'] }]
B. [{ title: 'Weekdays', data: ['Monday', 'Tuesday', 'Wednesday', 'Thursday', 'Friday'] }, { title: 'Weekend', data: ['Saturday', 'Sunday'] }]
C. [{ title: 'Weekdays', data: ['Monday', 'Tuesday', 'Wednesday', 'Thursday', 'Friday'].filter(day => day.startsWith('S')) }, { title: 'Weekend', data: ['Saturday', 'Sunday'].filter(day => day.startsWith('S')) }]
D. [{ title: 'Days', data: ['Saturday', 'Sunday'] }]

Solution

  1. Step 1: Filter days starting with 'S' in each group

    Use filter(day => day.startsWith('S')) on weekdays and weekend arrays to keep only days starting with 'S'.
  2. Step 2: Assign filtered arrays to correct section titles

    Weekdays filtered will be empty, weekend filtered will have 'Saturday' and 'Sunday'. This matches the requirement.
  3. Final Answer:

    [{ title: 'Weekdays', data: ['Monday', 'Tuesday', 'Wednesday', 'Thursday', 'Friday'].filter(day => day.startsWith('S')) }, { title: 'Weekend', data: ['Saturday', 'Sunday'].filter(day => day.startsWith('S')) }] -> Option C
  4. Quick Check:

    Filter each section's data by startsWith('S') [OK]
Hint: Filter each section's data array before passing to SectionList [OK]
Common Mistakes:
  • Not filtering weekdays, showing all days
  • Combining all days into one section
  • Ignoring filtering and passing raw arrays
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