Flutter 3.35.0 has officially landed, bringing a host of improvements across web, desktop, accessibility, UI components, and tooling.

🧠 Summary: ShrinkWrap vs Slivers in Flutter

In Flutter, managing scrollable widgets efficiently is crucial for optimal performance and user experience. This post explores two primary approaches: utilizing shrinkWrap and employing Slivers.

🔹 ShrinkWrap

• Definition: A property that, when set to true, forces the scrollable widget to size itself based on its children rather than expanding to fill available space.
• Use-Cases:
  • Embedding a scrollable widget inside another scrollable (e.g., a ListView inside a Column).
  • Situations where the number of child widgets is limited and known.
• Considerations:
  • Can lead to performance issues if used with a large number of children, as it requires computing the size of all children upfront.
  • May cause layout constraints and overflow errors if not managed carefully.

✅ Example with shrinkWrap

Column(
  children: [
    Text('Header'),
    ListView.builder(
      shrinkWrap: true,
      physics: NeverScrollableScrollPhysics(),
      itemCount: 5,
      itemBuilder: (context, index) => ListTile(
        title: Text('Item \$index'),
      ),
    ),
  ],
)

🔹 Slivers

• Definition: Specialized widgets that can produce scrollable areas with custom behaviors, allowing for more granular control over scrolling effects.
• Use-Cases:
  • Creating complex scrolling effects, such as collapsing toolbars or infinite scrolling lists.
  • Optimizing performance for large datasets by rendering only visible items.
• Considerations:
  • Requires a deeper understanding of Flutter’s rendering pipeline.
  • More verbose and complex to implement compared to standard scrollable widgets.

✅ Example with Slivers

CustomScrollView(
  slivers: [
    SliverAppBar(
      expandedHeight: 200.0,
      floating: false,
      pinned: true,
      flexibleSpace: FlexibleSpaceBar(
        title: Text('Sliver Demo'),
      ),
    ),
    SliverList(
      delegate: SliverChildBuilderDelegate(
        (context, index) => ListTile(
          title: Text('Item \$index'),
        ),
        childCount: 20,
      ),
    ),
  ],
)

🆚 Comparison

💡 Bonus Tip: Don’t Lose Lazy Loading

Sometimes, instead of using shrinkWrap: true, you can wrap your ListView with an Expanded widget. This way, Flutter keeps the lazy loading behavior, which means better performance with large lists:

Column(
  children: [
    Text('Header'),
    Expanded(
      child: ListView.builder(
        itemCount: 100,
        itemBuilder: (context, index) => ListTile(
          title: Text('Item \$index'),
        ),
      ),
    ),
  ],
)

However, be careful: this only works if the parent Column is inside a widget that provides bounded height (like a SizedBox, Expanded, or Scaffold). If not, you might run into this error:

“RenderFlex children have non-zero flex but incoming height constraints are unbounded”

To avoid this, make sure:

• The parent Column is constrained in height
• Or use a SizedBox with a fixed height for your ListView
• Or fall back to shrinkWrap if bounded height isn’t an option

📝 Conclusion

Choosing between shrinkWrap and Slivers depends on the specific requirements of your Flutter application. For simple, nested scrollable widgets with a limited number of children, shrinkWrap offers a straightforward solution. However, for complex scrolling behaviors and performance optimization with large datasets, leveraging Slivers is the recommended approach.

Understanding these tools and their appropriate use-cases is essential for building efficient and responsive Flutter applications.