How oolaapleur/yggert-nu works
Main Components
a. Frontend Layer:
• Flutter UI Components (screens, widgets)
• BLoC Pattern Components (for state management)
• Theme Management
• Internationalization (l10n)
b. Core Business Layer:
• Domain Logic
• Use Cases
• Repositories
• Data Models
c. Data Layer:
• API Providers
• Local Storage
• GTFS Data Operations
• Device Settings
d. External Services:
• Google Authentication
• Mobility Services APIs (Bolt, Hoog, Tuul)
• Public Transport APIs
• Services
┌─ Presentation Layer ─────────────────────────┐
• Home Screen │
• Map Screen │
• Settings Screen │
• Intro Screen │
• ┬───────────────────────────┘
• ↓
┌─ Business Logic Layer ────────────────────────┐
• ┌─ BLoCs ─────┐ ┌─ Use Cases ──────────┐ │
• Map Bloc │ │ - Filter Trips │ │
• Auth Bloc │ │ - Get Calendar │ │
• Theme Bloc│ │ - User Authentication│ │
• ┘ └──────────────────────── │
• ┬────────────────────────────┘
• ↓
┌─ Data Layer ──────────────────────────────────┐
• ┌─ Repositories ─┐ ┌─ Data Sources ────────┐ │
• Vehicle │ │ - GTFS Operations │ │
• Settings │ │ - API Providers │ │
• User │ │ - Local Storage │ │
• ┘ └─────────────────────────│ │
• ┬────────────────────────────┘
• ↓
┌─ External Services ──────────────────────────┐
• Google Auth │
• Mobility APIs (Bolt, Hoog, Tuul) │
• Public Transport APIs │
• Map Services │
• ┘
Important Details
• How user interactions flow through the layers
• API calls to external services
b. Component Relationships:
• BLoC to UI connections
• Repository to API provider relationships
• Authentication flow paths
c. Cross-Cutting Concerns:
• Internationalization
• Theme Management
• Error Handling
• Network Status Monitoring
Notes
• Clear separation between development and production flavors
• Where environment-specific configurations are applied
• Integration test boundaries