Introduction

Spacing between ListView items is a small UI detail that has a big impact on readability, touch comfort, and perceived quality. Legacy Android apps still use ListView, so getting spacing right is often a maintenance task rather than a greenfield design decision. The best technique depends on whether you need simple visual gaps, card-style rows, or precise per-item control.

Quick Spacing with Divider Height

The fastest approach is a transparent divider plus dividerHeight. It requires no adapter changes.

1<ListView
2    android:id="@+id/listView"
3    android:layout_width="match_parent"
4    android:layout_height="match_parent"
5    android:divider="@android:color/transparent"
6    android:dividerHeight="8dp"
7    android:padding="12dp"
8    android:clipToPadding="false" />

This works well for simple text rows and avoids complex layout edits.

Card-Style Gaps with Item Margins

If each row has its own background shape, margins in the row layout give cleaner visual separation than dividers.

1<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
2    android:layout_width="match_parent"
3    android:layout_height="wrap_content"
4    android:layout_marginTop="6dp"
5    android:layout_marginBottom="6dp"
6    android:padding="16dp"
7    android:background="@drawable/row_card"
8    android:orientation="vertical">
9
10    <TextView
11        android:id="@+id/title"
12        android:layout_width="wrap_content"
13        android:layout_height="wrap_content"
14        android:textSize="16sp" />
15</LinearLayout>

Margin-based spacing is usually better when rows look like independent cards.

Keep Spacing Rules in XML, Not Adapter Side Effects

ListView recycles views aggressively. If you set spacing dynamically in getView, inconsistent state can appear while scrolling. Keep spacing in layout XML and keep adapter logic focused on data binding.

1class UserAdapter(
2    context: Context,
3    private val users: List<String>
4) : ArrayAdapter<String>(context, 0, users) {
5
6    override fun getView(position: Int, convertView: View?, parent: ViewGroup): View {
7        val row = convertView ?: LayoutInflater.from(context)
8            .inflate(R.layout.item_user, parent, false)
9
10        row.findViewById<TextView>(R.id.title).text = users[position]
11        return row
12    }
13}

Predictable spacing behavior comes from deterministic layout resources.

Edge Spacing for First and Last Items

Many screens need breathing room above the first row and below the last row. Apply list-level padding and disable clipping.

1<ListView
2    android:id="@+id/listView"
3    android:layout_width="match_parent"
4    android:layout_height="match_parent"
5    android:paddingTop="12dp"
6    android:paddingBottom="12dp"
7    android:clipToPadding="false"
8    android:divider="@android:color/transparent"
9    android:dividerHeight="8dp" />

Without clipToPadding="false", top and bottom spacing may not appear as expected.

Use Dimensions Resources for Consistency

Hardcoded spacing values scattered across layouts become maintenance debt. Define spacing in dimens.xml and override for larger screens.

1<!-- res/values/dimens.xml -->
2<resources>
3    <dimen name="list_item_gap">8dp</dimen>
4    <dimen name="list_outer_padding">12dp</dimen>
5</resources>

1<!-- res/values-sw600dp/dimens.xml -->
2<resources>
3    <dimen name="list_item_gap">12dp</dimen>
4    <dimen name="list_outer_padding">16dp</dimen>
5</resources>

This keeps phone and tablet spacing coherent with minimal code change.

ListView Maintenance Versus RecyclerView

For new features, RecyclerView with ItemDecoration is usually preferred. However, many products still ship legacy ListView screens. You can still achieve good results by isolating spacing decisions in layout resources and adapters that do only binding.

If migration is planned later, reusing row layouts and spacing dimensions reduces rewrite cost.

Accessibility and Visual QA

Spacing should be validated under real user conditions:

• larger font scales
• dark and light themes
• right-to-left locale layouts
• low-end devices with slower rendering

A layout that looks fine at default settings can become crowded when text size increases.

Common Pitfalls

• Using both large divider height and large row margins, resulting in excessive gaps.
• Forgetting clipToPadding="false" when expecting visible edge padding.
• Hardcoding pixel values instead of density-independent units.
• Applying row background to the wrong container and creating visual artifacts.
• Mutating spacing in adapter code and causing recycled-view inconsistencies.

Summary

• Transparent dividers are the simplest way to add vertical gaps in ListView.
• Row margins are better for card-like designs.
• Keep spacing definitions in XML dimensions for consistency and reuse.
• Use list padding with clipping disabled for clean edge spacing.
• Validate spacing across themes, text scales, and device classes.
• Centralized spacing rules make future migration from ListView to RecyclerView much easier.