How adityabavadekar/messenger works
Project Type and Purpose
• This is an Android native, open-source real-time messaging application called “Wave Messenger.”
• It consists of two Gradle modules:
• “app”: the main Android application containing UI, controllers, services, and local persistence.
• “model”: a pure Kotlin module defining all data classes and domain models.
• It uses Firebase (Auth, Realtime Database, Cloud Storage, FCM), Room DB for offline caching, Android Jetpack (ViewModel, LiveData), SyncAdapters/ContentProvider, and various utility libraries.
File Structure
• Top-level: .github, CI/CD workflows, buildSrc for dependency/version management, app and model modules.
• app/src/main/java/com/adityaamolbavadekar/messenger: subdivided into
• ui (Activities/Fragments, ViewModels)
• database (Room entities, DAOs, Repositories, ViewModels)
• managers (AuthManager, CloudDatabaseManager, CloudStorageManager, FcmTokenManager, PrefsManager, InternetManager, etc.)
• services & sync (FcmService, AuthStateListenerService, SyncAdapter & ContentProvider)
• notifications (NotificationHelper, RetrofitInstance)
• account, contact, installation, dialogs, shortcuts, utils, views packages.
• model: Kotlin data classes mirror database records and remote data representations.
README Insights
• Confirms: no end-to-end encryption yet; under active development.
• Tech stack call-outs: Material Design, Room, libphonenumber, Firebase Auth/Messaging/Storage/RealtimeDB, Glide, Lottie, Jsoup, Kotlin.
Main Components
a. Android Application Module (“app”)
• Presentation Layer: Activities & Fragments
• ViewModel Layer: AndroidViewModel & Presenter classes
• Data Layer: Repositories that orchestrate Room database and CloudDatabaseManager
• Local Persistence: Room Database + DAOs + ContentProvider (for sync)
• Sync & Background Services: SyncAdapter, FcmService, AuthStateListenerService
• Notification Subsystem: FcmService → NotificationHelper → OS Notification API
• Utility & Helper classes (ClipboardUtil, EmojiUtils, LinkPreview, etc.)
• UI Components & Custom Views
b. Model Module (“model”)
• Domain/Data Models: MessageRecord, ConversationRecord, User, ReactionRecord, etc.
c. External Services
• Firebase Auth
• Firebase Realtime Database
• Firebase Cloud Storage
• Firebase Cloud Messaging (FCM)
• Google libphonenumber
d. Third-party Libraries
• Glide, Lottie, Jsoup, PhotoView, PinLog
Relationships and Data Flows
• UI → ViewModel: user actions (send message, open conversation)
• ViewModel → Repository: CRUD operations
• Repository → Room DB (local) & CloudDatabaseManager (remote sync)
• SyncAdapter/ContentProvider: periodic two-way sync between Room and Firebase RealtimeDB
• FcmService → NotificationHelper → OS → UI when messages arrive
• CloudStorageManager: file upload/download for attachments
• AuthManager → FirebaseAuth for login/logout flows
Architectural Patterns and Principles
• MVVM (Model-View-ViewModel) using AndroidViewModel
• Repository Pattern abstracting local vs. remote data sources
• Single Responsibility: each “Manager” or “Helper” focuses on one concern (auth, internet, prefs, links)
• Modularization: separation of domain models into a distinct model module
• Asynchronous data flow: LiveData / callbacks / Coroutine (presumed)