Search Result for Event Buses

The data binding model and tools that google introduced leaves out something, namely how to updated when user changes text, etc. Seems to me that it might call for using some of the RXJava and RxAndroid Observables sugar to handle those cases and make the event bus more streamlined and handle more use cases.

Handler-based Eventbus for Android.

A simple way to bind and exchange messages between activities and services.

An eventbus library for android, simplifies communication between Activities, Fragments, Threads, Services, etc.

MicroBus is inspired by OttoBus, and it has its stronger and weaker points.

Advantages:

• It does not use annotations.
• It does not have a bug with sub-classes
• It has a very small size.

Disadvantages:

• This is a one-thread solution.
• Usage requires a little more code.

Simple events bus (publish–subscribe) implementation based on regular Android BroadcastReceivers mechanism.

A lightweight and simple event bus for Android.

• small footprint
• simple to use
• optimized for startup and event dispatching

Type-safe and thread-safe, one-to-many event bus in Java, optimized for speed and low-garbage on Android.

Otto is an event bus designed to decouple different parts of your app while still allowing them to communicate efficiently. Forked from Guava, Otto adds functionality to an already refined event bus as well as specializing it to the Android platform.