> 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/5.-listviews/4.1-listview.md). # 3.1 ListView vs. RecyclerView `ListView` and `RecyclerView` are two different layouts that can be used to display a list of objects, but it is often difficult to tell which one is being used in a mobile app. Typically the implementation of a `ListView` is simpler than a `RecyclerView` but are less performant. For apps like those you built in HW4 and will build in HW5 where there are minimal calculations, a `ListView` is perfectly serviceable. We used both types of layouts in Eatery: ![](/files/-LvTosamzTLm-NKFGFsL) Looking at a list in an app for the first time, it’s difficult to tell whether the screen is made with a list view or a recycler view. In fact, to the user, there is **almost no visual difference** between a list made with either layouts. The main difference between the two layouts stems from how they handle performance. In the industry, it is highly recommended to use a recycler view unless you are building a very simple list that does not require heavy computations, as previously mentioned. --- # 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/5.-listviews/4.1-listview.md?ask=&goal= ``` `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.