Imagine event bus that does not require subscribe/unsubscribe, does not use reflection, does not use singletons. Just delivers messages when you need it.
A simple EventBus to handle activity result-like behaviors.
LiveBus is an event bus for Android which uses
LiveData component of the android architecture library to easily manage the lifecycles.
API 14+ LifecycleEvents library is an event bus implementation that works with the complexity O(1). It uses Lifecycle from android architecture components and Kotlin language features.
This is light-weight event bus dispatcher based on KOTLIN programming language.
EventListener is small library and is used for communication between classes like broadcast signals No Need to maintain listener reference. It auto work with app lifecycle.
A simple thread safe and tested event bus for JVM (1.7+) and Android apps built with RxJava 2.
Super lightweight (14 LOC) and minimalistic (post(), subscribe(), unsubscribe()) EventBus written with idiomatic Kotlin and RxJava 2.
NYBus - A pub-sub library for Android and Java applications.
Library for Event bus - implemented using RxJava2 in Android.
Simple Local Broadcast(s) on top of android
Android reactive event bus that simplifies communication between Presenters, Activities, Fragments, Threads, Services, etc.
Intents and easier than
AIDLs. IPC EventBus is an Android library for sending events between processes or different apps.
This library helps android developers to implement something like iOS key value observer pattern (KVO).
Demo for the EventBus library of GreenRobot.
RxJava2 EventBus that supports pausing and resuming. This way, you can achieve that the bus is queueing events while it is paused and emitting events while it is resumed which is a nice way to enforce that events are only observed, when for example your activity is resumed and your views are accessible.
The Universal Event Bus is an event dispatcher architecture which help you to use most common event bus implementation as Otto in a structured mode.
An events is a bus designed to separate different parts of the application, while still allowing them to communicate efficiently. The operation of the EventDispatcher is based on the publish-subscribe pattern: the bus asked a series of events that will be collected by those who joined them.
The publisher is, in this case, called Bus or RxBus and deals with post events using the Observable of RxJava. The event dispatcher contains two RxBuses: one dedicated to the UI thread, and the other for all the other events that have nothing to do with the UI (network calls, CRUD operations with the database etc.).
This is an event bus based on RxJava and optimized for Android.
Simpler to use and faster alternative to
itstimetoact - it's an android library, inspired by 'once', that can help you with planning events in your awesome application.
HermesEventBus is a library for using EventBus between processes, useful in IPC or plugin-in development. It has the same APIs as EventBus and easy to use.
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.