> 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/state-management-with-provider-and-bloc.md).

# State Management With Provider & Bloc

Different types of state management in Flutter with Provider and Bloc

Two popular state management approaches in Flutter are Provider and BLoC (Business Logic component). This documentation provides an overview of these state management techniques, their key concepts, and how to implement them in Flutter applications.

* **Provider**: [A simplified State Management Solution](/platform/guides/developer-guide/flutter-mobile-app-ui-developer-guide/state-management-with-provider-and-bloc/provider-state-management.md)
* **BLoC** [(Business Logic Component) Pattern](/platform/guides/developer-guide/flutter-mobile-app-ui-developer-guide/state-management-with-provider-and-bloc/bloc-state-management.md)

State management involves managing and updating the data and UI state within a Flutter application. It helps handle dynamic data, respond to user interactions, and keep the user interface synchronized with the underlying data.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.digit.org/platform/guides/developer-guide/flutter-mobile-app-ui-developer-guide/state-management-with-provider-and-bloc.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.