Here is the problem statement that EventBus solves in a nutshell: “I want an easy, centralized way to notify code that’s interested in specific types of events when those events occur without any direct coupling between the code that publishes an event and the code that receives it.” When you say “the business logic for … Read more
The following is what I see as benefits of using reactive event streams in a single-threaded synchronous application. 1. More declarative, less side-effects and less mutable state. Event streams are capable of encapsulating logic and state, potentially leaving your code without side-effects and mutable variables. Consider an application that counts button clicks and displays the … Read more
Please ensure these lines are in your proguard config file if you are using proguard for your builds. -keepattributes *Annotation* -keepclassmembers class ** { @org.greenrobot.eventbus.Subscribe <methods>; } -keep enum org.greenrobot.eventbus.ThreadMode { *; }
The event bus and Otto are not “recommended ways” by the Android developer guide primarily because they are third party libraries to simplify the task. And I believe Otto is fairly new, so older guides obviously aren’t using it. I personally like Otto, it’s what I use and I haven’t had any problems with it … Read more
EventBus and RxJava are different in their nature. EventBus is just a bus as the name suggest – it provides the mechanism to subscribe and publish events to the “bus”, without you caring how the wiring is done, what this “bus” actually is, etc. In the context of Android, the EventBus is just an easier … Read more