title: Understanding the Fragment.newInstance method
body: <p>I'm implementing an Android fragment. I understand that the framework can automatically destroy and recreate the fragment, and that recreating a fragment calls its default constructor, as opposed to a constructor that has arguments. 
  There are many posts (such as the accepted answer to <a href="https://stackoverflow.com/questions/9245408/best-practice-for-instantiating-a-new-android-fragment">this question</a>) that show how to provide arguments to the fragment by implementing a static <code>newInstance</code> method.</p>
  
  <p>What I don't understand is who calls <code>newInstance</code>. My first impression was that - since one can define arbitrary arguments for this <code>newInstance</code> method - I should add an explicit call to it somewhere in the app, and that the name <code>newInstance</code> is just a naming convention. But then I would be creating a second fragment in addition to the one created by framework calling the default constructor, which confuses me.</p>
  
  <p>So is the above assumption incorrect, and the <code>newInstance</code> method is really somehow an overload of Java's built-in method for instantiating a class? In that case, I don't see how I can define a <code>newinstance</code> method that takes an arbitrary argument list. Or is that possible in Java, and I just don't know Java well enough?</p>