How redsolution/xabber-android works
Project type and purpose
• A native Android mobile application (XMPP client)
• Written in Java (Android SDK), built with Gradle, supporting multiple product flavors (open, store, vip)
• Implements an MVP presentation layer, a data/business layer, persistence (SQLite + Realm), network layers (XMPP via Smack, HTTP via Retrofit), background Android services, and integrates 3rd-party submodules (MemorizingTrustManager, emojicon)
A. Presentation Layer (UI & MVP)
– Activities / Fragments (com.xabber.android.ui.*)
– View interfaces & Presenter classes (com.xabber.android.presentation.mvp.*)
B. Domain & Data Layer
– Managers (AccountManager, ConnectionManager, MessageManager, etc.)
– Extension managers (CapsManager, CarbonManager, FileManager, OTRManager, etc.)
– Business events & callbacks (OnInitializedListener, OnPacketListener, NewMessageEvent)
C. Persistence Layer
– SQLite tables (classes in data.database.sqlite)
– Realm models (data.database.messagerealm & io.realm)
– DatabaseManager façade
D. Network Layer
– XMPP stack (Smack: XMPPTCPConnection, PacketExtension, ProviderUtils)
– HTTP APIs (Retrofit/OkHttp clients in data.http: CrowdfundingClient, PushApiClient, XabberComClient)
– Custom trust management (MemorizingTrustManager submodule)
E. Background Services
– XabberService (foreground service for persistent connection)
– DownloadService / UploadService (file transfer)
– PushService (in open/store flavors)
F. Build & Flavor configuration
– Gradle productFlavors “open”, “store”, “vip”
– Submodule: MemorizingTrustManager
– Scripts (crowdin.bash for translation updates)
External Systems & Services
– XMPP servers (any XMPP domain)
– Xabber.com HTTP API (xaccount, Patreon endpoints)
– Crowdfunding / Patreon servers
– Crowdin (localization pipeline)
– Google Play / F-Droid (app distribution)
Relationships & Data Flows
• UI → Presenter: user actions (send message, change account settings)
• Presenter → Manager: invokes business logic (AccountManager.createAccount(), MessageManager.send())
• Manager → Network: XMPP layer (via ConnectionBuilder & XMPPTCPConnection) or Retrofit HTTP client
• Network → Manager → UI: incoming XMPP stanzas generate events (OnPacketListener → MessageUpdateEvent → Presenter)
• Manager → Persistence: store/retrieve chat history & settings (DatabaseManager → SQLite/Realm)
• Services → Manager/UI: background reconnection, push notification dispatch
• Build scripts → Flavor modules: include/exclude PushService keys, resource overlays for “vip” gold theme
Architectural patterns & design principles
– Layered architecture (Presentation → Domain → Persistence → Network)
– MVP in UI layer for separation of concerns
– Observer / Listener patterns for event dispatch
– Façades (DatabaseManager, NetworkManager) to abstract low‐level details
– Dependency injection implied by Manager interfaces (e.g., BaseManagerInterface)
– Product Flavor isolation (open vs. store vs. vip code paths)