How to use Flutter vs Flask for clean architecture

Introduction

Clean architecture revolves around converting the existing architecture into loosely coupled layers.

This saves time and is future-proof. Although not easy to explain, any architecture can be called a clean architecture if it decouples the layers. Some of the examples may include:

• Hexagonal architecture
• Oriented software
• Onion architecture
• Screaming architecture
• DCI
• BCI

The dependency rule

One more thing to remember is the dependency rule. It is related to the information isolation, meaning every inside layer must not know anything about the outside rule, as illustrated in the image below:

Note: The inside layers do not depend on the outside layers, but the reverse is true.

Note: There are other rules too, but the dependency rule must always apply to have a clean architecture.

Flutter with clean architecture

For Flutter, these layers are usually divided into four categories:

• Domain layer
• Application layer
• Data layer
• Device layer

The project hierarchy may look like the code below:

Note: This hierarchy may vary from project to project but should essentially consist of such layers.

Flask with clean architecture

The layers for Flask are usually divided into the following layers:

• Application layer
• Configuration layer
• Core layer
• Extension layer
• Infra layer
• Test layer