How sergioibz/task_manager_apex works
Project type and purpose
• Type: Mobile application (Flutter)
• Purpose: A task-manager app (“Task Manager Apex”) demonstrating Clean Architecture, offline/online data sync, dependency injection and state management.
File structure
• Top-level native folders:
• android/… → Android project, Gradle build scripts
• ios/… → iOS Xcode project, CocoaPods
• Flutter code under lib/:
• config/ → app bootstrap (MyApp), DI container (GetIt), navigation router, network clients, theme, error definitions
• features/ → split by domain: “countries” and “task”
– data → data-sources (Hive, REST/GraphQL), models, mappers, repository impl
– domain → entities, repository interfaces, use-cases
– presentation → Riverpod providers (StateNotifiers) and UI screens/widgets
• Other:
• main.dart → Hive init, DI registration, runApp
• pubspec.yaml → dependencies (Riverpod, GetIt, Dio, graphql_client, Hive, SharedPreferences, Freezed, Json Serializable)
Extract README insights
• Layers follow Clean Architecture (data, domain, presentation)
• DI: GetIt
• State: Riverpod + StateNotifier
• Local persistence: Hive + SharedPreferences (one-time flag)
• Remote sync: REST (Dio) + GraphQL
• Codegen: Freezed + json_serializable
• Blue rectangles for UI components
• Green for domain/use-cases
• Orange for data layer (data-sources, repositories)