Clean Architecture layers in Flutter - UI Render Trace

Component - Clean Architecture layers

This UI component visually explains the Clean Architecture layers in a Flutter app. It shows the separation of concerns by layering the UI, domain, and data parts clearly, helping beginners understand how app code is organized for maintainability and testability.

Widget Tree

Scaffold
├─ AppBar
│  └─ Text("Clean Architecture Layers")
└─ Column
   ├─ Container (Presentation Layer)
   │  └─ Text("Presentation Layer")
   ├─ Container (Domain Layer)
   │  └─ Text("Domain Layer")
   └─ Container (Data Layer)
      └─ Text("Data Layer")

The Scaffold provides the basic app structure with an AppBar showing the title. The body is a Column with three Containers stacked vertically, each labeled with one of the Clean Architecture layers: Presentation, Domain, and Data. This layout visually separates the layers for clarity.

Render Trace - 6 Steps

Step 1: Scaffold

Step 2: AppBar

Step 3: Column

Step 4: Container (Presentation Layer)

Step 5: Container (Domain Layer)

Step 6: Container (Data Layer)

State Change - Re-render

Trigger:No interactive state changes in this static UI example

Before

Static display of three layers

→

After

No change

Re-renders:No re-rendering occurs

UI Quiz - 3 Questions

Which layer in the UI is responsible for showing screens and widgets?

A Domain Layer

B Presentation Layer

C Data Layer

D AppBar

Key Insight

Using clear visual separation with colors and labels helps beginners understand how Clean Architecture divides app responsibilities into layers. This approach improves code organization and makes apps easier to maintain and test.

Practice

1. Which layer in Clean Architecture is responsible for handling the user interface in a Flutter app?

easy

A. Domain layer

B. Presentation layer

C. Data layer

D. Network layer

Solution

1. Step 1: Understand the role of each layer

   The Presentation layer manages UI elements and user interactions.

2. Step 2: Match the layer to UI responsibility

   Since UI is about what the user sees and interacts with, it belongs to the Presentation layer.

3. Final Answer:

   Presentation layer -> Option B

4. Quick Check:

   UI = Presentation layer [OK]

Hint: UI always belongs to Presentation layer [OK]

Common Mistakes:

• Confusing Domain layer with UI
• Thinking Data layer handles UI
• Assuming Network layer is part of UI

2. Which of the following is the correct way to describe the Domain layer in Clean Architecture?

easy

A. It contains business logic and rules.

B. It handles data storage and retrieval.

C. It manages UI components and widgets.

D. It deals with network requests and APIs.

Solution

1. Step 1: Identify the Domain layer's responsibility

   The Domain layer contains the core business logic and rules of the app.

2. Step 2: Eliminate incorrect options

   Data storage is Data layer, UI is Presentation, network is part of Data or external services.

3. Final Answer:

   It contains business logic and rules. -> Option A

4. Quick Check:

   Domain = Business logic [OK]

Hint: Domain layer = business rules and logic [OK]

Common Mistakes:

• Mixing Domain with Data layer
• Thinking Domain manages UI
• Confusing network tasks with Domain

3. Given the following Flutter app structure, which layer should contain the repository interface?

lib/
  presentation/
  domain/
    repositories/
  data/
    repositories_impl/

medium

A. Presentation layer

B. Data layer

C. Domain layer

D. UI layer

Solution

1. Step 1: Understand repository interface placement

   Repository interfaces define contracts for data access and belong in the Domain layer.

2. Step 2: Check the folder structure

   Domain layer has 'repositories' folder for interfaces; Data layer has 'repositories_impl' for implementations.

3. Final Answer:

   Domain layer -> Option C

4. Quick Check:

   Repository interface = Domain layer [OK]

Hint: Interfaces go in Domain, implementations in Data [OK]

Common Mistakes:

• Putting interfaces in Data layer
• Confusing UI layer with Presentation
• Ignoring folder naming conventions

4. In a Flutter app using Clean Architecture, a developer places API call code directly inside a widget class. What is the main problem with this approach?

medium

A. It violates the separation of concerns by mixing UI and data logic.

B. It improves app performance by reducing layers.

C. It follows Clean Architecture best practices.

D. It makes the Domain layer responsible for UI.

Solution

1. Step 1: Identify the problem with API calls in UI

   API calls belong in the Data layer, not in UI widgets.

2. Step 2: Understand separation of concerns

   Mixing UI and data logic breaks Clean Architecture principles, making code harder to maintain.

3. Final Answer:

   It violates the separation of concerns by mixing UI and data logic. -> Option A

4. Quick Check:

   UI should not contain data logic [OK]

Hint: Keep API calls out of UI widgets [OK]

Common Mistakes:

• Thinking mixing layers improves performance
• Assuming Domain layer handles UI
• Believing this is best practice

5. You want to add a new feature to your Flutter app that fetches user profiles from a remote server. According to Clean Architecture, where should you place the code that converts JSON data into Dart objects?

hard

A. In the Presentation layer inside widgets

B. In the Domain layer as part of business logic

C. Directly inside the main.dart file

D. In the Data layer within model or mapper classes

Solution

1. Step 1: Identify JSON conversion responsibility

   Converting JSON to Dart objects is a data transformation task, part of data handling.

2. Step 2: Match task to Clean Architecture layer

   Data layer handles data sources and transformations, so JSON parsing belongs here.

3. Step 3: Exclude other layers

   Presentation is UI only, Domain is business rules, main.dart is app entry point, not for data parsing.

4. Final Answer:

   In the Data layer within model or mapper classes -> Option D

5. Quick Check:

   JSON parsing = Data layer [OK]

Hint: Put JSON parsing in Data layer models/mappers [OK]

Common Mistakes:

• Parsing JSON in UI widgets
• Putting parsing in Domain layer logic
• Adding parsing code in main.dart