How solvro/mobile-topwr works
Main System Components
a) Frontend Layer (Mobile App):
• Sub-components:
• UI Features (Home, Map, Buildings, Departments, etc.)
• State Management (Riverpod)
• Asset Management
• Internationalization
b) API Layer:
• GraphQL Client
• REST Clients (Dio)
• Cache Management System
c) Backend Services:
• Directus CMS
• iParking Service
• SKS API
• Digital Guide API
• Firebase Services
Component Relationships
a) Data Flow:
• User interactions → UI Components
• UI Components → State Management
• State Management → API Clients
• API Clients → External Services
• Cache System ↔ API Clients
b) Feature Dependencies:
• Related features:
• -related features (buildings, parking)
• Academic features (departments, science clubs)
• User services (notifications, analytics)
Key Architectural Patterns
a) Feature-First Architecture:
• How each feature is self-contained with:
• Presentation layer
• Business logic
• Data layer
• Repository pattern
b) State Management:
• Riverpod's role in:
• State management
• Dependency injection
• Cache control
Technical Implementation Details
a) Cross-Cutting Concerns:
• Authentication
• Offline support
• Caching strategy
• Error handling
b) Platform-Specific Elements:
• Containers for:
• Android-specific implementations
• iOS-specific implementations