What is this?
EventBus is a publish/subscribe event bus for Android and Java. It simplifies communication between components — Activities, Fragments, Threads, Services — and decouples event senders from receivers.
EventBus is a publish/subscribe event bus for Android and Java. It simplifies communication between components — Activities, Fragments, Threads, Services — and decouples event senders from receivers.So it's a library I add to my app, not a framework that takes it over?A library: the whole jar is tiny (~60k). You plug it into your existing Android or Java project wherever components need to talk to each other.
A library: the whole jar is tiny (~60k). You plug it into your existing Android or Java project wherever components need to talk to each other.How do I use it in my app?Three steps: define event classes; declare and annotate subscriber methods (optionally with a thread mode) and register/unregister them — on Android usually along the Activity or Fragment lifecycle; then post events.
Three steps: define event classes; declare and annotate subscriber methods (optionally with a thread mode) and register/unregister them — on Android usually along the Activity or Fragment lifecycle; then post events.How do I add it to my project?The README includes ready dependency snippets for Android and plain Java projects. If you use R8 or ProGuard, there is nothing extra to configure — the needed rules ship embedded.
The README includes ready dependency snippets for Android and plain Java projects. If you use R8 or ProGuard, there is nothing extra to configure — the needed rules ship embedded.Any gotchas to watch out for?Yes — the README strongly recommends using the EventBus annotation processor with its subscriber index, which avoids reflection-related problems seen in the wild.
Yes — the README strongly recommends using the EventBus annotation processor with its subscriber index, which avoids reflection-related problems seen in the wild.Why use an event bus instead of components calling each other directly?Direct wiring creates tight, error-prone dependencies and life cycle headaches. EventBus decouples senders from receivers, sidesteps those life cycle issues and keeps your code simpler.
Direct wiring creates tight, error-prone dependencies and life cycle headaches. EventBus decouples senders from receivers, sidesteps those life cycle issues and keeps your code simpler.What can it do beyond basic publish and subscribe?It has advanced features like delivery threads (subscriber methods can run on a thread mode you choose) and subscriber priorities, so you control how and in what order events are delivered.
It has advanced features like delivery threads (subscriber methods can run on a thread mode you choose) and subscriber priorities, so you control how and in what order events are delivered.Will it weigh down my app?The README bills it as fast, with solid performance across Activities, Fragments and background threads — and the whole thing is a ~60k jar.
The README bills it as fast, with solid performance across Activities, Fragments and background threads — and the whole thing is a ~60k jar.Is it proven in real apps?Yes — the README says it is proven in practice by apps with 1,000,000,000+ installs, and the project has been around since 2012.
Yes — the README says it is proven in practice by apps with 1,000,000,000+ installs, and the project has been around since 2012.What are similar projects?disruptor, butterknife, MaterialDrawer, SlidingMenu, glide, FlycoTabLayout, SmartRefreshLayout, Android-Universal-Image-Loader
disruptor, butterknife, MaterialDrawer, SlidingMenu, glide, FlycoTabLayout, SmartRefreshLayout, Android-Universal-Image-LoaderWhich topics is it in?events, asynchronous, pubsub, event-driven, android-development, jvm, android-library, lightweight, messaging, mobile-development, developers, java
events, asynchronous, pubsub, event-driven, android-development, jvm, android-library, lightweight, messaging, mobile-development, developers, java