title: Are android adapters an example of Adapter Design pattern?
body: <p>Do Android adapters use Adapter Design pattern? The GoF design patterns book describes Adapter Design Pattern as </p>
  
  <blockquote>
    <p>The Adapter Pattern converts the interface of a class
    into another interface the clients expect. Adapter lets
    classes work together that couldn’t otherwise because of
    incompatible interfaces.</p>
  </blockquote>
  
  <p>There's a target interface which the adapter implements and the client uses(expects) and there is an adaptee to which the adapter delegates all the requests made by client.</p>
  
  <p>I understand that its theory and real world pattern adapter interfaces don't exactly look like it, but still I can't figure out what the android adapters adapt(what target interface) and to which adaptee are the requests actually made to.</p>
  
  <p>I have checked <a href="https://stackoverflow.com/questions/21671492/listview-and-adapters-in-android-does-falls-under-adapter-design-pattern">this</a>, <a href="https://stackoverflow.com/questions/13495405/is-androids-baseadapter-an-example-of-adapter-pattern">this</a> and <a href="https://stackoverflow.com/questions/4916209/which-design-patterns-are-used-on-android/36668058#36668058">this</a>. But none of them explain clearly how is the android adapter the adapter design pattern. The <a href="https://stackoverflow.com/questions/21671492/listview-and-adapters-in-android-does-falls-under-adapter-design-pattern">1st</a> and <a href="https://stackoverflow.com/questions/13495405/is-androids-baseadapter-an-example-of-adapter-pattern">2nd</a> answers, in fact, are somewhat conflicting. </p>
  
  <p>Can anyone please explain this?</p>