Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.

Virtualization massively improves memory consumption and performance of large lists by maintaining a finite render window of active items and replacing all items outside of the render window with appropriately sized blank space. The window adapts to scrolling behavior, and items are rendered incrementally with low-pri (after any running interactions) if they are far from the visible area, or with hi-pri otherwise to minimize the potential of seeing blank space.

Example

import React from 'react'; import { SafeAreaView, View, VirtualizedList, StyleSheet, Text } from 'react-native'; import Constants from 'expo-constants'; const DATA = []; const getItem = (data, index) => { return { id: Math.random().toString(12).substring(0), title: `Item ${index+1}` } } const getItemCount = (data) => { return 50; } const Item = ({ title })=> { return ( <View style={styles.item}> <Text style={styles.title}>{title}</Text> </View> ); } const VirtualizedListExample = () => { return ( <SafeAreaView style={styles.container}> <VirtualizedList data={DATA} initialNumToRender={4} renderItem={({ item }) => <Item title={item.title} />} keyExtractor={item => item.key} getItemCount={getItemCount} getItem={getItem} /> </SafeAreaView> ); } const styles = StyleSheet.create({ container: { flex: 1, marginTop: Constants.statusBarHeight, }, item: { backgroundColor: '#f9c2ff', height: 150, justifyContent: 'center', marginVertical: 8, marginHorizontal: 16, padding: 20, }, title: { fontSize: 32, }, }); export default VirtualizedListExample;

---

Some caveats:

• Internal state is not preserved when content scrolls out of the render window. Make sure all your data is captured in the item data or external stores like Flux, Redux, or Relay.
• This is a PureComponent which means that it will not re-render if props are shallow-equal. Make sure that everything your renderItem function depends on is passed as a prop (e.g. extraData) that is not === after updates, otherwise your UI may not update on changes. This includes the data prop and parent component state.
• In order to constrain memory and enable smooth scrolling, content is rendered asynchronously offscreen. This means it's possible to scroll faster than the fill rate and momentarily see blank content. This is a tradeoff that can be adjusted to suit the needs of each application, and we are working on improving it behind the scenes.
• By default, the list looks for a key prop on each item and uses that for the React key. Alternatively, you can provide a custom keyExtractor prop.

---

Reference

Props

Inherits ScrollView Props.

renderItem

(info: any) => ?React.Element<any>

Takes an item from data and renders it into the list

Type	Required
function	Yes

---

data

The default accessor functions assume this is an array of objects with shape {key: string} but you can override getItem, getItemCount, and keyExtractor to handle any type of index-based data.

Type	Required
any	Yes

---

getItem

(data: any, index: number) => object;

A generic accessor for extracting an item from any sort of data blob.

Type	Required
function	Yes

---

getItemCount

(data: any) => number;

Determines how many items are in the data blob.

Type	Required
function	Yes

---

debug

debug will turn on extra logging and visual overlays to aid with debugging both usage and implementation, but with a significant perf hit.

Type	Required
boolean	No

---

extraData

A marker property for telling the list to re-render (since it implements PureComponent). If any of your renderItem, Header, Footer, etc. functions depend on anything outside of the data prop, stick it here and treat it immutably.

Type	Required
any	No

---

getItemLayout

(

data: any,

index: number,

) => {length: number, offset: number, index: number}

Type	Required
function	No

---

initialScrollIndex

Instead of starting at the top with the first item, start at initialScrollIndex. This disables the "scroll to top" optimization that keeps the first initialNumToRender items always rendered and immediately renders the items starting at this initial index. Requires getItemLayout to be implemented.

Type	Required
number	No

---

inverted

Reverses the direction of scroll. Uses scale transforms of -1.

Type	Required
boolean	No

---

CellRendererComponent

Each cell is rendered using this element. Can be a React Component Class,or a render function. Defaults to using View.

Type	Required
component, function	No

---

ItemSeparatorComponent

Rendered in between each item, but not at the top or bottom. By default, highlighted and leadingItem props are provided. renderItem provides separators.highlight/unhighlight which will update the highlighted prop, but you can also add custom props with separators.updateProps.

Type	Required
component, function	No

---

listKey

A unique identifier for this list. If there are multiple VirtualizedLists at the same level of nesting within another VirtualizedList, this key is necessary for virtualization to work properly.

Type	Required
string	True

---

ListEmptyComponent

Rendered when the list is empty. Can be a React Component Class, a render function, or a rendered element.

Type	Required
component, function, element	No

---

ListItemComponent

Each data item is rendered using this element. Can be a React Component Class, or a render function

Type	Required
component, function	No

---

ListFooterComponent

Rendered at the bottom of all the items. Can be a React Component Class, a render function, or a rendered element.

Type	Required
component, function, element	No

---

ListFooterComponentStyle

Styling for internal View for ListFooterComponent

Type	Required
ViewStyleProp	No

---

ListHeaderComponent

Rendered at the top of all the items. Can be a React Component Class, a render function, or a rendered element.

Type	Required
component, function, element	No

---

ListHeaderComponentStyle

Styling for internal View for ListHeaderComponent

Type	Required
ViewStyleProp	No

---

onRefresh

() => void

If provided, a standard RefreshControl will be added for "Pull to Refresh" functionality. Make sure to also set the refreshing prop correctly.

Type	Required
function	No

---

onScrollToIndexFailed

(info: {

index: number,

highestMeasuredFrameIndex: number,

averageItemLength: number,

}) => void

Used to handle failures when scrolling to an index that has not been measured yet. Recommended action is to either compute your own offset and scrollTo it, or scroll as far as possible and then try again after more items have been rendered.

Type	Required
function	No

---

onViewableItemsChanged

(info: {

viewableItems: array,

changed: array,

}) => void

