Flutter Implementation with Clean Architecture and BLoC Pattern

Design the complete architecture for a Flutter app called [APP NAME], a [APP TYPE] with [NUMBER] main screens/features.\\\\\\\\n\\\\\\\\n**Context:**\\\\\\\\n- Team: [NUMBER] Flutter developers\\\\\\\\n- Complexity: [NUMBER] screens, [NUMBER] APIs, [NUMBER] offline features\\\\\\\\n- Backend: [API DESCRIPTION]\\\\\\\\n- Target platforms: iOS + Android [+ Web]\\\\\\\\n\\\\\\\\n**1) Clean Architecture — Layers:**\\\\\\\\n\\\\\\\\n\\\\\\\\\\\\\\\\\\\\\\\`\\\\\\\\\\\\\\\\\\\\\\\`\\\\\\\\\\\\\\\\\\\\\\\`\\\\\\\\nlib/\\\\\\\\n├── core/                    # Shared across features\\\\\\\\n│   ├── error/               # Failure classes, exceptions\\\\\\\\n│   ├── network/             # API client, interceptors\\\\\\\\n│   ├── usecases/            # Base UseCase class\\\\\\\\n│   └── theme/               # AppTheme, colors, typography\\\\\\\\n├── features/\\\\\\\\n│   └── [feature_name]/\\\\\\\\n│       ├── data/\\\\\\\\n│       │   ├── datasources/  # Remote + Local data sources\\\\\\\\n│       │   ├── models/       # JSON serialization (fromJson/toJson)\\\\\\\\n│       │   └── repositories/ # Repository implementation\\\\\\\\n│       ├── domain/\\\\\\\\n│       │   ├── entities/     # Business objects (pure Dart)\\\\\\\\n│       │   ├── repositories/ # Repository contracts (abstract)\\\\\\\\n│       │   └── usecases/     # Business logic\\\\\\\\n│       └── presentation/\\\\\\\\n│           ├── bloc/         # BLoC + Events + States\\\\\\\\n│           ├── pages/        # Full screens\\\\\\\\n│           └── widgets/      # Feature-specific widgets\\\\\\\\n└── injection_container.dart  # GetIt DI setup\\\\\\\\n\\\\\\\\\\\\\\\\\\\\\\\`\\\\\\\\\\\\\\\\\\\\\\\`\\\\\\\\\\\\\\\\\\\\\\\`\\\\\\\\n\\\\\\\\n**2) BLoC Pattern in Detail:**\\\\\\\\n- For [MAIN FEATURE], create:\\\\\\\\n  - Events: all possible user actions\\\\\\\\n  - States: all possible screen states (initial, loading, loaded, error)\\\\\\\\n  - BLoC: event → state transformation logic\\\\\\\\n  - Unit tests for BLoC (bloc_test package)\\\\\\\\n- Cubit vs. BLoC: when to use each\\\\\\\\n- BlocObserver for global logging\\\\\\\\n- MultiBlocProvider at app root\\\\\\\\n\\\\\\\\n**3) Dependency Injection (GetIt):**\\\\\\\\n- Singleton registration (API client, database)\\\\\\\\n- Factory registration (BLoCs, UseCases)\\\\\\\\n- Lazy vs. eager initialization\\\\\\\\n- Feature-based modules for organization\\\\\\\\n\\\\\\\\n**4) Networking:**\\\\\\\\n- Dio with interceptors (auth, logging, error handling)\\\\\\\\n- Retrofit for API code generation\\\\\\\\n- Unified error model with Either (dartz/fpdart)\\\\\\\\n- Connectivity check before requests\\\\\\\\n\\\\\\\\n**5) Navigation:**\\\\\\\\n- GoRouter (declarative) with typed routes\\\\\\\\n- Guards for authentication\\\\\\\\n- Deep linking\\\\\\\\n- Nested navigation (shell routes)\\\\\\\\n\\\\\\\\n**6) Testing:**\\\\\\\\n- Unit tests: BLoCs, UseCases, Repositories\\\\\\\\n- Widget tests: isolated components\\\\\\\\n- Integration tests: complete flows\\\\\\\\n- Mocking with Mocktail\\\\\\\\n- Coverage target: > [%]\\\\\\\\n\\\\\\\\n**7) CI/CD:**\\\\\\\\n- GitHub Actions: analyze, test, build\\\\\\\\n- Fastlane for App Store/Play Store deployment\\\\\\\\n- Flavor configuration (dev, staging, prod)\\\\\\\\n- Code generation: build_runner, freezed, json_serializable\\\\\\\\n\\\\\\\\nInclude complete code for [MAIN FEATURE] following all architecture layers.