How zainulabdn/learning works
Project type and purpose
• This repo is not an application codebase but a learning roadmap for Flutter & Dart developers.
• It’s organized as a sequence of practicals grouped by topic (Material UI, Navigation, Networking, State Management, Local Storage, Streams, Firestore, SOLID Principles).
• Its purpose is to guide a learner through progressively advanced Flutter concepts via hands-on exercises.
File structure
• There is only one top-level file: README.md, which contains the entire curriculum.
• No source code or subdirectories exist; the structure is purely conceptual.
• All “components” of the system are the thematic modules and their dependencies on one another.
README for additional insights
• The table of contents lists 29 practical modules grouped under major topics.
• Each topic introduces a set of exercises that build on core Flutter/Dart concepts and external services (APIs, Firebase).
• Repeated reference to architectural patterns (MVVM, Provider, Riverpod, BLoC, DI) and technologies.
Main components
a. Curriculum Shell – the root “system.”
b. Topic Modules – Material Components, Navigation & Routing, Networking, State Management, Local Storage, Streams, Firestore Database, SOLID Principles.
c. Practicals – numbered exercises under each module.
d. Technologies & Patterns – Flutter UI (Material 3), Dart, MVVM, Provider, Riverpod, flutter_bloc, injectable/getIt, HTTP/dio, SQLite, Firebase Auth/Firestore, Streams.
e. External Services & APIs – JSONPlaceholder, Yummly, TheCocktailDB, NewsAPI, Firebase, dummyjson, dictionary API, funtranslations API.
f. Learner – the end-consumer interacting with exercises.
Relationships and interactions
• Curriculum Shell → contains Topic Modules.
• Each Topic Module → links to a set of Practicals.
• Practicals → depend on specific Technologies & Patterns and often call External Services & APIs.
• State Management and Dependency Injection patterns cross-cut multiple modules (Networking, Local Storage, Firestore).
Architectural patterns & design principles
• Layered Approach:
• UI (Flutter widgets)
• State Management (ViewModel classes via Provider/Riverpod/BLoC)
• Data Layer:
– Remote (HTTP/dio → APIs)
– Local (SQLite, Firestore)
• Dependency Injection (injectable/getIt)
• MVVM is the recommended presentation architecture.
• SOLID principles emphasized at the end.
Elements
• Clear labels: name each module, practical, technology, and external service.
• Learner’s path from module to module.
• Dependencies from practicals to technologies and APIs.
Final advice
• Every major topic as its own component.
• How each practical exercise pulls in specific technologies and services.
• Keep the learner’s journey visible, from Material UI basics through advanced Streams and Firestore.