How schtroumphy/feedme works
Main Components
a. Presentation Layer:
• Jetpack Compose UI Components
• ViewModels (Command, Client, Product, Basket)
• UI States
• Navigation Components
b. Domain Layer:
• Use Cases (organized by feature)
• Domain Models
• Repository Interfaces
c. Data Layer:
• Local Storage (Room Database)
• Remote Services (Google Maps/Nominatim API)
• Repository Implementations
• Data Mappers
d. Core Module:
• Dependency Injection (Dagger-Hilt)
• Database Configuration
• Theme/Styling
• Common Extensions
┌─────────────────────────────────────────────────────────────┐
• Presentation Layer │
• ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ │
• Command │ │ Client │ │ Basket │ │
• Views │ │ Views │ │ Views │ │
• ┬───────┘ └─────┬───────┘ └─────┬───────┘ │
• ┌─────┴───────┐ ┌─────┴───────┐ ┌─────┴───────┐ │
• ViewModels │ │ ViewModels │ │ ViewModels │ │
• ┬───────┘ └─────┬───────┘ └─────┬───────┘ │
• ┼────────────────┼────────────────┼─────────────────┘
┌────────┼────────────────┼────────────────┼─────────────────┐
• Domain Layer│ │ │
• ┌─────┴───────┐ ┌─────┴───────┐ ┌─────┴───────┐ │
• Use Cases │ │ Use Cases │ │ Use Cases │ │
• ┬───────┘ └─────┬───────┘ └─────┬───────┘ │
• ┌─────┴───────┐ ┌─────┴───────┐ ┌─────┴───────┐ │
• Models │ │ Models │ │ Models │ │
• ┬───────┘ └─────┬───────┘ └─────┬───────┘ │
• ┼────────────────┼────────────────┼─────────────────┘
┌────────┼────────────────┼────────────────┼─────────────────┐
• Data Layer │ │ │
• ┌─────┴───────┐ ┌─────┴───────┐ ┌─────┴───────┐ │
• Repositories│ │ Repositories│ │ Repositories│ │
• ┬───────┘ └─────┬───────┘ └─────┬───────┘ │
• ┌───┴────┐ ┌───┴────┐ ┌───┴────┐ │
• Room │ │ APIs │ │Mappers │ │
• ┘ └────────┘ └────────┘ │
• ┘
Important Relationships
• Dependency flow (always pointing towards the domain layer)
• Data flow between layers
• Feature module boundaries
• Database relationships
• API integrations
Additional Elements
• Notes for key architectural decisions
• Dependency injection flow
• Clean Architecture boundaries
Implementation Details
• Related components with containers
• Version information and tech stack details
Remember to include the core module's relationship with all features and how it provides common functionality across the application.