BLoC pattern basics in Flutter - Build, Publish & Deploy

Build & Publish - BLoC pattern basics

Performance Impact

The BLoC (Business Logic Component) pattern helps keep your Flutter app smooth by separating UI from logic. This separation reduces unnecessary widget rebuilds, helping maintain a steady 60 frames per second (fps) for smooth animations and scrolling. Proper use of streams and sinks in BLoC minimizes memory leaks and battery drain by disposing of unused resources promptly.

Optimization Tips

To optimize BLoC for 60fps rendering, avoid heavy computations inside the BLoC that block the main thread. Use asynchronous operations and isolate heavy tasks if needed. Dispose of BLoC instances properly to free memory. Use StreamBuilder widgets wisely to rebuild only parts of the UI that need updating, preventing unnecessary redraws.

App Size and Startup Time

Implementing BLoC adds minimal code size since it mainly organizes existing logic. It does not significantly increase your app bundle size. Startup time remains fast because BLoC initializes only when needed, not at app launch. Keeping BLoC classes lean and avoiding large dependencies helps maintain quick startup.

iOS vs Android Differences

BLoC pattern works the same on both iOS and Android since it is Flutter-based. However, iOS devices may have stricter memory limits (~1.5GB), so efficient disposal of streams is crucial. Android devices vary more in performance and memory, so testing on multiple devices is important. Both platforms benefit equally from BLoC's separation of concerns for maintainability and performance.

Store Review Guidelines

Both Apple App Store and Google Play require apps to be stable and responsive. Using BLoC helps meet these by preventing UI freezes and crashes. Ensure your app handles errors gracefully in streams to avoid unexpected terminations. Follow platform-specific guidelines for privacy and data handling, as BLoC does not affect these directly but your app logic might.

Self-Check

Your app takes 5 seconds to load this screen. What's likely wrong?

• Heavy synchronous work blocking the UI thread inside the BLoC.
• Not disposing of streams causing memory leaks and slowdowns.
• Rebuilding large widget trees unnecessarily due to improper StreamBuilder usage.

Key Result

Using the BLoC pattern in Flutter improves app performance by separating UI and logic, enabling smooth 60fps rendering and efficient memory use, while adding minimal app size and supporting both iOS and Android equally.

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