Why use an interface to communicate from fragment to activity?
<p>What is the advantage of using an interface to communicate from a fragment to an activity, as described here: <a href="http://developer.android.com/training/basics/fragments/communicating.html" rel="nofollow">http://developer.android.com/training/basics/fragments/communicating.html</a></p>

<p>This creates an unecessary dependency when we could have created an "onArticleSelected()" method in the activity WITHOUT THE INTERFACE and called it in the fragment via getActivity().onArticleSelected().  </p>

<p>What if the activity, at another point in time contain a fragment where there are no articles, why create this illogical dependency and add more code?</p>