How melihalkbk/flutter_guidance works
• Project Type & Purpose
– This is a full-featured Flutter educational app geared toward demonstrating best practices in Flutter UI development.
– It offers interactive examples, widget documentation, daily Flutter tips, and support for multiple platform targets.
• Main Components of the System
– UI Layers:
▪ “Pages” (various screens: home, login, register, quiz, profile, notifications, etc.)
▪ “Components” (reusable widgets like alert dialog, app bar, buttons, etc.)
– Business Logic:
▪ “Services” which contain authentication logic, widget-related services, and interactions with external backends (e.g., Firebase Auth, HTTP calls via Dio, web sockets).
– Data Layer:
▪ “Models” representing entities such as quiz questions and widget data.
▪ Data files and JSON assets (e.g., easy_questions, hard_questions, etc.).
– External Dependencies & Third-Party Integrations:
▪ Firebase services (authentication, messaging, firestore if applicable)
▪ URL launcher, Dio for network operations
▪ Shared preferences and Hive for local data storage
▪ Other Flutter packages (video_player, fluttertoast, etc.)
• Relationships & Data Flow
– Show dependency between “Pages” and “Components” for assembling the user interface.
• Architectural Patterns & Design Principles
– Highlight the Clean Architecture pattern: Separate layers for UI (presentation), business logic (services or domain), and data (models and repositories).
– Illustrate modularization; you might have a distinct module for widget examples, another for authentication, etc.
– Emphasize maintainability and testability by marking unit & widget test components (present in the “test” directory).
• Technology Stack & Frameworks
– Flutter & Dart (primary dev tools)
– Firebase (for backend/authentication/messaging)
– Dio & WebSocket for network interactions
– SharedPreferences & Hive for local storage