You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
16 lines
1.5 KiB
16 lines
1.5 KiB
% LTeX: language=en-US
|
|
|
|
%*******************************************************
|
|
% Abstract in English
|
|
%*******************************************************
|
|
\pdfbookmark[0]{Abstract}{Abstract}
|
|
|
|
|
|
\begin{otherlanguage}{american}
|
|
\chapter*{Abstract}
|
|
Flutter has multiple approaches in managing the state of an application. Flutter is a popular cross-platform framework for the development of applications for iOS, Android, Web, Windows, Linux and macOS. It offers the advantage to develop one codebase for multiple platforms at once resulting in reduced costs and complexity. Flutter uses a declarative UI that renders widgets based on a given state. The state management of a Flutter application is one of the most important parts of an application influencing the architecture and structure of an application.
|
|
|
|
This thesis describes multiple already existing approaches for state management in Flutter. The objective is to determine which approach is the most suitable approach for managing state in Flutter. In order to meet this objective, an evaluation will be carried out by evaluating the state management approaches setState, InheritedWidget, BLoC, Provider, Riverpod, Redux and MobX. An example application will be implemented for every approach. Those applications will be assessed by qualitative and quantitative criteria based on the requirements of state management systems for Flutter.
|
|
|
|
The result, in addition of the evaluation assessments, is also a recommendation which approach to use for a specific use case.
|
|
\end{otherlanguage}
|
|
|