How charlie-shub/world_on_client works
Main Architectural Components
a) Presentation Layer (Views)
• Main UI components from /lib/views/
• By features (authentication, profile, experience_management, etc.)
b) Application Layer (BLoCs)
• Below the presentation layer
• The BLoC components from /lib/application/
• By feature matching the views
c) Domain Layer
• In the center
• Entities, value objects, and interfaces from /lib/domain/
• Core business logic and validation rules
d) Infrastructure Layer
• At the bottom
• Repositories and data sources from /lib/data/
• External service integrations (Firebase, Google services)
Key Relationships to Highlight
• Dependency flow (following Clean Architecture)
• Data flow between layers
• Event/State management patterns
• Repository implementations
• External service interactions
Component Groups
Related components into bounded contexts:
• Authentication & User Management
• Experience Management
• Navigation & Maps
• Social Features (comments, sharing)
• Store & Purchases
• Notifications
• Search & Discovery
Technical Details
Specific implementations of:
• Firebase integration
• BLoC pattern implementation
• Repository pattern
• Clean Architecture boundaries
• Dependency injection setup
• Testing architecture
Cross-Cutting Concerns
Shared components:
• Core utilities
• Validation logic
• Common widgets
• Error handling
• Authentication state
External Dependencies
Integration points with:
• Firebase services
• Google services
• Local storage
• Location services
• Payment processing
• Clean Architecture layers
• Feature modularity
• Data flow directions
• State management
• Error handling paths
• Authentication flow
• Domain model relationships