# AnnotatedAdapter

DevFeed: [AnnotatedAdapter](<https://devfeed.tech/articles/annotatedadapter-25439.md>)

Original publisher: [Read original article](<https://hannesdorfmann.com/android/annotatedadapter/>)

Author: Hannes Dorfmann

Published: 2014-09-24T09:00:00Z

Content type: tutorial

Language: en

Sources: [Hannes Dorfmann](<https://devfeed.tech/sources/hannes-dorfmann.md>)

Topics: [Android](<https://devfeed.tech/topics/android.md>), [Code](<https://devfeed.tech/topics/code.md>), [Development](<https://devfeed.tech/topics/development.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [annotation-processor](<https://devfeed.tech/tags/annotation-processor.md>), [code](<https://devfeed.tech/tags/code.md>), [development](<https://devfeed.tech/tags/development.md>), [layout](<https://devfeed.tech/tags/layout.md>), [recyclerview](<https://devfeed.tech/tags/recyclerview.md>), [view](<https://devfeed.tech/tags/view.md>), [xml](<https://devfeed.tech/tags/xml.md>)

## AI overview

A tutorial introducing AnnotatedAdapter, an Android annotation-processor approach for generating repetitive RecyclerView adapter code such as layout inflation, ViewHolder setup, and view-type handling.

## Source excerpt

With FragmentArgs and ParcelablePlease I have already shown that Annotation Processor is really helpful to speedup development by reducing writing boilerplate code. Regarding Android I found one scenario where I find myself writing nearly the same code ever and ever again. I'm looking at you Adapter with your ViewHolders, layout inflating code and view types.