Which one should I pick for a new project?
Which one should I pick for a new project?
About greenrobot/eventbus · 2 messages · last activity 9/6/2026
I can only answer questions about greenrobot/eventbus or romandanylyk/pageindicatorview.
These are two completely different libraries serving different purposes, so the choice depends on your project's needs:
greenrobot/eventbus — Use this if you need:
- Inter-component communication (Activities, Fragments, Services, background threads)
- A publish/subscribe event bus pattern
- Decoupled messaging within your application
romandanylyk/pageindicatorview — Use this if you need:
- Visual page indicators for ViewPagers
- Customizable dot animations (scale, slide, worm, fill, etc.)
- A UI component, not application architecture
They solve different problems. EventBus is architectural (how components talk to each other); PageIndicatorView is a UI widget (how pages are visualized). Many projects use both—EventBus for communication and PageIndicatorView for paging UI.
If you're building an Android app with page navigation and inter-component messaging, you might benefit from both. If you're only building page navigation UI, use PageIndicatorView. If you're only managing component communication, use EventBus.
The RepoPilot verdict for greenrobot/eventbus is "GO — Healthy across all four use cases," indicating it's well-maintained and reliable for production use.
FOLLOW_UPS:
- What is EventBus's subscriber index feature?
- How do I integrate PageIndicatorView with ViewPager?
- Does EventBus support Android background threads?
Want to ask your own question?
Open chat for greenrobot/eventbusPublic Q&A. Generated by RepoPilot from the actual source of greenrobot/eventbus. AI answers can be incomplete or stale — verify before relying on them.