This is an event bus designed to allowing your application to communicate efficiently.
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.
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:
Disadvantages:
Simple events bus (publish–subscribe) implementation based on regular Android BroadcastReceivers
mechanism.
A lightweight and simple event bus for 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.
Android optimized event bus that simplifies communication between Activities, Fragments, Threads, Services, etc. Less code, better quality.