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.
SectionList for grouped data in React Native - Build, Publish & Deploy
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.
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.
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.
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.
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
keyExtractorleads to inefficient re-renders. - Loading too many items at once without pagination or virtualization.
Practice
SectionList in React Native?Solution
Step 1: Understand SectionList usage
SectionListis designed to show lists grouped by sections, each with a header and items.Step 2: Compare options with SectionList purpose
Options B, C, and D describe other UI or functionality unrelated to grouped lists.Final Answer:
To display a list of items grouped by sections with headers -> Option AQuick Check:
SectionList = grouped list display [OK]
- Confusing SectionList with FlatList
- Thinking SectionList is for navigation
- Assuming SectionList creates grids
sections prop for a SectionList?Solution
Step 1: Recall SectionList sections structure
Each section is an object with atitleand adataarray of items.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.Final Answer:
[{ title: 'Fruits', data: ['Apple', 'Banana'] }, { title: 'Veggies', data: ['Carrot'] }] -> Option AQuick Check:
sections = array of {title, data} objects [OK]
- Using wrong keys like 'items' or 'header'
- Passing a flat array instead of array of objects
- Confusing data array with section title
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>}
/>Solution
Step 1: Understand renderSectionHeader usage
TherenderSectionHeaderrenders thetitleof each section as header.Step 2: Identify section titles in data
Sections have titles 'A' and 'B', so these will be shown as headers above their items.Final Answer:
A and B as headers above their items -> Option DQuick Check:
Section titles = headers [OK]
- Thinking items become headers
- Assuming only first section shows header
- Forgetting to use renderSectionHeader
SectionList usage?
const sections = [
{ title: 'Numbers', data: 12345 }
];
<SectionList
sections={sections}
renderItem={({ item }) => <Text>{item}</Text>}
renderSectionHeader={({ section }) => <Text>{section.title}</Text>}
/>Solution
Step 1: Check the type of data property
Thedataproperty must be an array of items, but here it is a number (12345).Step 2: Understand consequences of wrong data type
This will cause runtime errors becauseSectionListexpects an array to iterate over.Final Answer:
The data property should be an array, not a number -> Option BQuick Check:
data must be array [OK]
- Passing a single value instead of array to data
- Confusing title type with data type
- Using wrong render method names
SectionList with sections for weekdays and weekend, but only show days that start with 'S'. How should you prepare the sections data?Solution
Step 1: Filter days starting with 'S' in each group
Usefilter(day => day.startsWith('S'))on weekdays and weekend arrays to keep only days starting with 'S'.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.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 CQuick Check:
Filter each section's data by startsWith('S') [OK]
- Not filtering weekdays, showing all days
- Combining all days into one section
- Ignoring filtering and passing raw arrays
Ready to prove it?
Pass the test and this pattern moves unknown
