BEST PRACTICE ARCHITECTURE AND STATE MANAGEMENT IN FLUTTER APPLICATIONS

2024

Closed access Metadata (CSL-JSON)
DOI 10.54251/2616-6429.2024.03.08nu
Data confidence 70 medium
How this score is calculated

It is built from checkable properties of the record itself: whether the article has a DOI, how many independent sources confirmed its data, whether the required fields are filled in, and how recent the latest confirmation is. Disagreement between sources and a missing identifier lower it. A value of 80 or above means the record was published without further checking; 60 to 79 means it is published at reduced confidence, with a manual check advisable. A record verified by an editor by hand is never pushed below 90 by a recalculation. This scores our data about the article, not the article itself.

Abstract

In the rapidly evolving landscape of mobile application development, Flutter has emerged as a robust framework for creating high-performance, cross-platform apps. This article explores best practices in architecture and state management within Flutter applications, with a particular focus on developing educational tools for Kazakh children to learn about their cultural heritage. We delve into architectural patterns that enhance code maintainability and scalability, such as MVVM and Clean Architecture. Additionally, we examine various state management solutions, including Provider, Bloc and Riverpod, comparing their strengths and use cases. The study highlights the collaborative efforts of the development team, demonstrating how effective teamwork and role allocation can lead to the successful implementation of a portable and user-friendly application. By eliminating the existing gap in educational resources adapted for children, this Flutter-based application offers a free and accessible platform for learning Kazakh traditions.