> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/platform/guides/developer-guide/flutter-mobile-app-ui-developer-guide/introduction-to-flutter/flutter-architecture-and-approach.md).
# Flutter Architecture & Approach
At the core of Flutter's architecture is the Flutter engine, which is written in C++ and provides low-level rendering capabilities. The engine interfaces with the host operating system and handles tasks such as layout, drawing, and gesture recognition.
On top of the engine, Flutter provides a comprehensive UI toolkit that consists of widgets. Widgets are the building blocks of Flutter applications and represent different elements of the user interface.
Flutter's reactive framework allows widgets to rebuild efficiently when there are changes
Watch the video here to understand Flutter Architecture -
{% embed url="" %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.digit.org/platform/guides/developer-guide/flutter-mobile-app-ui-developer-guide/introduction-to-flutter/flutter-architecture-and-approach.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.