Is EventBus Making a Comeback in Navigation 3?
This title could be clearer and more informative.Try out Clickbait Shieldfor free (5 uses left this month).
Navigation 3 (alpha02) introduces a ResultEventBus API for passing results between NavEntries using keyed Channels. The post examines why classic EventBus patterns fell out of favor (implicit dependencies, lifecycle issues, lack of type safety), then dives into how ResultEventBus attempts to address those pitfalls by scoping communication strictly to navigation result passing. Both event-based and state-based usage patterns are demonstrated with code samples from the official nav3-recipes repository, along with practical implementation notes around ViewModel integration and the rememberResultEventBusNavEntryDecorator decorator.
Table of contents
Why Event Buses Fell Out of FavorEventBus: Events for Android - Open Source by greenrobotGitHub - square/otto: An enhanced Guava-based event bus with emphasis on Android support.Implementing an Event Bus With RxJava - RxBus - Kaushik Gopal's WebsiteShared flows, broadcast channelsWhat is ResultEventBus ?Get chanzmao ’s stories in your inboxOne-Time Events in Jetpack Compose: Why I Switched from SharedFlow to Channelobject vs compositionLocalOf vs staticCompositionLocalOf : The Ultimate State Sharing GuideOfficial samples 🎓Let’s Try It Out 🛠️Stop Passing ViewModels to Your Composables?Conclusion 🤔1.4K Impressions