How shaunm1724/geniebox works
Project type and purpose
• This is a cross‑platform Flutter client application (“geniebox”) targeting mobile (iOS, Android), desktop (Windows, macOS, Linux) and web.
• Its purpose is to present multiple “features” (home, email reply, recipe creator, story/poem, weather), each implemented in its own module, and to fetch or generate data via external services (e.g., a Gemini AI service, a weather API).
File structure
• Top‑level folders:
– android, ios, linux, macos, windows, web: native embedding projects and build files for each platform.
– lib: main Dart code—subdivided into core (shared services, constants, themes) and features (UI + state management per feature).
– test: widget tests
• “lib/core” holds application constants, theme definitions, and service abstractions (gemini_service.dart, weather_service.dart).
• “lib/features” follows a feature‑driven, presentation‑layer approach: each feature has its pages, providers (state management), widgets, and—where needed—data models.
• pubspec.yaml / pubspec.lock list dependencies.
• No separate backend or database—data comes from external APIs.
Extract additional insights from README
• Assumes standard Flutter build and run flow.
Detail
• Every major feature module (email_reply, recipe, story_poem, weather) as sub‑components under UI and State Management.
• Shared core services being injected or referenced by multiple providers.
• Don’t abstract away the platform folders—show how they tie into the Flutter engine.