How to set up the EventBus annotation processor in an Android project?

Add the annotation processor dependency in your build.gradle and enable it to avoid reflection-related issues; the README recommends this for improved performance and reliability in obfuscated code.

EventBus vs LiveData in Android – which is better?

EventBus is more flexible for decoupled communication across any components, while LiveData is lifecycle-aware and tied to UI updates. Choose EventBus for broader event handling, LiveData for ViewModel-to-UI data flow.

Why is my EventBus subscriber not receiving events?

Check if the subscriber is properly registered and unregistered, the event type matches the method parameter, and the thread mode is correct; common issues include missing registration or lifecycle mismatches.

Can EventBus be used in non-Android Java applications?

Yes, EventBus has a Java-specific version (eventbus-java) available on Maven Central, suitable for desktop or server-side applications requiring in-process event communication.

How to post events from a background thread to the main thread in EventBus?

Annotate your subscriber method with @Subscribe(threadMode = ThreadMode.MAIN), and EventBus will handle thread switching automatically when events are posted from any thread.

What are the ProGuard or R8 rules for EventBus?

EventBus ships with embedded rules, so no extra configuration is needed; it automatically preserves subscriber methods and event classes during obfuscation, as mentioned in the README.

How does EventBus handle event priorities and cancellation?

Use @Subscribe(priority = ...) to set subscriber priorities, and call EventBus.getDefault().cancelEventDelivery(event) to cancel further delivery, but this can break expected event flows if misused.

Open-Awesome

EventBus

Apache-2.0JavaV3.3.1

A publish/subscribe event bus for Android and Java that simplifies communication between components like Activities, Fragments, and threads.

Visit Website GitHub

24.7k stars4.6k forks0 contributors

What is EventBus?

EventBus is a publish/subscribe event bus library for Android and Java applications. It simplifies communication between different components like Activities, Fragments, Threads, and Services by decoupling senders and receivers, reducing boilerplate code and lifecycle-related errors.

Target Audience

Android and Java developers building applications that require efficient, decoupled communication between various components, especially in complex UI and background task scenarios.

Value Proposition

Developers choose EventBus for its simplicity, performance, and reliability—it replaces cumbersome callback patterns with a clean event-driven architecture, has a minimal footprint, and is proven in large-scale applications.

Overview

Event bus for Android and Java that simplifies communication between Activities, Fragments, Threads, Services, etc. Less code, better quality.

Use Cases

Best For

Decoupling Activities and Fragments in Android apps
Handling communication between background threads and the UI thread
Simplifying event-driven architectures in Java applications
Reducing boilerplate code for component interactions
Managing complex lifecycle dependencies in Android
Implementing clean, maintainable publish/subscribe patterns

Not Ideal For

Projects requiring strict compile-time type safety for event handling
Distributed systems or microservices needing cross-process event communication
Kotlin-centric applications that prefer coroutines and Flow for reactive streams
Large codebases where event traceability and debugging are critical

Pros & Cons

Pros

Decoupled Communication

Separates event senders from receivers, reducing complex dependencies and lifecycle issues in Android components like Activities and Fragments, as highlighted in the README.

Thread Mode Support

Allows specifying delivery threads via annotations, such as MAIN thread, ensuring safe UI updates from background operations, with documentation on thread modes.

High Performance

Optimized for speed with a minimal footprint (~60k jar), providing efficient event delivery with low overhead, as noted in the features.

Proven Scalability

Used in apps with over 1 billion installs, demonstrating reliability in large-scale production environments, a key selling point in the README.

Cons

Runtime Type Safety

Relies on runtime type checking for events, which can lead to ClassCastException if event types are mismatched, unlike compile-time enforced solutions, a limitation inherent in its design.

Reflection Overhead

Without the optional annotation processor, it uses reflection for subscriber discovery, potentially causing performance issues and problems with code obfuscation, as the README warns.

In-Process Limitation

Designed only for in-process communication, making it unsuitable for distributed architectures that require event streaming across processes, a gap compared to more advanced event systems.

Frequently Asked Questions

Related Projects

AutoMQ

Diskless Kafka® on S3. 10x Cost-Effective. No Cross-AZ Traffic Cost. Autoscale in seconds. Single-digit ms latency. Multi-AZ Availability.

Efficient reliable UDP unicast, UDP multicast, and IPC message transport

Stars8,846

Forks1,089

Last commit18 hours ago

JeroMQ

JeroMQ is a pure Java implementation of the ZeroMQ messaging library, offering high-performance asynchronous messaging for distributed or concurrent applications.

Stars2,451

Forks487

Last commit9 months ago

Smack

A modular and portable open source XMPP client library written in Java for Android and Java (SE) VMs

Stars2,415

Forks882

Last commit15 days ago

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub