How neoapplications/neo-store works
Main Components
a. Core Application Layer:
• Main Application (MainApplication.kt)
• Activity Container (NeoActivity.kt)
• Navigation System (ui/navigation/)
b. Feature Modules (arrange in a circular pattern around core):
• Pages Module (pages/)
• Explore, Latest, Installed, Search pages
• Preferences pages
• App details page
• Database Module (database/)
• Room Database (DatabaseX)
• DAOs for different entities
• Repository Management (index/)
• Repository Updater
• Index Parsers (v0 and v1)
• Installation System (installer/)
• Multiple installer implementations
• Installation event handling
c. Supporting Services:
• Worker Management (service/worker/)
• Download Worker
• Sync Worker
• Install Worker
• Exodus Worker
• Network Layer (network/)
• Downloader
• CoilDownloader
• ExodusRepo
• Installation processes (thick lines)
Component Relationships
• ViewModels (viewmodels/) connecting UI to data
• Database interactions with repositories
• Service worker connections to network and storage
• Installation flow from UI to system
External Integrations
Connections to:
• F-Droid Repositories
• Exodus Privacy
• Android Package Manager
• File System
Architectural Patterns
MVVM pattern used:
• UI Layer (pages/, components/)
• ViewModel Layer (viewmodels/)
• Model Layer (database/, entity/)
Notes
Annotations for:
• Privacy features
• Multi-language support
• Theme system
• Permission handling
• Clean architecture separation
• Modern Android development patterns
• Privacy-focused features
• Efficient repository management
• Multiple installation methods