Perfect — here's how to create a clean, reusable utility method to hide the keyboard across all activities or fragments, including ChatActivity.

✅ Step-by-Step: Make hideKeyboard a Reusable Utility

🔹 Step 1: Create a Kotlin File for Extensions

📄 KeyboardUtils.kt (create under com.seneca.dayamed.utils or your preferred utils package):

package com.seneca.dayamed.utils

import android.app.Activity
import android.view.View
import android.view.inputmethod.InputMethodManager
import android.content.Context

fun Activity.hideKeyboard() {
    val imm = getSystemService(Context.INPUT_METHOD_SERVICE) as InputMethodManager
    val view = currentFocus ?: View(this)
    imm.hideSoftInputFromWindow(view.windowToken, 0)
    view.clearFocus()
}

✅ This will work in any Activity. You can also extend this to Fragment or View if needed later.

🔹 Step 2: Use It in ChatActivity

In ChatActivity, update your setupRecyclerView() like this:

import com.seneca.dayamed.utils.hideKeyboard // 👈 Make sure to import it

private fun setupRecyclerView() {
    binding.recyclerView.apply {
        layoutManager = LinearLayoutManager(this@ChatActivity).apply {
            stackFromEnd = true
        }
        adapter = chatAdapter

        setOnTouchListener { _, _ ->
            hideKeyboard()
            false
        }
    }
}

✅ Benefits

  • ✔ Clean and reusable across any Activity

  • 📦 Centralized utility — easy to maintain

  • ✨ Extendable to Fragment.hideKeyboard(), View.hideKeyboard(), etc.

Let me know if you want companion functions for Fragment or View as well!

Comments

Post a Comment

Popular posts from this blog

Jetpack Compose based Android interview and questions

What’s Jetpack Compose and its Benefits? Jetpack Compose is a modern UI toolkit recently launched by Google which is used for building native Android UI. It simplifies and accelerates the UI development with less code, Kotlin APIs, and powerful tools.  Declarative Compatible Increase development speed Concise and Idiomatic Kotlin Easy to maintain Written in Kotlin To read more, refer  to  the article:  Jetpack Compose in Android Aaaaaa
Read more

Kotlin Some important unsorted interview questions and answers

Image
  What is inline class in Kotlin and when do we need one? Provide an example.  What is inline class in Kotlin and when do we need one? Provide an example. Senior Answer Sometimes it is necessary for business logic to create a wrapper around some type. However, it introduces runtime overhead due to additional heap allocations. Moreover, if the wrapped type is primitive, the performance hit is terrible, because primitive types are usually heavily optimized by the runtime. Inline classes  provide us with a way to wrap a type, thus adding functionality and creating a new type by itself. As opposed to regular (non-inlined) wrappers, they will benefit from improved performance. This happens because the data is inlined into its usages, and object instantiation is skipped in the resulting compiled code. inline class Name ( val s : String ) { val length : Int get ( ) = s . length fun greet ( ) { println ( "Hello, $s " ) } } fun ma...
Read more

Null safety based Kotlin interview questions and answers

Image
Nullable Non Nullable Types What’s Null Safety and Nullable Types in Kotlin? What is the Elvis Operator? Kotlin puts a lot of weight behind null safety which is an approach to prevent the dreaded Null Pointer Exceptions by using nullable types which are like  String? ,  Int? ,  Float?  etc. These act as a wrapper type and can hold null values. A nullable value cannot be added to another nullable or basic type of value. To retrieve the basic types we need to use safe calls that unwrap the Nullable Types. If on unwrapping, the value is null we can choose to ignore or use a default value instead. The Elvis Operator is used to safely unwrap the value from the Nullable. It’s represented as  ?:  over the nullable type. The value on the right hand side would be used if the nullable type holds a null. var str: String ? = "JournalDev.com" var newStr = str?: "Default Value" str = null newStr = str?: "Default Value" How is  !! different from ?. in unwrappi...
Read more