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。ListView应该只在项目数量总是相同并且受屏幕大小限制的情况下使用。

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

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

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

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

mikepenz的FastAdapter

davideas的FlexibleAdapter

以下是RecyclerView和ListView之间的几个关键点/区别。明智地接电话。

If ListView works for you, there is no reason to migrate. If you are writing a new UI, you might be better off with RecyclerView. RecylerView has inbuilt ViewHolder, doesn't need to implement our own like in listView. It support notify at particular index as well Things like animating the addition or removal of items are already implemented in the RecyclerView without you having to do anything We can associate a layout manager with a RecyclerView, this can be used for getting random views in recycleview while this was limitation in ListView In a ListView, the only type of view available is the vertical ListView. There is no official way to even implement a horizontal ListView. Now using a RecyclerView, we can have a i) LinearLayoutManager - which supports both vertical and horizontal lists, ii) StaggeredLayoutManager - which supports Pinterest like staggered lists, iii) GridLayoutManager - which supports displaying grids as seen in Gallery apps. And the best thing is that we can do all these dynamically as we want.

主要优势:

ViewHolder在ListView中默认是不可用的。我们将在getView()中显式地创建。 RecyclerView有内置的Viewholder。

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

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

RecyclerView被创建为一个ListView的改进，所以是的，你可以创建一个附加列表与ListView控件，但使用RecyclerView更容易，因为它:

在向上/向下滚动时重用单元格——这在ListView适配器中实现View Holder是可能的，但这是一个可选的事情，而在RecycleView中，这是默认的写适配器的方式。 解耦列表从它的容器-所以你可以很容易地把列表项在运行时在不同的容器(线性布局，gridLayout)通过设置LayoutManager。

例子:

mRecyclerView = (RecyclerView) findViewById(R.id.my_recycler_view);
mRecyclerView.setLayoutManager(new LinearLayoutManager(this));
//or
mRecyclerView.setLayoutManager(new GridLayoutManager(this, 2));

动画常用列表动作——动画被解耦并委托给ItemAnimator。

还有更多关于RecyclerView的内容，但我认为这些要点是主要的。

因此，综上所述，RecyclerView是处理“列表数据”的一个更灵活的控件，它遵循关注点的委托模式，只留给自己一个任务——回收项目。