Flutter ListView and ScrollPhysics: A Detailed Look

Exploring the ListView Widget and its Features in Depth

A while ago, I wrote an article on the basics of using a ListView and GridView in Flutter. This article is meant as a more detailed exploration on the ListView class, ScrollPhysics and tweaks and optimisations for the general widget.

A ListView in Flutter is a linear list of scrollable items. We can use it to make a list of items scrollable or make a list of repeating items.

Exploring the types of ListView

We’ll start with looking at the types of ListViews and later look at the other features and neat modifications for it.

Let’s look at the types of ListViews there are:

  1. ListView
  2. ListView.builder
  3. ListView.separated
  4. ListView.custom

Let’s go around exploring these types one by one:


This is the default constructor of the ListView class. A ListView simply takes a list of children and makes it scrollable.

A List constructed using the default constructor

The general format of the code is:

children: <Widget>[

Usually this should be used with a small number of children as the List will also construct the invisible elements in the list and a large amount of elements may render this inefficient.


The builder() constructor constructs a repeating list of items. The constructor takes two main parameters: An itemCount for the number of items in the list and an itemBuilder for constructed each list item.

A List constructed using the builder() constructor

The general format of the code is:

itemCount: itemCount,
itemBuilder: (context, position) {
return listItem();

The list items are constructed lazily, meaning only a specific number of list items are constructed and when a user scrolls ahead, the earlier ones are destroyed.

Neat trick: Since the elements are loaded lazily and only the needed number of elements are loaded, we don’t really need an itemCount as a compulsory parameter and the list can be infinite.

itemBuilder: (context, position) {
return Card(
child: Padding(
padding: const EdgeInsets.all(16.0),
child: Text(position.toString(), style: TextStyle(fontSize: 22.0),),
A ListView without the itemCount parameter


In the separated() constructor, we generate a list and we can specify the separator between each item.

A ListView constructed using the ListView.separated() constructor

In essence, we construct two interweaved lists: one as the main list, one as the separator list.

Note that the infinite count discussed in the earlier constructor cannot be used here and this constructor enforces an itemCount.

The code for this type goes as:

itemBuilder: (context, position) {
return ListItem();
separatorBuilder: (context, position) {
return SeparatorItem();
itemCount: itemCount,

This type of list lets you dynamically define separators, have different types of separators for different types of items, add or remove separators when needed, etc.

This implementation can also be used for inserting other types of elements (advertisements for example) easily and without any modification to the main list in the middle of the list items.

Example shows advertisement when position is divisible by 4

Note: The separator list length is 1 less than the item list as a separator does not exist after the last element.


The custom() constructor as its name suggests, lets you build ListViews with custom functionality for how the children of the list are built. The main parameter required for this is a SliverChildDelegate which builds the items. The types of SliverChildDelegates are

  1. SliverChildListDelegate
  2. SliverChildBuilderDelegate

SliverChildListDelegate accepts a direct list of children whereas SliverChildBuiderDelegate accepts an IndexedWidgetBuilder (The builder function we use).

You can either use or subclass these for building your own delegates.

ListView.builder is essentially a ListView.custom with a SliverChildBuilderDelegate.

The ListView default constructor behaves like a ListView.custom with a SliverChildListDelegate.

Now that we’re done with the types of ListViews, let’s take a look at ScrollPhysics.

Exploring ScrollPhysics

To control the way scrolling takes place, we set the physics parameter in the ListView constructor. The different types of physics are:


NeverScrollablePhysics renders the list non-scrollable. Use this to disable scrolling of the ListView completely.


BouncingScrollPhysics bounces back the list when the list ends. A similar effect is used on iOS.


This is the default scrolling physics used on Android. The list stops at the end and gives an effect indicating it.


This is slightly different than the other ones in this list in the sense that it only works with FixedExtendScrollControllers and lists that use them. For an example we will take a ListWheelScrollView which makes a wheel-like list.

FixedExtentScrollPhysics only scrolls to items instead of any offset in between.

The code for this example is incredibly simple:

FixedExtentScrollController fixedExtentScrollController =
new FixedExtentScrollController();
controller: fixedExtentScrollController,
physics: FixedExtentScrollPhysics(),
children: monthsOfTheYear.map((month) {
return Card(
child: Row(
children: <Widget>[
child: Padding(
padding: const EdgeInsets.all(8.0),
child: Text(
style: TextStyle(fontSize: 18.0),
itemExtent: 60.0,

A few more things to know

How to keep elements that get destroyed alive in a list?

Flutter provides a KeepAlive() widget which keeps an item alive which would have otherwise be destroyed. In a list, elements are wrapped by default in a AutomaticKeepAlive widget.

AutomaticKeepAlives can be disabled by setting the addAutomaticKeepAlives field to false. This is useful in cases where the elements don’t need to be kept alive or for a custom implementation of KeepAlive.

Why does my ListView have space between the list and the outer widget?

By default, a ListView has padding between it and the outer widget, to remove it, set padding to EdgeInsets.all(0.0).

That’s it for this article! I hope you enjoyed it and leave a few claps if you did. Follow me for more Flutter articles and comment for any feedback you might have about this article.

Some of my other articles