title: When to use IntentSender vs. PendingIntent?
body: <p>The Android documentation describes both <a href="http://developer.android.com/reference/android/app/PendingIntent.html" rel="noreferrer"><code>PendingIntent</code></a> and <a href="http://developer.android.com/reference/android/content/IntentSender.html" rel="noreferrer"><code>IntentSender</code></a> classes but it's not clear when or why you would use an <code>IntentSender</code> over a <code>PendingIntent</code> -- in fact much of the description appears to be identical for both.</p>
  
  <p>The <code>PendingIntent</code> documentation:</p>
  
  <blockquote>
    <p>A description of an Intent and target action to perform with it. Instances of this class are created with (...); the returned object can be handed to other applications so that they can perform the action you described on your behalf at a later time.</p>
  </blockquote>
  
  <p>The <code>IntentSender</code> documentation:</p>
  
  <blockquote>
    <p>A description of an Intent and target action to perform with it. The returned object can be handed to other applications so that they can perform the action you described on your behalf at a later time.</p>
  </blockquote>
  
  <p>Both classes are <code>Parcelable</code> and both classes allow the receiver to invoke the action with <code>send</code> or <code>sendIntent</code> (with nearly identical signatures).</p>
  
  <p>Since you need an existing <code>PendingIntent</code> to create an <code>IntentSender</code>, in what situation would you ever want to create an <code>IntentSender</code> rather than just using your <code>PendingIntent</code>?</p>