How brayanalmengor04/saborpty-app works
Project type and purpose
• This is a cross-platform mobile (and desktop/web) application built in Flutter/Dart.
• Purpose: “SaborPTY” is a recipe app for Panamanian dishes, built with a modular, feature-driven, clean-architecture approach.
• It uses Material Design 3 for UI, Riverpod/Provider/BLoC for state management, Hive & SharedPreferences for local persistence, and integrates (or is ready to integrate) with Firebase and a Laravel backend.
File structure
• Top-level targets: android/, ios/, web/, linux/, macos/, windows/ — each platform shell generated by Flutter.
• Core Flutter code under lib/:
• core/: global constants, errors, services, utils
• features/: feature modules (auth, category, home, recipes, favorites, suggestion) each following data/domain/presentation substructure
• shared/: reusable widgets, theme definitions, navigation (go_router)
• main.dart: app entry, routes initialization
• pubspec.*: dependencies declaration (Flutter, Riverpod, Hive, Firebase, etc.)
• Android/iOS/CMake files: native configuration and plugin registration.
README for additional insights
• The README explicitly outlines the clean-architecture layering (core, features, shared), the intended feature set (categories, search, favorites), and the tech stack (Flutter + Dart + Material Design 3 + Riverpod/Provider/BLoC + Hive + Firebase + Laravel).
Detailed breakdown of components
• Flutter Shell (per platform)
• Main entrypoint: main.dart → AppRouter (go_router)
• Shared layer: ThemeManager, NavigationService, reusable Widgets
• Feature “recipes”: Presentation (RecipeListScreen), ViewModel/BLoC, Domain (RecipesUseCases + Entities), Data (RecipeModel, RecipeDataSource)
• Remote: REST client (Laravel), Firebase module (if used)
• Error handling: core/errors
• Utility services: core/services (connectivity, notifications)