How neoapplications/neo-backup works
Main Components Identification
The system should be divided into these major components:
a) User Interface Layer:
• Activities (MainActivityX, ComposeSms)
• Pages (HomePage, AppPage, BatchPage, etc.)
• Compose UI Components (under ui/compose)
• Navigation System (under ui/navigation)
b) Business Logic Layer:
• ViewModels (MainVM, AppVM, BatchVM, etc.)
• Actions (BackupAppAction, RestoreAppAction, etc.)
• Handlers (BackendController, ShellHandler, etc.)
c) Data Layer:
• Databases (ODatabase, ScheduleDatabase, etc.)
• DAOs (AppInfoDao, BackupDao, etc.)
• Repositories (PackageRepository, ScheduleRepository, etc.)
d) System Integration Layer:
• Root Access Interface
• File System Operations
• Shell Commands
• System Services Integration
Key Workflows to Highlight
a) Backup Process:
UI -> ViewModel -> BackupAppAction -> ShellHandler -> Root Access -> File System
b) Restore Process:
UI -> ViewModel -> RestoreAppAction -> ShellHandler -> Root Access -> File System
c) Scheduling System:
ScheduleWork -> WorkHandler -> BackupAppAction -> NotificationHandler
Additional Elements
• Version compatibility notes
• Encryption/decryption workflow
• Scheduled backup system
• Components requiring root access
• Database schema relationships