How to avoid Interface-Hell and Eventbus-Confusion?

Question

I develop some apps for android and always come to point where I need to communicate within

• Fragment to Activity
• Activity to Fragment
• Fragment to Fragment
• Service to Fragment
• etc.

At the Android documentation they recommend to use interfaces to communicate between Activity and Fragment for example. But I have for example 4 Fragments, then my Activity needs to implement 4 Interfaces. I my intention right?

So I tried Otto and it is worth to try it. However I recognized, if you don't track the bus events you could get very confused.

I searching for a strategy to avoid those approches. How does it Google or other major developer?

Answer 1

If you are using IntelliJ or Android Studio for development you can minify confusion with Otto IntelliJ Plugin.