How suwayomi/tachidesk-sorayomi works
Main Components
a. Client-Side Architecture (Flutter App):
• Presentation Layer
• Features modules (Library, Browse, Reader, Settings, etc.)
• Widgets and UI components
• Domain Layer
• Models and business logic
• Data Layer
• Repositories
• API clients
• Global State Management (Riverpod)
b. Server Integration:
• Tachidesk Server connection
• REST API communication
• Authentication handling
Key Architectural Elements
[Client Layer]
• UI Components (Flutter Widgets)
• Shell (Navigation)
• Manga Reader
• Library Manager
• Settings Interface
• Feature Modules
• Library
• Browse Center
• Manga Book
• Settings
• Quick Open
• State Management (Riverpod)
• Global Providers
• Feature-specific Controllers
• Data Layer
• Repositories
• API Client (Dio)
[External Integration]
• Tachidesk Server
• REST API Endpoints
• Authentication
• Manga Source Management
Important Relationships to Highlight
• Feature modules interact with state management through controllers
• Repositories communicate with external Tachidesk server
• UI components observe state changes through Riverpod
• Cross-platform compatibility layers
Technical Details
• Flutter/Dart as the primary framework
• Riverpod for state management
• Dio for HTTP client
• JSON serialization with freezed
• Local storage handling
• Platform-specific implementations (Android, iOS, Web, Desktop)
Implementation Notes
• How the feature-first folder structure maps to the architecture
• How global providers interact with feature-specific controllers
• Demonstrate the separation of concerns between layers