How devendroid/trainiings_app works
Project Type and Purpose
• This is a cross-platform mobile application built with Flutter. It follows a layered architecture (presentation, domain, data) and demonstrates the BLoC pattern, dependency injection via get_it, theming, routing, and mock data repositories. Its purpose is to display “trainings” with lists, highlights, filters, and details using Flutter widgets on both Android and iOS.
File Structure Analysis
• Top-level mobile targets:
• android/ – Gradle build, manifests, Kotlin MainActivity, resources
• ios/ – Xcode project, Swift/AppDelegate, storyboards, asset catalogs
• Shared Dart code under lib/:
• main.dart – app entry point, DI setup, MaterialApp/router
• routing/ – route_name.dart, router.dart (navigation management)
• core/ – datasource (mock), di (service locator), theme, utils
• features/
– shared/ – reusable widgets and modal classes
– trainings/ – domain (usecases, repository interface), data (mock datasource, repository impl), presentation (bloc/cubit, UI screens, widgets)
• Configuration and metadata: pubspec.yaml, analysis_options.yaml, assets/, media/, test/
Insights from README
• Explicit description of the three-layered structure:
• data: “Mock API or training repository”
• domain: “Usecases containing business logic”
• presentation: “BLoC logic for state management” + Flutter UI
• Lists external dependencies: flutter_bloc, equatable, get_it, carousel_slider, modal_bottom_sheet