BLoC pattern basics in Flutter - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does BLoC stand for in Flutter development?

BLoC stands for Business Logic Component. It helps separate app logic from UI.

beginner

What are the main parts of the BLoC pattern?

The main parts are Events (inputs), States (outputs), and the BLoC itself which processes events and emits states.

intermediate

How does BLoC help with app testing?

BLoC separates logic from UI, making it easier to test business logic without UI dependencies.

beginner

In BLoC, what triggers a state change?

A new event sent to the BLoC triggers processing and emits a new state.

beginner

Why is it good to keep UI code separate from business logic using BLoC?

Separating UI and logic makes the app easier to maintain, test, and scale. UI just listens to states and shows them.

What is the role of an Event in the BLoC pattern?

A It represents user actions or inputs sent to the BLoC

B It is the UI widget that displays data

C It stores the app's database

D It is the final output shown on screen

Events are inputs like button taps or data requests sent to the BLoC to process.

What does the BLoC emit after processing an event?

A A new Event

B A database query

C A UI widget

D A new State

After processing an event, the BLoC emits a new State that the UI listens to.

Which of these is NOT a benefit of using BLoC?

A Separates UI from business logic

B Automatically creates UI widgets

C Improves app maintainability

D Makes testing easier

BLoC does not create UI widgets automatically; it manages logic and state.

How does the UI get updated in the BLoC pattern?

A By listening to state changes emitted by the BLoC

B By sending events directly to the UI

C By modifying the database

D By rebuilding the entire app

UI listens to the BLoC's state stream and rebuilds when states change.

Which Flutter package is commonly used to implement the BLoC pattern?

A provider

B http

C flutter_bloc

D shared_preferences

The flutter_bloc package provides tools to implement BLoC easily.

Explain the flow of data in the BLoC pattern from user action to UI update.

Think about how input becomes output step-by-step.

Describe why separating business logic from UI is helpful in Flutter apps using BLoC.

Consider benefits for developers and app quality.

Practice

1. What is the main purpose of the BLoC pattern in Flutter?
BLoC stands for Business Logic Component.

easy

A. To separate app logic from the user interface using streams

B. To create animations easily

C. To manage database connections

D. To style widgets with themes

Solution

1. Step 1: Understand BLoC purpose

   BLoC is designed to separate business logic from UI to keep code clean and testable.

2. Step 2: Identify correct function

   Among options, only separation of logic and UI using streams matches BLoC's goal.

3. Final Answer:

   To separate app logic from the user interface using streams -> Option A

4. Quick Check:

   BLoC = Separate logic and UI [OK]

Hint: Remember BLoC means separating logic from UI with streams [OK]

Common Mistakes:

• Confusing BLoC with UI styling or animations
• Thinking BLoC manages databases directly
• Assuming BLoC is only for UI widgets

2. Which of the following is the correct way to create a StreamController in Dart for BLoC?

easy

A. var controller = Stream();

B. var controller = StreamController<int>();

C. var controller = ControllerStream();

D. var controller = StreamBuilder();

Solution

1. Step 1: Recall StreamController syntax

   In Dart, StreamController is created by calling its constructor: StreamController<int>().

2. Step 2: Check options for correct syntax

   Only var controller = StreamController<int>(); uses correct class and constructor syntax.

3. Final Answer:

   var controller = StreamController<int>(); -> Option B

4. Quick Check:

   StreamController() constructor = var controller = StreamController(); [OK]

Hint: StreamController is a class, so use its constructor with parentheses [OK]

Common Mistakes:

• Using Stream() instead of StreamController()
• Confusing StreamBuilder with StreamController
• Misspelling class names

3. Given this BLoC code snippet:

final _controller = StreamController<int>();
void addNumber(int n) {
  _controller.sink.add(n);
}

Stream<int> get stream => _controller.stream;

// In UI:
StreamBuilder<int>(
  stream: bloc.stream,
  builder: (context, snapshot) {
    return Text(snapshot.data?.toString() ?? 'No data');
  },
);

What will the UI show after calling addNumber(5)?

medium

A. 5

B. No data

C. null

D. Error

Solution

1. Step 1: Understand data flow

   Calling addNumber(5) adds 5 to the stream sink, which emits 5 to listeners.

2. Step 2: StreamBuilder updates UI

   StreamBuilder listens to stream and rebuilds Text widget with snapshot.data = 5.

3. Final Answer:

   5 -> Option A

4. Quick Check:

   Stream emits 5, UI shows 5 [OK]

Hint: StreamBuilder shows latest stream data in UI [OK]

Common Mistakes:

• Thinking UI shows 'No data' after adding a number
• Confusing snapshot.data with snapshot.hasData
• Assuming null is shown instead of actual data

4. Identify the error in this BLoC snippet:

class CounterBloc {
  final _controller = StreamController<int>();

  void increment() {
    _controller.sink.add(_counter + 1);
  }

  Stream<int> get stream => _controller.stream;
}

Assuming _counter is not declared anywhere, what is the issue?

medium

A. increment() should return a value

B. StreamController is not closed properly

C. Stream getter should be a method, not a property

D. _counter is not defined, causing a compile error

Solution

1. Step 1: Check variable usage

   _counter is used but never declared or initialized, causing an error.

2. Step 2: Review other options

   While closing StreamController is good practice, missing _counter causes immediate compile error.

3. Final Answer:

   _counter is not defined, causing a compile error -> Option D

4. Quick Check:

   Undefined variable = compile error [OK]

Hint: Undefined variables cause compile errors immediately [OK]

Common Mistakes:

• Ignoring missing variable declarations
• Confusing Stream getter syntax
• Thinking StreamController must always be closed immediately

5. You want to create a BLoC that filters out even numbers and only emits odd numbers to the UI. Which code snippet correctly implements this behavior?

hard

A. final _controller = StreamController<int>();
Stream<int> get stream => _controller.stream.skip(1);

B. final _controller = StreamController<int>();
Stream<int> get stream => _controller.stream.map((n) => n * 2);

C. final _controller = StreamController<int>();
Stream<int> get stream => _controller.stream.where((n) => n % 2 != 0);

D. final _controller = StreamController<int>();
Stream<int> get stream => _controller.stream.where((n) => n % 2 == 0);

Solution

1. Step 1: Understand filtering logic

   We want to emit only odd numbers, so filter with condition n % 2 != 0.

2. Step 2: Check each option's stream transformation

   Only the transformation using where((n) => n % 2 != 0) correctly filters odd numbers. The others either skip the first element, double the numbers with map, or filter even numbers with where((n) => n % 2 == 0).

3. Final Answer:

   final _controller = StreamController<int>();\nStream<int> get stream => _controller.stream.where((n) => n % 2 != 0); -> Option C

4. Quick Check:

   Filter odd numbers with where(n % 2 != 0) [OK]

Hint: Use where() with condition to filter stream data [OK]

Common Mistakes:

• Using map() instead of where() for filtering
• Filtering even numbers instead of odd
• Using skip() which removes elements by count