Eventbus V3
summary
EventBus V3 replaces naming conventions with annotation-based subscription, moves heavy work to compile-time indexing and code generation, and benchmarks show registration becomes several times faster (Nexus One/5/9 tests). The annotation processor has limits: anonymous subscribers are invisible and subscriber/event classes must be public, so V3 uses a hybrid fallback to reflection when indexing can’t cover cases. Add the annotation-processor dependency only in apps (not libraries); V3 is available now and requires a build-time provider.
AI-written summary · about
chapters (13)
- 0:00Start
- 0:30Android without EventBus
- 0:55EventBus Communication
- 2:13EventBus: Top Selling Points
- 3:09EventBus 2 Adoption
- 4:19Example Annotations
- 6:04The Journey to EventBus 3: Community
- 6:39The Journey to EventBus 3: Tweaking
- 7:58Annotation Processor Caveats
- 10:13State of EventBus 3
- 10:52EventBus 3 Reg. Performance Nexus One
- 11:30EventBus 3 Reg. Performance Nexus 5 (5.1)
- 11:43Registration Performance Observations
related talks
37mWhat's new in architecture components
57mSimplify Your Architecture: Events and Publishing
52mA Deep Dive into Spring Application Events
24mAnnotation Processing in Android
01h 12mDemystifying "event-based" software concepts and methodologies
34mWhat's new with the Android Gradle plugin
49mDemystifying ‘Event’ Related Software Concepts and Methodologies
23mCloudEvents: Intro, Status and the Future...