Gesture handling in Android Kotlin - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ ui_behavior

intermediate

Detecting a Single Tap Gesture

What will be the output when the user performs a single tap on the view with the following code?

Android Kotlin

val gestureDetector = GestureDetector(context, object : GestureDetector.SimpleOnGestureListener() {
  override fun onDown(e: MotionEvent?): Boolean {
    return true
  }
  override fun onSingleTapConfirmed(e: MotionEvent?): Boolean {
    println("Single tap detected")
    return true
  }
})

view.setOnTouchListener { _, event ->
  gestureDetector.onTouchEvent(event)
  true
}

A Prints "Single tap detected" once per tap

B Throws a runtime exception

C Does not print anything on tap

D Prints "Single tap detected" multiple times per tap

💡 Hint

Consider how GestureDetector.SimpleOnGestureListener handles tap events.

The onSingleTapConfirmed method is called once per confirmed single tap, so the message prints once per tap.

❓ lifecycle

intermediate

GestureDetector and Activity Lifecycle

What happens if you create a GestureDetector inside onCreate but forget to set the OnTouchListener on the view?

A GestureDetector will detect gestures automatically without OnTouchListener

B GestureDetector will not receive touch events, so no gestures are detected

C App will crash with NullPointerException

D GestureDetector will detect gestures but with delay

💡 Hint

Think about how touch events reach GestureDetector.

GestureDetector needs touch events passed to it via OnTouchListener; without it, it won't detect gestures.

🔧 Debug

advanced

Why does onFling not trigger?

Given this code snippet, why might the onFling gesture not trigger as expected? val gestureDetector = GestureDetector(context, object : GestureDetector.SimpleOnGestureListener() { override fun onDown(e: MotionEvent?): Boolean { return true } override fun onFling(e1: MotionEvent?, e2: MotionEvent?, velocityX: Float, velocityY: Float): Boolean { println("Fling detected") return true } }) view.setOnTouchListener { _, event -> gestureDetector.onTouchEvent(event) true }

A GestureDetector must be recreated on every touch event

B onFling requires overriding onScroll as well

C The velocity thresholds for fling are not met because the swipe is too slow

D The view does not have focus

💡 Hint

Consider what conditions GestureDetector uses to recognize a fling.

onFling triggers only if the swipe velocity exceeds a certain threshold; slow swipes won't trigger it.

🧠 Conceptual

advanced

Difference Between onTouchEvent and OnTouchListener

Which statement correctly describes the difference between overriding View.onTouchEvent and setting an OnTouchListener?

A OnTouchListener is called before onTouchEvent and can consume the event to prevent onTouchEvent from running

B onTouchEvent is a method inside the View class to handle touch events; OnTouchListener is an interface to listen for touch events externally

C Both are the same and interchangeable

D onTouchEvent only handles multi-touch, OnTouchListener only handles single touch

💡 Hint

Think about event propagation and consumption in Android touch system.

OnTouchListener's onTouch method is called before View's onTouchEvent; returning true consumes the event and stops further processing.

❓ navigation

expert

Gesture Navigation Conflict Resolution

In an app with a horizontal ViewPager and a vertical ScrollView inside each page, what is the best way to handle gesture conflicts so both horizontal swipes and vertical scrolls work smoothly?

A Wrap ScrollView in a FrameLayout to block gestures

B Disable scrolling in ScrollView and handle all gestures in ViewPager

C Use GestureDetector only on ScrollView and ignore ViewPager gestures

D Override onInterceptTouchEvent in the parent ViewPager to detect vertical scrolls and avoid intercepting them

💡 Hint

Think about how parent views can decide to intercept touch events.

Overriding onInterceptTouchEvent allows the ViewPager to decide when to intercept horizontal swipes and let vertical scrolls pass to ScrollView.

Practice

1. What is the primary purpose of using GestureDetector in Android Kotlin apps?

easy

A. To detect user gestures like taps and swipes on a view

B. To create animations for UI components

C. To manage app navigation between screens

D. To handle database operations asynchronously

Solution

1. Step 1: Understand GestureDetector role

   GestureDetector is designed to listen for user touch gestures such as taps, swipes, and long presses on views.

2. Step 2: Compare other options

   Options A, B, and D relate to navigation, animations, and database tasks, which are unrelated to gesture detection.

3. Final Answer:

   To detect user gestures like taps and swipes on a view -> Option A

4. Quick Check:

   GestureDetector = Detect gestures [OK]

Hint: GestureDetector listens for touch gestures on views [OK]

Common Mistakes:

• Confusing GestureDetector with animation tools
• Thinking GestureDetector manages navigation
• Assuming GestureDetector handles data tasks

2. Which of the following is the correct way to create a GestureDetector with a simple gesture listener in Kotlin?

easy

A. val detector = GestureDetector(this, object : GestureDetector.SimpleOnGestureListener() {})

B. val detector = GestureDetector(object : GestureDetector.SimpleOnGestureListener() {}, this)

C. val detector = GestureDetector(this, GestureListener())

D. val detector = GestureDetector.SimpleOnGestureListener(this)

Solution

