Swipe to dismiss in Android Kotlin - Build, Publish & Deploy

Build & Publish - Swipe to dismiss

Performance Impact

Swipe to dismiss uses touch gestures and animations. Smooth 60fps frame rate is important for good user experience. Poorly optimized animations can cause jank or dropped frames. Memory use is usually low, but heavy UI elements inside swipeable items can increase memory and CPU load. Battery impact is minimal if animations are efficient.

Optimization Tips

• Use Android's ItemTouchHelper for built-in swipe support with optimized animations.
• Keep swipeable item layouts simple and lightweight.
• Avoid heavy work on the main thread during swipe gestures.
• Use hardware-accelerated animations and avoid overdraw.
• Recycle views properly in lists to reduce memory pressure.

App Size and Startup

Swipe to dismiss functionality uses standard Android libraries, so it adds negligible size to your app bundle. Custom animations or third-party libraries may increase size slightly. Startup time is not affected by swipe to dismiss unless you preload heavy resources for the swipe UI.

iOS vs Android Differences

On Android, swipe to dismiss is often implemented with RecyclerView and ItemTouchHelper. On iOS, similar behavior uses UITableView or UICollectionView with UISwipeActionsConfiguration. Android requires handling gesture detection and animations explicitly, while iOS provides built-in swipe action APIs. Both platforms recommend smooth animations and accessibility support.

Store Review Guidelines

• Ensure swipe gestures do not interfere with accessibility features (e.g., screen readers).
• Do not use swipe to dismiss for critical data without confirmation to prevent accidental loss.
• Follow platform UI guidelines for gesture responsiveness and visual feedback.
• Test on multiple device sizes and orientations to ensure consistent behavior.

Self-Check Question

Your app takes 5 seconds to load this screen with swipe to dismiss list. What's likely wrong?

• Heavy UI elements or images inside list items causing slow rendering.
• Swipe gesture handling blocking the main thread.
• Not recycling views properly, causing memory bloat.
• Complex animations without hardware acceleration.

Key Result

Swipe to dismiss uses touch gestures and animations that must be optimized for smooth 60fps performance. Use Android's built-in ItemTouchHelper for efficient implementation. The feature adds minimal app size impact and requires attention to accessibility and platform UI guidelines for store approval.

Practice

1.

What is the main purpose of implementing onSwiped in ItemTouchHelper.SimpleCallback when using swipe to dismiss?

easy

A. To change the background color of the list item

B. To add a new item to the list

C. To disable swipe gestures on the list

D. To remove the swiped item from the data and update the UI

Solution

1. Step 1: Understand the role of onSwiped

   This method is called when a user swipes an item. It is used to handle what happens after the swipe gesture.

2. Step 2: Identify the correct action after swipe

   The typical action is to remove the swiped item from the data source and notify the adapter to update the UI.

3. Final Answer:

   To remove the swiped item from the data and update the UI -> Option D

4. Quick Check:

   onSwiped removes item [OK]

Hint: Remember: swipe means remove item and refresh list [OK]

Common Mistakes:

• Trying to add items in onSwiped
• Ignoring data update after swipe
• Using onSwiped to change colors only

2.

Which of the following is the correct way to create a SimpleCallback for swipe to dismiss only (no drag) in Kotlin?

val callback = object : ItemTouchHelper.SimpleCallback(?, ?) {}

easy

A. 0, ItemTouchHelper.LEFT or ItemTouchHelper.RIGHT

B. ItemTouchHelper.UP or ItemTouchHelper.DOWN, ItemTouchHelper.LEFT or ItemTouchHelper.RIGHT

C. ItemTouchHelper.LEFT or ItemTouchHelper.RIGHT, 0

D. ItemTouchHelper.UP or ItemTouchHelper.DOWN, 0

Solution

1. Step 1: Understand SimpleCallback constructor parameters

   The first parameter is for drag directions, the second for swipe directions.

2. Step 2: Set drag to 0 and swipe to left or right

   For swipe to dismiss only, drag should be 0 and swipe should allow left or right.

