How josedev155/flutter_flickd_rest_app works
What this project is (type + purpose)
It is a single codebase deployed to Android, iOS, and Web (see android/, ios/, web/), with the core app in lib/ using a fairly standard layered structure:
• UI: pages/, widgets/
• State/coordination: controllers/
• Domain/data models: models/
• Networking/data access: services/
The key runtime relationships to show (what talks to what)
User Interaction
→ pages/main_page.dart + widgets/movie_tile.dart (presentation)
→ controllers/main_page_data_controller.dart (state + orchestration)
→ services/movie_service.dart (use-case/data service)
→ services/http_service.dart (HTTP client)
→ External Movie REST API (unknown provider; represent generically)
→ JSON responses
→ models/*.dart (parse/deserialize to Movie, MainPageData, etc.)
→ controller updates state
→ UI re-renders
Also show:
• lib/main.dart initializes app, loads AppConfig, routes to SplashPage then MainPage.
• Assets (assets/images) are read by UI widgets/pages (one-way dependency).
Entry / App Bootstrap
• main.dart
• depends on: pages/, models/app_config.dart
Controller / State Layer
• controllers/main_page_data_controller.dart
• depends on: services/movie_service.dart, models/main_page_data.dart, models/search_category.dart
Services / Data Access Layer
• services/movie_service.dart
• depends on: services/http_service.dart, models/movie.dart, models/search_category.dart
• services/http_service.dart
Domain Models
• models/movie.dart
• models/main_page_data.dart
• models/search_category.dart
• models/app_config.dart
Assets
• assets/images/* (consumed by pages/widgets)
• Movie REST API
• Endpoints (if known), auth (API key), response types
• pages/widgets → controller (not the other way)
• controller → movie_service → http_service → external API
• services → models (for serialization)
• UI → assets
Architectural patterns/design principles to highlight (based on structure)
Even without full code, the directory layout strongly suggests:
• Layered architecture (UI → controller → services → external API)
• Separation of concerns
• UI components in pages/ and widgets/
• Business/data orchestration in controllers/
• API access isolated in services/
• Data contracts in models/
render MainPage with list of MovieTile
UI event → controller → service → http → API → models → controller → UI
• main.dart
• pages/splash_page.dart
• pages/main_page.dart
• widgets/movie_tile.dart
• controllers/main_page_data_controller.dart
• services/movie_service.dart
• services/http_service.dart
• models/app_config.dart
• models/main_page_data.dart
• models/movie.dart
• models/search_category.dart
• assets/images
• External: Movie REST API
• Deployment shells: Android / iOS / Web