Infinite scrolling in Flutter - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ ui_behavior

intermediate

Detecting scroll position for infinite scrolling

In Flutter, which code snippet correctly detects when the user has scrolled to the bottom of a ListView to trigger loading more items?

Flutter

ScrollController _controller = ScrollController();

_controller.addListener(() {
  if (_controller.position.pixels == _controller.position.maxScrollExtent) {
    // Load more items
  }
});

A if (_controller.position.pixels >= _controller.position.minScrollExtent) { /* load more */ }

B if (_controller.position.pixels == _controller.position.maxScrollExtent) { /* load more */ }

C if (_controller.offset == 0) { /* load more */ }

D if (_controller.position.atEdge) { /* load more */ }

💡 Hint

Think about when the scroll position reaches the bottom edge.

The scroll position's pixels equal to maxScrollExtent means the user reached the bottom. Option B checks this exactly. Option B checks if at any edge (top or bottom), which is not specific enough.

❓ lifecycle

intermediate

Properly disposing ScrollController

Which Flutter widget lifecycle method is the best place to dispose a ScrollController to avoid memory leaks?

A dispose()

B initState()

C didChangeDependencies()

D build()

💡 Hint

Think about cleaning up resources when the widget is removed.

dispose() is called when the widget is removed permanently. It's the right place to dispose controllers. initState() is for initialization, build() runs often, and didChangeDependencies() is for dependency changes.

📝 Syntax

advanced

Correct async data loading in infinite scroll

Which code snippet correctly loads more data asynchronously when the user scrolls to the bottom, updating the UI in Flutter?

Flutter

void _loadMore() async {
  final newItems = await fetchItems();
  setState(() {
    items.addAll(newItems);
  });
}

_controller.addListener(() {
  if (_controller.position.pixels == _controller.position.maxScrollExtent) {
    _loadMore();
  }
});

A Use async function _loadMore with await fetchItems and call setState to add new items.

B Call fetchItems without await and update items directly without setState.

C Use a synchronous function to fetch items and update items inside setState.

D Call setState before await fetchItems to update UI early.

💡 Hint

UI updates must happen inside setState after data is ready.

Option A correctly waits for data asynchronously, then updates state inside setState. Option A misses await and setState, so UI won't update properly. Option A updates UI before data is ready. Option A uses synchronous fetch which is unrealistic for network calls.

❓ navigation

advanced

Maintaining scroll position after navigation

After navigating back to a screen with infinite scrolling, which approach preserves the scroll position in Flutter?

A Use a GlobalKey to rebuild the entire widget tree.

B Create a new ScrollController every time the widget rebuilds.

C Reset the scroll position to zero in initState().

D Keep the ScrollController as a member variable and do not recreate it on rebuild.

💡 Hint

Think about keeping the controller alive to remember scroll offset.

Keeping the same ScrollController preserves scroll offset. Creating a new one resets position. Resetting scroll to zero loses position. GlobalKey rebuilds widget but does not preserve scroll automatically.

🧠 Conceptual

expert

Handling rapid scroll events in infinite scrolling

What is the best way to prevent multiple simultaneous data fetches when the user scrolls quickly to the bottom multiple times in Flutter infinite scrolling?

A Call the data fetch function every time the scroll reaches bottom without checks.

B Clear the items list before each fetch to avoid duplicates.

C Use a boolean flag to track if a fetch is in progress and ignore new fetch requests until done.

D Use a timer to delay all fetches by 5 seconds.

💡 Hint

Think about how to avoid starting a new fetch before the previous finishes.

Using a boolean flag (e.g., isLoading) prevents starting multiple fetches simultaneously. Calling fetch every time causes duplicate requests. Clearing items loses data. Delaying fetches arbitrarily can cause bad UX.

Practice

1. What is the main purpose of using infinite scrolling in a Flutter app?

easy

A. To load more content automatically as the user scrolls down

B. To preload all data before showing the screen

C. To prevent any scrolling on the screen

D. To refresh the entire app when the user taps a button

Solution

1. Step 1: Understand infinite scrolling concept

   Infinite scrolling means loading more data automatically when the user reaches the bottom of the list.

2. Step 2: Compare options with this concept

   Only To load more content automatically as the user scrolls down describes loading more content as the user scrolls down, which matches infinite scrolling.

3. Final Answer:

   To load more content automatically as the user scrolls down -> Option A

4. Quick Check:

   Infinite scrolling = load more on scroll [OK]

Hint: Infinite scrolling means loading more items when scrolling down [OK]

Common Mistakes:

• Thinking infinite scrolling means preloading all data
• Confusing infinite scrolling with pull-to-refresh
• Assuming infinite scrolling disables scrolling

2. Which Flutter widget is commonly used to detect scroll position for infinite scrolling?

easy

A. TextEditingController

B. ScrollController

C. AnimationController

D. PageController

Solution

1. Step 1: Identify controller for scroll events

   ScrollController is designed to listen to scroll position changes in scrollable widgets.

2. Step 2: Eliminate unrelated controllers

   TextEditingController is for text input, AnimationController for animations, PageController for page views, so they don't detect scroll position.

3. Final Answer:

   ScrollController -> Option B

4. Quick Check:

   ScrollController detects scroll position [OK]

Hint: ScrollController tracks scroll position for infinite scroll [OK]

Common Mistakes:

• Using TextEditingController for scrolling
• Confusing PageController with ScrollController
• Not using any controller to detect scroll

3. Given this Flutter code snippet, what will happen when the user scrolls to the bottom?

ScrollController _controller = ScrollController();

_controller.addListener(() {
  if (_controller.position.pixels == _controller.position.maxScrollExtent) {
    print('Load more items');
  }
});

medium

A. Prints 'Load more items' when user reaches bottom

B. Nothing happens when scrolling to bottom

C. Throws an error because of missing setState

D. Scrolls back to top automatically

Solution

1. Step 1: Understand the listener logic

   The listener checks if the scroll position equals the max scroll extent, meaning user reached bottom.

2. Step 2: Check the action inside listener

   When condition is true, it prints 'Load more items' to console.

3. Final Answer:

   Prints 'Load more items' when user reaches bottom -> Option A

4. Quick Check:

   Scroll at bottom triggers print [OK]

Hint: Listener triggers action at maxScrollExtent (bottom) [OK]

Common Mistakes:

• Thinking setState is required for print statements
• Assuming nothing happens without UI update
• Confusing pixels with minScrollExtent

4. Identify the error in this infinite scrolling setup:

ScrollController _controller = ScrollController();

@override
void initState() {
  super.initState();
  _controller.addListener(() {
    if (_controller.position.pixels >= _controller.position.maxScrollExtent) {
      fetchMoreData();
    }
  });
}

@override
void dispose() {
  super.dispose();
}

medium

A. initState should not call super.initState()

B. Incorrect comparison operator in listener

C. Missing call to _controller.dispose() in dispose method

D. fetchMoreData() should be called in build method

Solution

1. Step 1: Check lifecycle methods for controller cleanup

   ScrollController must be disposed in dispose() to avoid memory leaks.

2. Step 2: Verify dispose method implementation

   dispose() calls super.dispose() but does not call _controller.dispose(), which is required.

3. Final Answer:

   Missing call to _controller.dispose() in dispose method -> Option C

4. Quick Check:

   Dispose controllers to prevent leaks [OK]

Hint: Always dispose controllers in dispose() method [OK]

Common Mistakes:

• Forgetting to dispose ScrollController
• Calling fetchMoreData() in build causing repeated calls
• Misunderstanding lifecycle method order

5. You want to implement infinite scrolling with a loading spinner at the bottom. Which approach correctly shows the spinner only while loading new items?

hard

A. Always show CircularProgressIndicator at bottom regardless of loading state

B. Replace entire ListView with spinner when loading

C. Use a Timer to show spinner for fixed 5 seconds after scroll

D. Add a boolean isLoading state; show CircularProgressIndicator in ListView footer when true

Solution

1. Step 1: Understand conditional UI for loading spinner

   Spinner should appear only when new data is loading, controlled by a boolean state.

2. Step 2: Evaluate options for showing spinner

   Add a boolean isLoading state; show CircularProgressIndicator in ListView footer when true uses isLoading boolean to conditionally show spinner in ListView footer, which is correct.

3. Step 3: Why other options are incorrect

   Always show CircularProgressIndicator at bottom regardless of loading state always shows spinner, confusing users. Use a Timer to show spinner for fixed 5 seconds after scroll uses fixed timer unrelated to actual loading. Replace entire ListView with spinner when loading hides list, bad UX.

4. Final Answer:

   Add a boolean isLoading state; show CircularProgressIndicator in ListView footer when true -> Option D

5. Quick Check:

   Show spinner only while loading = use boolean state [OK]

Hint: Use boolean state to toggle loading spinner visibility [OK]

Common Mistakes:

• Showing spinner all the time confusing users
• Using timers instead of actual loading state
• Hiding list instead of appending new items