3. Final Answer:

   0, ItemTouchHelper.LEFT or ItemTouchHelper.RIGHT -> Option A

4. Quick Check:

   Drag=0, Swipe=LEFT|RIGHT [OK]

Hint: Drag=0 disables drag; swipe=LEFT|RIGHT enables swipe [OK]

Common Mistakes:

• Swapping drag and swipe parameters
• Using drag directions when only swipe needed
• Setting swipe to 0 disables swipe

3.

Given this code snippet inside onSwiped:

val position = viewHolder.adapterPosition
items.removeAt(position)
adapter.notifyItemRemoved(position)

What will happen when the user swipes an item?

medium

A. The item remains but the UI flashes

B. The item is removed from the list and the UI updates to reflect the change

C. The app crashes due to invalid position

D. Nothing happens because notifyItemRemoved is missing

Solution

1. Step 1: Remove item from data list

   The code removes the item at the swiped position from the data list.

2. Step 2: Notify adapter about removal

   Calling notifyItemRemoved updates the UI to remove the item visually.

3. Final Answer:

   The item is removed from the list and the UI updates to reflect the change -> Option B

4. Quick Check:

   Remove item + notify adapter = UI updates [OK]

Hint: Remove data then notify adapter to update UI [OK]

Common Mistakes:

• Not removing item from data list
• Forgetting to notify adapter
• Using wrong adapter position

4.

What is wrong with this onSwiped implementation?

override fun onSwiped(viewHolder: RecyclerView.ViewHolder, direction: Int) {
    adapter.notifyItemRemoved(viewHolder.adapterPosition)
    items.removeAt(viewHolder.adapterPosition)
}

medium

A. The adapter position is not valid inside onSwiped

B. The method is missing a call to super.onSwiped

C. Calling notifyItemRemoved before removing item causes UI inconsistency

D. Nothing is wrong; this code works fine

Solution

1. Step 1: Check order of operations

   notifyItemRemoved should be called after removing the item from the data list.

2. Step 2: Understand impact of wrong order

   Calling notifyItemRemoved first causes the adapter to update UI before data changes, leading to inconsistency or crash.

3. Final Answer:

   Calling notifyItemRemoved before removing item causes UI inconsistency -> Option C

4. Quick Check:

   Remove data first, then notify adapter [OK]

Hint: Always update data before notifying adapter [OK]

Common Mistakes:

• Not removing item before notify
• Calling super.onSwiped unnecessarily
• Using wrong adapter position

5.

You want to implement swipe to dismiss in a RecyclerView but only allow swipe to the right. Which code snippet correctly sets up the SimpleCallback and handles the swipe?

val callback = object : ItemTouchHelper.SimpleCallback(0, ItemTouchHelper.RIGHT) {
    override fun onMove(...) = false
    override fun onSwiped(viewHolder: RecyclerView.ViewHolder, direction: Int) {
        val pos = viewHolder.adapterPosition
        items.removeAt(pos)
        adapter.notifyItemRemoved(pos)
    }
}
ItemTouchHelper(callback).attachToRecyclerView(recyclerView)

hard

A. This code allows swipe only to the right and removes the item correctly

B. This code allows swipe both left and right

C. This code will crash because onMove is not implemented properly

D. This code does not remove the item from the list

Solution

1. Step 1: Check swipe directions in SimpleCallback

   Swipe is set to ItemTouchHelper.RIGHT only, so only right swipe is allowed.

2. Step 2: Verify onSwiped removes item and notifies adapter

   onSwiped removes the item at adapterPosition and calls notifyItemRemoved correctly.

3. Step 3: Confirm onMove returns false

   Returning false disables drag, which is intended here.

4. Final Answer:

   This code allows swipe only to the right and removes the item correctly -> Option A

5. Quick Check:

   Swipe=RIGHT only + remove item + notify adapter [OK]

Hint: Set swipe directions and remove item in onSwiped [OK]

Common Mistakes:

• Setting swipe to LEFT or both directions
• Not removing item from data list
• Returning true in onMove causing drag