1. Step 1: Check GestureDetector constructor syntax

   The constructor takes a Context (usually 'this') and a GestureDetector.OnGestureListener implementation, often an anonymous object of SimpleOnGestureListener.

2. Step 2: Validate options

   val detector = GestureDetector(this, object : GestureDetector.SimpleOnGestureListener() {}) matches the correct syntax. val detector = GestureDetector(object : GestureDetector.SimpleOnGestureListener() {}, this) reverses parameters. val detector = GestureDetector(this, GestureListener()) uses an undefined class. val detector = GestureDetector.SimpleOnGestureListener(this) incorrectly calls SimpleOnGestureListener as a constructor.

3. Final Answer:

   val detector = GestureDetector(this, object : GestureDetector.SimpleOnGestureListener() {}) -> Option A

4. Quick Check:

   Context first, listener second in GestureDetector constructor [OK]

Hint: Context is first, listener second in GestureDetector constructor [OK]

Common Mistakes:

• Swapping constructor parameters order
• Using undefined listener classes
• Calling listener as a constructor

3. Given this Kotlin code snippet inside an Activity:

val detector = GestureDetector(this, object : GestureDetector.SimpleOnGestureListener() {
  override fun onSingleTapUp(e: MotionEvent?): Boolean {
    println("Tapped")
    return true
  }
})

view.setOnTouchListener { _, event ->
  detector.onTouchEvent(event)
  true
}

What will happen when the user taps on the view?

medium

A. The view ignores the tap and does not respond

B. Nothing happens because onSingleTapUp is not called

C. The message "Tapped" is printed to the console

D. The app crashes due to missing return statement

Solution

1. Step 1: Understand onSingleTapUp override

   The overridden method prints "Tapped" and returns true, indicating the tap gesture was handled.

2. Step 2: Check touch listener behavior

   The touch listener passes events to the detector, which triggers onSingleTapUp on tap, so "Tapped" is printed.

3. Final Answer:

   The message "Tapped" is printed to the console -> Option C

4. Quick Check:

   onSingleTapUp triggers print on tap [OK]

Hint: onSingleTapUp prints message when tap detected [OK]

Common Mistakes:

• Assuming onSingleTapUp is never called
• Forgetting to return true to handle gesture
• Ignoring event forwarding to GestureDetector

4. What is wrong with this Kotlin code snippet for gesture detection?

val detector = GestureDetector(this, object : GestureDetector.SimpleOnGestureListener() {
  override fun onLongPress(e: MotionEvent?) {
    println("Long press detected")
  }
})

view.setOnTouchListener { _, event ->
  detector.onTouchEvent(event)
}

medium

A. MotionEvent parameter cannot be nullable

B. onLongPress must return a Boolean

C. GestureDetector requires a separate listener for long press

D. The onTouchListener does not return a Boolean value

Solution

1. Step 1: Check onTouchListener return type

   onTouchListener must return a Boolean indicating if the event was handled. This code lacks a return statement.

2. Step 2: Validate other parts

   onLongPress returns void (Unit) correctly. GestureDetector supports long press in the same listener. MotionEvent can be nullable.

3. Final Answer:

   The onTouchListener does not return a Boolean value -> Option D

4. Quick Check:

   onTouchListener must return Boolean [OK]

Hint: Always return Boolean from onTouchListener [OK]

Common Mistakes:

• Forgetting to return true or false in onTouchListener
• Expecting onLongPress to return Boolean
• Misunderstanding nullable MotionEvent

5. You want to detect both single taps and double taps on a view using GestureDetector in Kotlin. Which approach correctly handles both gestures without conflict?

hard

A. Use two separate GestureDetectors, one for single tap and one for double tap, attached to the same view

B. Use GestureDetector with a GestureDetector.OnDoubleTapListener and override both onSingleTapConfirmed and onDoubleTap methods

C. Override only onSingleTapUp and ignore double taps to avoid conflicts

D. Use onTouchListener to manually count taps and ignore GestureDetector

Solution

1. Step 1: Understand GestureDetector double tap support

   GestureDetector supports double tap detection via OnDoubleTapListener interface, which includes onSingleTapConfirmed and onDoubleTap methods.

2. Step 2: Evaluate options for handling both taps

   Use GestureDetector with a GestureDetector.OnDoubleTapListener and override both onSingleTapConfirmed and onDoubleTap methods correctly uses OnDoubleTapListener to distinguish single and double taps. Use two separate GestureDetectors, one for single tap and one for double tap, attached to the same view causes conflicts with multiple detectors. Override only onSingleTapUp and ignore double taps to avoid conflicts ignores double taps. Use onTouchListener to manually count taps and ignore GestureDetector is manual and error-prone.

3. Final Answer:

   Use GestureDetector with a GestureDetector.OnDoubleTapListener and override both onSingleTapConfirmed and onDoubleTap methods -> Option B

4. Quick Check:

   OnDoubleTapListener handles single and double taps [OK]

Hint: Use OnDoubleTapListener to handle single and double taps [OK]

Common Mistakes:

• Using multiple GestureDetectors on one view
• Ignoring double tap detection
• Manually counting taps instead of using listener