Why Custom exception classes in Kotlin? - Purpose & Use Cases

The Big Idea

What if your program could tell you exactly what went wrong, every time?

The Scenario

Imagine you are building a program that handles different errors like invalid input, missing files, or network problems. Without custom exceptions, you have to guess what went wrong just by looking at generic error messages.

The Problem

Using only built-in exceptions is like getting a vague "Something went wrong" message. It makes fixing problems slow and confusing because you can't tell exactly what caused the error or handle it properly.

The Solution

Custom exception classes let you create clear, specific error types. This way, your program can catch and respond to each problem exactly as needed, making your code easier to understand and maintain.

Before vs After

✗ Before

try {
    // code that might fail
} catch (e: Exception) {
    println("Error occurred")
}

✓ After

class InvalidInputException(message: String) : Exception(message)

try {
    // code that might fail
} catch (e: InvalidInputException) {
    println("Invalid input: ${e.message}")
}

What It Enables

It enables your program to clearly communicate and handle different problems, making debugging and user feedback much better.

Real Life Example

Think of a banking app that throws a specific exception when a withdrawal exceeds the balance. This helps the app show a clear message like "Insufficient funds" instead of a generic error.

Key Takeaways

Custom exceptions give clear, specific error types.

They help your program handle errors precisely.

This makes debugging and user messages easier and clearer.