RecyclerView vs ListView in Android

Problem What is the difference between RecyclerView and ListView in Android?

Be ready to discuss

• View recycling: ListView recycles via convertView and leaves the ViewHolder pattern as an optional convention developers often got wrong; RecyclerView enforces ViewHolder by design so view lookups are not repeated on every bind.
• Separation of concerns: RecyclerView splits responsibilities across LayoutManager (positioning), Adapter/ViewHolder (binding), ItemAnimator (animations), and ItemDecoration (dividers/spacing) — ListView bakes these into one widget.
• Layout flexibility: pluggable LinearLayoutManager, GridLayoutManager, StaggeredGridLayoutManager, or a custom one, versus ListView's fixed vertical list.
• Updates and diffing: notifyItemInserted/notifyItemChanged and DiffUtil enable targeted updates with animations, versus ListView's coarse notifyDataSetChanged full rebind.
• Costs of RecyclerView: no built-in item click listener, no header/footer support, and more boilerplate — a genuinely simple static list was cheaper in ListView, which is the trade-off worth naming.
• Performance details: view type support, setHasFixedSize, shared RecycledViewPool across nested lists, and prefetching.
• Context: RecyclerView is the modern standard and ListView is effectively legacy, with Jetpack Compose's LazyColumn as the current successor to both.