> For the complete documentation index, see [llms.txt](https://android-course.cornellappdev.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://android-course.cornellappdev.com/archive/archived-native-android-textbook-pages/4.-listview-and-recyclerview/4.1-recycler-views.md).

# 2.1 RecyclerViews

Lists are one of the most ubiquitous layouts that can be found in any mobile app. All of the screenshots below show different usages of a list-like layout. In Facebook, lists are used to display each post in the news feed and allow a user to engage with the post through likes and comments. In Podbean, each cell in the list is clickable and leads the user to the specific podcast's page. Finally, in Venmo, the list just displays information on past transactions with some user interactions supported.

![](/files/-LvTml59yJE5FYdTNncZ)

RecyclerView makes it easy to efficiently display large sets of data. You supply the data and define how each item looks, and the RecyclerView library dynamically creates the elements when they're needed.

As the name implies, RecyclerView *recycles* those individual elements. When an item scrolls off the screen, RecyclerView doesn't destroy its view. Instead, RecyclerView reuses the view for new items that have scrolled onscreen. This reuse vastly improves performance, improving your app's responsiveness and reducing power consumption (more on this in the next section, [2.2 RecyclerView Performance](/archive/archived-native-android-textbook-pages/4.-listview-and-recyclerview/4.3-performance.md)).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://android-course.cornellappdev.com/archive/archived-native-android-textbook-pages/4.-listview-and-recyclerview/4.1-recycler-views.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.