IssueTracker

Hello Google Android Team,

I am writing as an Android developer to express my deep concern regarding the deprecation of LocalBroadcastManager.

I am a university student from Korea studying Android development. LocalBroadcastManager has been a valuable tool for safely handling application-wide events. While I understand the official documentation's point about the potential inappropriateness of event bus patterns that violate application layers, I believe that the continued allowance of broadcast receivers with the Not Exported declaration indicates that the Android team does not strongly oppose this pattern.

Deprecating LocalBroadcastManager without providing a suitable alternative for safely handling application-wide events seems counterproductive. The suggested alternative of using stream-based variables is inadequate compared to the traditional broadcast approach for several reasons:

Increased Complexity: Stream-based variables introduce more complexity in both implementation and maintenance. Developers might find themselves spending more time handling simple event processing tasks.

Performance Issues: Stream-based variables might be less efficient in handling application-wide events, especially when events occur frequently. This could lead to overall performance degradation of the application.

Compatibility Problems: Many existing applications still rely on LocalBroadcastManager. Transitioning all of these to stream-based variables requires significant resources and time, and could introduce compatibility issues during the process.

Considering these points, I urge you to reconsider the decision to deprecate LocalBroadcastManager. This tool remains highly useful to many developers, and providing a safe and efficient way to handle application-wide events would be greatly appreciated.

Thank you for your attention to this matter.