How shrimqy/sekia works
Main Components
a. Mobile Application Architecture:
• Presentation Layer (UI)
• Main screens (Home, Devices, Settings, Sync)
• Compose UI components
• Domain Layer
• Use cases and business logic
• Repository interfaces
• Data Layer
• Repository implementations
• Local database
• Network services
b. Core Services:
• Network Service
• Notification Service
• Screen Mirror Service
• File Transfer Handler
• Media Handler
• Message Handler
c. External Connections:
• Windows PC Client (Seki)
• Network Communication (WebSocket)
• Network Service Discovery (mDNS)
┌─────────────────────────────────────────────────────────┐
• Presentation Layer │
• ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ │
• Home Screen │ │Device Screen│ │Settings etc.│ │
• ┘ └─────────────┘ └─────────────┘ │
• ┤
• Domain Layer │
• ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ │
• Use Cases │ │ Repository │ │ Models │ │
• Interfaces │ │ │ │
• ┘ └─────────────┘ └─────────────┘ │
• ┤
• Data Layer │
• ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ │
• Repository │ │ Database │ │ Network │ │
• Impl │ │ │ │ Services │ │
• ┘ └─────────────┘ └─────────────┘ │
• ┘
Connection Types
→ Data flow direction
⟷ Two-way communication
• - - Optional/conditional flow
Implementation Details
• Dependency injection points (Hilt/Dagger)
• Coroutine scope management
• Navigation graph structure
• Database schema
• WebSocket communication protocol
External Integration Points
• Windows PC client connection
• Network service discovery
• File system access
• Media control interface
• Notification listener service
Remember to:
• Notes for critical architectural decisions
• Document performance considerations
• Security checkpoints