How nextcloud/android works
Project type and purpose
• It’s a monolithic Android client app for Nextcloud (mobile front‑end)
• Written in Kotlin/Java with Gradle, Dagger (DI), Room (local DB), WorkManager, ExoPlayer, AIDL (SSO), Compose, traditional Activities/Fragments
Main components
A. UI Layer
– Activities, Fragments, Compose screens
– ViewModels (Android Architecture Components)
B. Domain/Business Logic
– Use‑cases (e.g. GeneratePDFUseCase, FileLockingHelper)
– AsyncRunner/Task abstractions
C. Data Layer (Repository Pattern)
– Repositories (ClientRepository, OfflineOperationsRepository, AssistantRepository, etc.)
– Local DataSource: Room database (NextcloudDatabase + DAOs + Entities + Migrations)
– Remote DataSource: Nextcloud Server API (ClientFactory → HTTP client modules)
D. Background & Services
– WorkManager jobs (SyncWork, BackupWork, OfflineOperationsWorker, FileUploadWorker, etc.)
– Foreground/Bound services (PlayerService, PowerManagementService, ConnectivityServiceImpl)
– AIDL SSO service for streaming remote content
E. External/Device Integrations
– Nextcloud server (HTTPS REST APIs)
– Firebase Messaging or Huawei Push (in gplay/huawei flavors)
– Camera/File storage (document scan, media playback, downloads)
– Local notifications (NotificationManager)
Relationships and data flows
• User taps UI → ViewModel → Repository
• Repository decides:
– Query Room DB (DAO) → returns LiveData/Flow
– Or call HTTP client → parse JSON → write to DB
• Background sync: WorkManager schedules jobs → executes OfflineSyncWork → uses Repository → updates DB
• Push arrives → Firebase/HMS → triggers BroadcastReceiver → enqueues WorkManager task
• AIDL SSO: UI binds to InputStreamService → streams content from server
• Media playback: UI → PlayerService → ExoPlayer → streams remote URLs
Architectural patterns & principles
• MVVM (UI ↔ ViewModel ↔ Repository)
• Repository pattern + data sources
• Dependency Injection (Dagger modules in /di)
• Single source of truth: Room DB
• Reactive UI: LiveData/Flow
• Background processing: WorkManager
• Flavor‑based configuration: generic, gplay, huawei, debug, qa, release