为了使列表视图具有良好的性能，您需要实现holder模式，这很容易搞砸，特别是当您想用几种不同类型的视图填充列表时。

RecyclerView烘焙了这个模式，使它更难以搞砸。它也更灵活，更容易处理不同的布局，不是直线，如网格。

ListView和RecyclerView之间有很多区别，但你应该特别注意以下几点:

ViewHolder模式在ListView中是完全可选的，但它被烘焙到RecyclerView中。 ListView只支持垂直滚动，但RecyclerView并不局限于垂直滚动列表。

ListView是RecyclerView的祖先。有很多事情ListView没有做，或者做得不好。如果您要收集ListView的缺点，并通过将问题抽象到不同的域来解决问题，那么您最终会得到类似于回收器视图的东西。下面是ListViews的主要问题点:

Didn't enforce View Reuse for same item types (look at one of the adapters that are used in a ListView, if you study the getView method you will see that nothing prevents a programmer from creating a new view for every row even if one is passed in via the convertView variable) Didn't prevent costly findViewById uses(Even if you were recycling views as noted above it was possible for devs to be calling findViewById to update the displayed contents of child views. The main purpose of the ViewHolder pattern in ListViews was to cache the findViewById calls. However this was only available if you knew about it as it wasn't part of the platform at all) Only supported Vertical Scrolling with Row displayed Views (Recycler view doesn't care about where views are placed and how they are moved, it's abstracted into a LayoutManager. A Recycler can therefore support the traditional ListView as shown above, as well as things like the GridView, but it isn't limited to that, it can do more, but you have to do the programming foot work to make it happen). Animations to added/removed was not a use case that was considered. It was completely up to you to figure out how go about this (compare the RecyclerView. Adapter classes notify* method offerings v. ListViews to get an idea).

简而言之，RecyclerView是一个更灵活的ListView，尽管你可能需要做更多的编码工作。

RecyclerView是一个新的ViewGroup，准备渲染任何 以类似的方式创建基于适配器的视图。它应该是 ListView和GridView的继承者，它可以在 最新的support-v7版本。已经开发了RecyclerView 考虑到可扩展性，因此可以创建任何类型的 你能想到的布局，但也不能没有一点恼人的地方 剂量。

安东尼奥·莱瓦的回答

 compile 'com.android.support:recyclerview-v7:27.0.0'

RecyclerView确实是一个比ListView强大的视图。 欲了解更多详情，请访问此页面。

简单的回答:在想要显示许多项，并且它们的数量是动态的情况下，应该使用RecyclerView。ListView应该只在项目数量总是相同并且受屏幕大小限制的情况下使用。

你会发现这很难，因为你只考虑Android库。

现在有很多选项可以帮助您构建自己的适配器，使您可以轻松地构建动态项目的列表和网格，您可以选择、重新排序、使用动画、分隔符、添加页脚、页眉等等。

不要害怕，给一个尝试RecyclerView，你可以开始喜欢它从一个ListView和一个RecyclerView中从网络下载的100个项目的列表，当你尝试滚动时，你会看到UX(用户体验)的差异，可能测试应用程序会在你甚至可以这样做之前停止。

我建议你检查这两个库来制作简单的适配器:

mikepenz的FastAdapter

davideas的FlexibleAdapter

I think the main and biggest difference they have is that ListView looks for the position of the item while creating or putting it, on the other hand RecyclerView looks for the type of the item. if there is another item created with the same type RecyclerView does not create it again. It asks first adapter and then asks to recycledpool, if recycled pool says "yeah I've created a type similar to it", then RecyclerView doesn't try to create same type. ListView doesn't have a this kind of pooling mechanism.