Called when the viewability of rows changes, as defined by the viewabilityConfig prop.

Type	Required
function	No

---

refreshing

Set this true while waiting for new data from a refresh.

Type	Required
boolean	No

---

refreshControl

A custom refresh control element. When set, it overrides the default <RefreshControl> component built internally. The onRefresh and refreshing props are also ignored. Only works for vertical VirtualizedList.

Type	Required
element	No

---

removeClippedSubviews

This may improve scroll performance for large lists.

Note: May have bugs (missing content) in some circumstances - use at your own risk.

Type	Required
boolean	No

---

renderScrollComponent

(props: object) => element;

Render a custom scroll component, e.g. with a differently styled RefreshControl.

Type	Required
function	No

---

viewabilityConfig

See ViewabilityHelper.js for flow type and further documentation.

Type	Required
ViewabilityConfig	No

---

viewabilityConfigCallbackPairs

List of ViewabilityConfig/onViewableItemsChanged pairs. A specific onViewableItemsChanged will be called when its corresponding ViewabilityConfig's conditions are met. See ViewabilityHelper.js for flow type and further documentation.

Type	Required
array of ViewabilityConfigCallbackPair	No

---

horizontal

Type	Required
boolean	No

---

initialNumToRender

How many items to render in the initial batch. This should be enough to fill the screen but not much more. Note these items will never be unmounted as part of the windowed rendering in order to improve perceived performance of scroll-to-top actions.

Type	Required
number	Yes

---

keyExtractor

(item: object, index: number) => string;

Used to extract a unique key for a given item at the specified index. Key is used for caching and as the react key to track item re-ordering. The default extractor checks item.key, then falls back to using the index, like React does.

Type	Required
function	No

---

maxToRenderPerBatch

The maximum number of items to render in each incremental render batch. The more rendered at once, the better the fill rate, but responsiveness may suffer because rendering content may interfere with responding to button taps or other interactions.

Type	Required
number	No

---

onEndReached

(info: {distanceFromEnd: number}) => void

Called once when the scroll position gets within onEndReachedThreshold of the rendered content.

Type	Required
function	No

---

onEndReachedThreshold

How far from the end (in units of visible length of the list) the bottom edge of the list must be from the end of the content to trigger the onEndReached callback. Thus a value of 0.5 will trigger onEndReached when the end of the content is within half the visible length of the list.

Type	Required
number	No

---

updateCellsBatchingPeriod

Amount of time between low-pri item render batches, e.g. for rendering items quite a ways off screen. Similar fill rate/responsiveness tradeoff as maxToRenderPerBatch.

Type	Required
number	No

---

windowSize

Determines the maximum number of items rendered outside of the visible area, in units of visible lengths. So if your list fills the screen, then windowSize={21} (the default) will render the visible screen area plus up to 10 screens above and 10 below the viewport. Reducing this number will reduce memory consumption and may improve performance, but will increase the chance that fast scrolling may reveal momentary blank areas of unrendered content.

Type	Required
number	No

---

disableVirtualization

Deprecated. Virtualization provides significant performance and memory optimizations, but fully unmounts react instances that are outside of the render window. You should only need to disable this for debugging purposes.

Type	Required
	No

---

persistentScrollbar

Type	Required
bool	No

---

progressViewOffset

Set this when offset is needed for the loading indicator to show correctly.

Type	Required	Platform
number	No	Android

Methods

scrollToEnd()

scrollToEnd((params: object));

Valid `params` consist of:

- 'animated' (boolean). Optional default is true.

---

scrollToIndex()

scrollToIndex((params: object));

Valid params consist of:

• 'animated' (boolean). Optional.
• 'index' (number). Required.
• 'viewOffset' (number). Optional.
• 'viewPosition' (number). Optional.

---

scrollToItem()

scrollToItem((params: object));

Valid params consist of:

• 'animated' (boolean). Optional.
• 'item' (Item). Required.
• 'viewPosition' (number). Optional.

---

scrollToOffset()

scrollToOffset((params: object));

Scroll to a specific content pixel offset in the list.

Param offset expects the offset to scroll to. In case of horizontal is true, the offset is the x-value, in any other case the offset is the y-value.

Param animated (true by default) defines whether the list should do an animation while scrolling.

---

recordInteraction()

recordInteraction();

---

flashScrollIndicators()

flashScrollIndicators();

---

getScrollResponder()

getScrollResponder () => ?ScrollResponderType;

Provides a handle to the underlying scroll responder. Note that this._scrollRef might not be a ScrollView, so we need to check that it responds to getScrollResponder before calling it.

---

getScrollableNode()

getScrollableNode () => ?number;

---

getScrollRef()

getScrollRef () => | ?React.ElementRef<typeof ScrollView>

| ?React.ElementRef<typeof View>;

---

setNativeProps()

setNativeProps((props: Object));

---

getChildContext()

getChildContext () => Object;

The Object returned consist of:

• 'virtualizedList' (Object). This object consist of the following
  • getScrollMetrics' (Function). Returns an object with following properties: { contentLength: number, dOffset: number, dt: number, offset: number, timestamp: number, velocity: number, visibleLength: number }.
  • 'horizontal' (boolean) - Optional.
  • 'getOutermostParentListRef' (Function).
  • 'getNestedChildState' (Function) - Returns ChildListState .
  • 'registerAsNestedChild' (Function). This accept an object with following properties { cellKey: string, key: string, ref: VirtualizedList, parentDebugInfo: ListDebugInfo }. It returns a ChildListState
  • 'unregisterAsNestedChild' (Function). This takes an object with following properties, { key: string, state: ChildListState }
  • 'debugInfo' (ListDebugInfo).

---

hasMore()

hasMore () => boolean;