Loading and error states in Flutter

Introduction

Loading and error states help users know what is happening in the app. They show when data is loading or if something went wrong.

When fetching data from the internet and waiting for a response.

When saving information and the app needs time to finish.

When a network error happens and the app cannot get data.

When a process takes time and the user should wait.

When showing a message if something fails.

Syntax

Flutter

if (isLoading) {
  return CircularProgressIndicator();
} else if (hasError) {
  return Text('Error loading data');
} else {
  return YourContentWidget();
}

Use a boolean like isLoading to show a spinner.

Use a boolean like hasError to show an error message.

Examples

Show a spinner while loading.

Flutter

if (isLoading) {
  return CircularProgressIndicator();
}

Show a simple error message if loading fails.

Flutter

if (hasError) {
  return Text('Failed to load data');
}

Show spinner while loading, then show data.

Flutter

if (isLoading) {
  return CircularProgressIndicator();
} else {
  return Text('Data loaded');
}

Sample App

This app shows a spinner for 3 seconds to simulate loading. Then it shows a success message. You can change hasError to true to see the error message instead.

Flutter

import 'package:flutter/material.dart';

void main() => runApp(const MyApp());

class MyApp extends StatefulWidget {
  const MyApp({super.key});

  @override
  State<MyApp> createState() => _MyAppState();
}

class _MyAppState extends State<MyApp> {
  bool isLoading = true;
  bool hasError = false;

  @override
  void initState() {
    super.initState();
    // Simulate loading data
    Future.delayed(const Duration(seconds: 3), () {
      setState(() {
        isLoading = false;
        hasError = false; // Change to true to test error state
      });
    });
  }

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Scaffold(
        appBar: AppBar(title: const Text('Loading and Error States')),
        body: Center(
          child: isLoading
              ? const CircularProgressIndicator()
              : hasError
                  ? const Text('Error loading data', style: TextStyle(color: Colors.red, fontSize: 18))
                  : const Text('Data loaded successfully!', style: TextStyle(fontSize: 18)),
        ),
      ),
    );
  }
}

Important Notes

Always give feedback to users so they know the app is working.

Use colors and icons to make error messages clear.

Keep loading states simple and easy to understand.

Summary

Loading states show a spinner or progress while waiting.

Error states show a message if something goes wrong.

Use simple booleans to control what the user sees.

Practice

1. What is the main purpose of showing a loading state in a Flutter app?

easy

A. To inform the user that data is being fetched or processed

B. To display an error message when something fails

C. To navigate to a new screen automatically

D. To permanently block user interaction

Solution

1. Step 1: Understand loading state purpose

   Loading states indicate to users that the app is busy fetching or processing data.

2. Step 2: Differentiate from error state

   Error states show problems, not progress. Loading states show progress.

3. Final Answer:

   To inform the user that data is being fetched or processed -> Option A

4. Quick Check:

   Loading state = show progress [OK]

Hint: Loading means waiting, not error or navigation [OK]

Common Mistakes:

• Confusing loading with error messages
• Thinking loading blocks app permanently
• Assuming loading triggers navigation

2. Which Flutter widget is commonly used to show a loading spinner?

easy

A. Text

B. ListView

C. CircularProgressIndicator

D. Container

Solution

1. Step 1: Identify loading spinner widget

   CircularProgressIndicator is the built-in widget for showing a spinner in Flutter.

2. Step 2: Exclude other widgets

   Text shows text, Container is a box, ListView shows lists, none show spinners.

3. Final Answer:

   CircularProgressIndicator -> Option C

4. Quick Check:

   Spinner widget = CircularProgressIndicator [OK]

Hint: Spinner = CircularProgressIndicator in Flutter [OK]

Common Mistakes:

• Using Text widget to show spinner
• Confusing Container with spinner
• Trying to use ListView for loading

3. What will the following Flutter code display when isLoading is true?

bool isLoading = true;

Widget build(BuildContext context) {
  if (isLoading) {
    return CircularProgressIndicator();
  } else {
    return Text('Data loaded');
  }
}

medium

A. A text saying 'Data loaded'

B. A runtime error

C. An empty screen

D. A circular loading spinner

Solution

1. Step 1: Check condition when isLoading is true

   The if condition is true, so CircularProgressIndicator() is returned.

2. Step 2: Understand widget output

   CircularProgressIndicator shows a spinner, not text or error.

3. Final Answer:

   A circular loading spinner -> Option D

4. Quick Check:

   isLoading true shows spinner [OK]

Hint: If isLoading true, show spinner widget [OK]

Common Mistakes:

• Assuming text shows when loading is true
• Expecting empty screen instead of spinner
• Thinking code causes error

4. Identify the error in this Flutter snippet for showing error or loading states:

bool hasError = false;
bool isLoading = true;

Widget build(BuildContext context) {
  if (hasError) {
    return Text('Error occurred');
  } else if (isLoading) {
    CircularProgressIndicator();
  } else {
    return Text('Content loaded');
  }
}

medium

A. Missing return before CircularProgressIndicator()

B. Wrong boolean variable names

C. Text widget cannot show error messages

D. Using else if instead of if

Solution

1. Step 1: Check all return statements

   hasError branch returns Text, else branch returns Text, but isLoading branch calls CircularProgressIndicator without return.

2. Step 2: Understand Flutter build method needs return

   Every branch must return a widget; missing return causes error.

3. Final Answer:

   Missing return before CircularProgressIndicator() -> Option A

4. Quick Check:

   All branches must return widgets [OK]

Hint: Always return widgets in build method branches [OK]

Common Mistakes:

• Forgetting return keyword before widgets
• Confusing variable names
• Thinking else if is wrong here

5. You want to show a loading spinner, then an error message if loading fails, or content if successful. Which Flutter widget structure correctly handles this with booleans isLoading and hasError?

hard

A. if (isLoading) return CircularProgressIndicator(); else if (hasError) return Text('Error'); else return Text('Content');

B. if (hasError) return Text('Error'); else if (isLoading) return CircularProgressIndicator(); else return Text('Content');

C. if (isLoading && hasError) return CircularProgressIndicator(); else return Text('Content');

D. if (hasError) return CircularProgressIndicator(); else if (isLoading) return Text('Loading'); else return Text('Content');

Solution

1. Step 1: Prioritize error over loading

   If there is an error, show error message first before loading or content.

2. Step 2: Show loading only if no error and loading is true

   Then show spinner if loading is true and no error.

3. Step 3: Show content if no error and not loading

   Finally, show content when no error and loading is false.

4. Final Answer:

   if (hasError) return Text('Error'); else if (isLoading) return CircularProgressIndicator(); else return Text('Content'); -> Option B

5. Quick Check:

   Error first, then loading, then content [OK]

Hint: Show error before loading, loading before content [OK]

Common Mistakes:

• Showing loading before error
• Combining error and loading in one condition
• Using wrong widgets for states