Sealed Class Use Cases in Kotlin

Introduction

Sealed Class Use Cases is a fundamental concept every Kotlin developer should understand. Sealed classes restrict which subclasses can exist, making when expressions exhaustive and safer for representing finite state machines or result types.

Sealed classes model API responses, UI states and operation results. In this tutorial you will learn the syntax, walk through a complete example program, study the sample output, and review best practices so you can apply the concept confidently in your own projects.

Definition

• Sealed classes model API responses, UI states and operation results.
• They improve type safety compared to string constants.
• They work well with when for clean branching.

Syntax

sealed class ApiResult

Sealed Class Use Cases in Kotlin Example Program in Kotlin

sealed class ApiResult
class Ok<T>(val value: T) : ApiResult()
class Fail(val code: Int) : ApiResult()

fun main(args: Array<String>) {
    val result: ApiResult = Ok("Profile loaded")
    when (result) {
        is Ok<*> -> println(result.value)
        is Fail -> println("Error ${result.code}")
    }
}

Sample Output

Profile loaded

When to use

Use sealed classes for closed hierarchies — UI states, network results, or AST node types.

How it works

1. The program starts with a main function — the entry point that runs when you execute the file.

2. val result: ApiResult = Ok("Profile loaded") assigns or updates a value used later in the program.

3. The println(result.value) statement writes a line to the console — this produces part of the sample output below.

4. The println("Error ${result.code}") statement writes a line to the console — this produces part of the sample output below.

5. Sealed classes model API responses, UI states and operation results.

6. Run the program in IntelliJ IDEA, Android Studio, or with the Kotlin command-line compiler (kotlinc / kotlin). Compare your console output with the sample output shown below.

Best Practices

• Understand the core idea: sealed classes model API responses, UI states and operation results.
• Prefer readable names and small functions so examples map directly to real projects.
• Run and modify the example — change values and observe how the output changes.

Common Mistakes

• Skipping the example and only reading the definition — hands-on practice cements the concept.
• Copying syntax without understanding nullable vs non-nullable types or scope rules.
• Ignoring compiler warnings that often point to safer alternatives.

Key Points

• Sealed classes model API responses, UI states and operation results.
• They improve type safety compared to string constants.
• They work well with when for clean branching.
• Test the example locally and verify the output matches the sample.
• Experiment by changing input values to see how behaviour changes.

Notes

• Semicolons at the end of statements are optional in Kotlin.