How team-aipaca/aipaca_app works
Main Architecture Components
a) Presentation Layer (UI)
• MVVM pattern implementation with:
• Views (Views folder)
• ViewModels (ViewModels folder)
• Models (Models folder)
• AppShell as the navigation container
b) Core Services Layer
• Database Service (Data/DatabaseService.cs)
• API Configuration (Data/ApiConfigManager.cs)
• Resource Management (Localization, Configurations)
c) Platform-Specific Layer
• Android
• iOS
• MacCatalyst
• Windows
• Tizen
Component Relationships
a) Data Flow
• ViewModels ↔ Models
• ViewModels ↔ Services
• Services ↔ External API
• Database Service ↔ Local Storage
b) Navigation Flow
• AppShell ↔ Main Pages
• Pages ↔ Popups
Specific Implementation Details
Create sections for:
a) Feature Modules
• Account Management (Views/Account)
• Settings Management (Views/Settings)
• Challenge System
• Robot Interface
• Record Tracking
b) Cross-Cutting Concerns
• Localization (Resources/Localization)
• Configuration Management
• Converters
┌─────────────────────────────────────────┐
• UI Layer │
• (Views, ViewModels, XAML Components) │
• ┤
• Business Logic Layer │
• (Services, Models, Configuration) │
• ┤
• Cross-Platform Layer │
• (.NET MAUI Framework Components) │
• ┤
• Platform-Specific Layer │
• (Android, iOS, Windows, macOS, Tizen) │
• ┘
Important Details
• MVVM binding relationships
• Multi-language support system
• API configuration flow
• Demonstrate the database interaction pattern
• Platform-specific implementation points