State management comparison in Flutter

Introduction

State management helps your app remember and update information on the screen. It keeps your app working smoothly when things change.

When you want to update the screen after a button press.

When you need to share data between different parts of your app.

When your app has forms or inputs that change over time.

When you want to keep track of user login status.

When you want to handle data from the internet and show it on the screen.

Syntax

Flutter

class MyWidget extends StatefulWidget {
  @override
  State<MyWidget> createState() => _MyWidgetState();
}

class _MyWidgetState extends State<MyWidget> {
  int counter = 0;

  void increment() {
    setState(() {
      counter++;
    });
  }

  @override
  Widget build(BuildContext context) {
    return Text('Count: $counter');
  }
}

setState() tells Flutter to update the screen with new data.

State can be local (inside one widget) or shared (across many widgets).

Examples

Simple local state update inside a StatefulWidget.

Flutter

int counter = 0;

void increment() {
  setState(() {
    counter++;
  });
}

Example of global state using Riverpod package.

Flutter

final counterProvider = StateProvider<int>((ref) => 0);

// Using Riverpod to manage state globally.

Provider with ChangeNotifier to notify widgets when data changes.

Flutter

class CounterModel extends ChangeNotifier {
  int _count = 0;
  int get count => _count;

  void increment() {
    _count++;
    notifyListeners();
  }
}

// Using Provider package with ChangeNotifier.

Sample App

This app shows a number on the screen. When you press the + button, the number goes up. It uses local state inside a StatefulWidget.

Flutter

import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

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

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: CounterScreen(),
    );
  }
}

class CounterScreen extends StatefulWidget {
  @override
  State<CounterScreen> createState() => _CounterScreenState();
}

class _CounterScreenState extends State<CounterScreen> {
  int _count = 0;

  void _increment() {
    setState(() {
      _count++;
    });
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(title: const Text('Counter Example')),
      body: Center(
        child: Text('Count: $_count', style: const TextStyle(fontSize: 24)),
      ),
      floatingActionButton: FloatingActionButton(
        onPressed: _increment,
        child: const Icon(Icons.add),
        tooltip: 'Increment',
      ),
    );
  }
}

Important Notes

Local state with setState() is simple but only works inside one widget.

For bigger apps, use packages like Provider, Riverpod, or Bloc to share state easily.

Choose state management based on app size and complexity.

Summary

State management keeps your app data and UI in sync.

Use setState() for small, local changes.

Use Provider, Riverpod, or Bloc for bigger apps with shared data.

Practice

1.

Which Flutter state management method is best for simple, local UI updates within a single widget?

easy

A. Using Bloc for complex event handling

B. Using the Provider package for global state

C. Using setState() inside a StatefulWidget

D. Using Riverpod for dependency injection

Solution

1. Step 1: Understand the scope of setState()

   setState() is designed for small, local changes inside a StatefulWidget.

2. Step 2: Compare with other methods

   Provider, Bloc, and Riverpod are better for shared or complex state across multiple widgets.

3. Final Answer:

   Using setState() inside a StatefulWidget -> Option C

4. Quick Check:

   Local UI updates = setState() [OK]

Hint: Use setState() for small widget-only changes [OK]

Common Mistakes:

• Thinking Provider is simpler for local state
• Using Bloc for tiny UI updates
• Confusing Riverpod with setState()

2.

Which of the following is the correct syntax to update state using setState() in Flutter?

???

easy

A. setState(counter++);

B. setState { counter++; }

C. setState(=> counter++);

D. setState(() { counter++; });

Solution

1. Step 1: Recall the setState() method signature

   setState() takes a function with no parameters that updates the state inside its body.

2. Step 2: Check each option's syntax

   setState(() { counter++; }); correctly uses a function block. setState { counter++; } misses parentheses. setState(=> counter++); misses parentheses after setState. setState(counter++); passes a value, not a function.

3. Final Answer:

   setState(() { counter++; }); -> Option D

4. Quick Check:

   setState requires a function block [OK]

Hint: setState needs a function with braces () { } [OK]

Common Mistakes:

• Omitting parentheses after setState
• Passing expressions instead of functions
• Using arrow syntax incorrectly

3.

Given this Flutter code snippet using Provider:

class Counter with ChangeNotifier {
  int value = 0;
  void increment() {
    value++;
    notifyListeners();
  }
}

// In widget:
final counter = Provider.of<Counter>(context);
counter.increment();
print(counter.value);

What will be printed after calling increment()?

medium

A. 1

B. An error occurs

C. null

D. 0

Solution

1. Step 1: Understand the increment method

   The method increases value by 1 and calls notifyListeners() to update UI.

2. Step 2: Check the printed value after increment

   Since value starts at 0 and increments once, the printed value is 1.

3. Final Answer:

   1 -> Option A

4. Quick Check:

   Provider state increments value to 1 [OK]

Hint: Increment then print shows updated value [OK]

Common Mistakes:

• Forgetting notifyListeners() updates UI
• Assuming value stays 0 after increment
• Confusing Provider with setState()

4.

Identify the error in this Flutter Bloc usage snippet:

class CounterCubit extends Cubit<int> {
  CounterCubit() : super(0);
  void increment() {
    state++;
    emit(state);
  }
}

medium

A. Missing call to super.increment()

B. Cannot mutate state directly; it is immutable

C. emit() should not be called inside increment()

D. Cubit must extend Bloc, not Cubit

Solution

1. Step 1: Understand Cubit state immutability

   The state property is immutable; you cannot change it directly.

2. Step 2: Identify correct way to update state

   You must emit a new value, e.g., emit(state + 1);, instead of modifying state directly.

3. Final Answer:

   Cannot mutate state directly; it is immutable -> Option B

4. Quick Check:

   Cubit state is immutable, use emit(newValue) [OK]

Hint: Cubit state is immutable; never change state directly [OK]

Common Mistakes:

• Trying to increment state variable directly
• Calling super.increment() which doesn't exist
• Confusing Cubit with Bloc inheritance

5.

You have a Flutter app with multiple widgets needing access to user login status and theme settings. Which state management approach is best and why?

hard

A. Use Provider or Riverpod to share state across widgets

B. Use setState() in each widget separately

C. Use local variables inside widgets without state management

D. Use Bloc only for UI animations

Solution

1. Step 1: Analyze the need for shared state

   Login status and theme settings are shared data needed by multiple widgets.

2. Step 2: Choose appropriate state management

   setState() is local and not suitable for sharing. Provider or Riverpod efficiently share and update state across widgets.

3. Step 3: Exclude incorrect options

   Local variables don't update UI globally. Bloc is more complex and not just for animations.

4. Final Answer:

   Use Provider or Riverpod to share state across widgets -> Option A

5. Quick Check:

   Shared app state = Provider or Riverpod [OK]

Hint: Use Provider/Riverpod for shared app-wide state [OK]

Common Mistakes:

• Using setState() for global shared data
• Ignoring state management for shared info
• Misusing Bloc only for animations