How projetogestaoinsumos/front_insumos works
Project type and purpose
• This is a Flutter-based, multi‐platform front-end application called “Front-Insumos.”
• It targets Android, iOS, web, Linux, macOS and Windows via the standard Flutter project directories.
• There is no in-repo backend: all data comes from an external API (lib/api/api_service.dart).
File structure
• Top-level platform folders: android/, ios/, linux/, macos/, windows/, web/ – each holds the native shell and Flutter integration code.
• lib/ contains the Dart application code:
• main.dart – app entry point
• components/ – reusable UI widgets
• screens/ – page widgets (login, home, items)
• state/ – BLoC(s) for state management (auth_bloc.dart)
• api/ – API service for HTTP calls (api_service.dart)
• models/ – domain data models (user.dart)
• Configuration and build files: pubspec.yaml, analysis_options.yaml, platform build scripts (Gradle, Xcode, CMake).
Readme insights
• Very brief: confirms this is the front-end (“Front-Insumos”).
• No further architecture docs included, so we must infer the layered architecture from code organization.
Final advice
• Platform-level code as one group, emphasizing reuse of the single Flutter codebase.
• Don’t worry about every single file—group by function (e.g., “Components”, “Screens”, “State Management”).