Why SAM conversions for Java interfaces in Kotlin? - Purpose & Use Cases

The Big Idea

Discover how a tiny Kotlin feature can save you from writing bulky Java code every day!

The Scenario

Imagine you want to use a Java interface with just one method in your Kotlin code. Without SAM conversions, you have to write a full anonymous class every time, even if you just want to pass a simple action.

The Problem

Writing anonymous classes for simple tasks is slow and clutters your code. It's easy to make mistakes and hard to read, especially when you just want to pass a small piece of behavior like a click listener or a callback.

The Solution

SAM conversions let you write a simple lambda expression instead of a full anonymous class. Kotlin automatically converts your lambda into the Java interface, making your code shorter, cleaner, and easier to understand.

Before vs After

✗ Before

button.setOnClickListener(object : View.OnClickListener {
    override fun onClick(v: View?) {
        println("Clicked")
    }
})

✓ After

button.setOnClickListener { println("Clicked") }

What It Enables

You can write concise, readable Kotlin code that works seamlessly with Java interfaces, making your apps easier to build and maintain.

Real Life Example

When adding a button click listener in Android, instead of writing a full anonymous class, you just write a short lambda that runs when the button is clicked.

Key Takeaways

SAM conversions simplify using Java interfaces with one method in Kotlin.

They replace verbose anonymous classes with clean lambda expressions.

This leads to clearer, more maintainable code.