Create a new adapter for a RecyclerView or ViewPager is now much easier.
Clone or download
Latest commit 0bcc3a2 Nov 14, 2018
Type Name Latest commit message Commit time
Failed to load latest commit information.
efficientadapter Update libraries version Nov 13, 2018
example Fix test heterogeneous Nov 13, 2018
gradle/wrapper Update libraries version Nov 13, 2018
gradle_script Change distribution to JCenter Apr 30, 2016
.gitignore Initial commit Oct 18, 2014 Go to 2.3.1 (17) Nov 13, 2018
LICENSE Create LICENSE Feb 5, 2018 Go to 2.3.1 (17) Nov 13, 2018
build.gradle Go to 2.3.1 (17) Nov 13, 2018 Initial commit Oct 18, 2014
gradlew Initial commit Oct 18, 2014
gradlew.bat Initial commit Oct 18, 2014
settings.gradle Change distribution to JCenter Apr 30, 2016

Efficient Adapter for Android

Create a new adapter for a RecyclerView or ViewPager is now much easier.


Create a list of elements into a RecyclerView or ViewPager is not that easy for a beginner, and repetitive for others. The goal of this library is to simplify that for you.

How does it work?

Create a class ViewHolder (BookViewHolder for example). The method updateView will be call with the object, when an update of your view is require:

public class BookViewHolder extends EfficientViewHolder<Book> {
    public BookViewHolder(View itemView) {  super(itemView); }

    protected void updateView(Context context, Book object) {
        TextView textView = findViewByIdEfficient(;
		// or just
		setText(, object.getTitle());

Give this ViewHolder class to the constructor of the adapter (SimpleAdapter) of your RecyclerView, with the resource id of your item view and the list of objects:

EfficientRecyclerAdapter<Plane> adapter = new EfficientRecyclerAdapter<Plane>(R.layout.item_book, BookViewHolder.class, listOfBooks);

And that's it!

It's also working with a ViewPager:

EfficientPagerAdapter<Plane> adapter = new EfficientPagerAdapter<Plane>(R.layout.item_book, BookViewHolder.class, listOfBooks);

Other features

Heterogenous list

For a list of different kind of objects, layout, viewholder…

EfficientRecyclerAdapter adapter = new EfficientRecyclerAdapter(generateListObjects()) {
    public int getItemViewType(int position) {
        if (get(position) instanceof Plane) {
            return VIEW_TYPE_PLANE;
        } else {
            return VIEW_TYPE_BOOK;

    public Class<? extends EfficientViewHolder> getViewHolderClass(int viewType) {
        switch (viewType) {
            case VIEW_TYPE_BOOK:
                return BookViewHolder.class;
            case VIEW_TYPE_PLANE:
                return PlaneViewHolder.class;
                return null;

    public int getLayoutResId(int viewType) {
        switch (viewType) {
            case VIEW_TYPE_BOOK:
                return R.layout.item_book;
            case VIEW_TYPE_PLANE:
                return R.layout.item_plane;
                return 0;

Efficient findViewById()

Because findViewById(int) is CPU-consuming (this is why we use the ViewHolder pattern), this library use a findViewByIdEfficient(int id) into the ViewHolder class.

You can use it like a findViewById(int id) but the view return will be cached to be returned into the next call.

Your view id should be unique into your view hierarchy, but sometimes is not that easy (with an include for example). It's now easier to find a subview by specify the parent of this subview with findViewByIdEfficient(int parentId, int id) to say "the view with this id into the parent with this id".

Let the element be clickable

Your ViewHolder class can override the method isClickable() to tell is this element is clickable or not.

By default, the view is clickable if you have a listener on your adapter.


This library includes the proguard configuration file. If you want to add it manually:

-keepclassmembers public class * extends com.skocken.efficientadapter.lib.viewholder.EfficientViewHolder {
    public <init>(...);


dependencies {
    compile 'com.skocken:efficientadapter:2.3.1'



Please fork this repository and contribute back using pull requests.

Any contributions, large or small, major features, bug fixes, additional language translations, unit/integration tests are welcomed and appreciated but will be thoroughly reviewed and discussed.