When an Android app is split into isolated modules, direct dependencies between them quickly lead to circular dependency problems or O(n²) bridge module sprawl. The solution is a single shared communication layer — a passive, infrastructure-level module that acts as a reactive key-value store with named channels. Modules publish and subscribe to channels without knowing about each other. The layer supports three communication patterns: persistent state, one-time events, and point-to-point work. A key rule is that no module-specific types are allowed in the communication layer — values must be serialized payloads to avoid reintroducing coupling. The tradeoff is losing compile-time type safety across modules in exchange for true independence. The pattern works well for asynchronous, reactive communication but is a poor fit when strict delivery guarantees or synchronous coupling are required.
Sort: