Flutter architecture can be discussed from two main perspectives.

The layered architectural model of the Flutter framework.

➔ Embedder: This is the lowest level of the Flutter layered architecture. It is platform specific and it provides entry point support for the host operating system. It coordinates with the OS to manage the application lifecycle.

➔ Engine: This is responsible for rasterizing or drawing the UI on the device screen. It is platform agnostic and runs the Dart runtime environment.

➔ Framework: This layer provides support to developers by providing rich libraries such as foundation classes for animations and gestures, widgets. The framework also provides the Materials and Cupertino libraries that implement a wide range of widgets for Google's Material Design and Apple's iOS design.

App architecture pattern for the application.

➔ UI Layer: This layer is responsible for displaying data to the user and handling user interaction

➔ Domain Layer (Optional): This is an optional layer. It can contain independent business rules, reusable code, or components.

➔ Data Layer: This layer is the source of application data, and handles business logic and interactions with the data source.