Deep Kotlin tutorial covering nullable types, non-null types, compiler checks, null handling with examples, diagram, mistakes, and interview answers.

Nullable and Non-null Types

What is Nullable and Non-null Types?

Nullable and Non-null Types is an important Kotlin topic from 1.2 Immutability, Null Safety, and Type System. In this lesson we focus only on the concepts that belong together: nullable types, non-null types, compiler checks, null handling. This keeps the lesson deep enough for interviews but not mixed with unrelated ideas.

Why students should learn it

• Understand Nullable and Non-null Types in simple language
• Use nullable types in real Kotlin or Android code
• Explain Nullable and Non-null Types in interviews with examples and trade-offs

How it works

Nullable and Non-null Types: nullable types, non-null types, compiler checks, null handling works through Kotlin's type system. The compiler uses type information to warn you before runtime. When the type says a value may be missing, changing, or unknown because it came from Java, your code must handle that explicitly.

1. Identify what problem Nullable and Non-null Types: nullable types, non-null types, compiler checks, null handling solves.
2. Write the smallest Kotlin snippet that demonstrates it.
3. Add one Android or JVM use case where it matters.
4. Compare it with a similar concept so the difference is clear.
5. Finish by naming one common mistake and the safer alternative.

Interview tip: keep the answer simple first, then add example, trade-off, and mistake.

Types / Classification

• nullable types: core concept in this lesson
• non-null types: core concept in this lesson
• compiler checks: core concept in this lesson
• null handling: core concept in this lesson
• Non-null type: value should exist
• Nullable type: value can be missing
• Safe access: handles absence
• Unsafe access: may crash

Important differences

Diagram

flowchart TD
A["1.2 Immutability, Null Safety, and Type System"] --> B["Nullable and Non-null Types"]
B --> C["Why it exists"]
C --> D["How it works in Kotlin"]
D --> E["Android or JVM example"]
E --> F["Mistakes and interview answer"]

Examples

Safe nullable handling

fun displayName(name: String?): String {
return name?.trim()?.takeIf { it.isNotEmpty() } ?: "Guest"
}

val is not deep immutability

val names = mutableListOf("Asha")
names.add("Riya") // object still changes

When to use it

Use it when: Use nullable types whenever a value can genuinely be absent - an optional profile photo, a search result that might not exist, a network call that failed.

Avoid it when: Avoid marking everything nullable "just in case" - it pushes null checks everywhere and hides which values are actually guaranteed to exist.

Common mistakes

• Using !! to silence compiler warnings
• Thinking val makes a mutable object immutable
• Trusting Java platform types without checks
• Returning null when a sealed result would explain failure
• Smart-casting mutable properties that can change

Interview questions

Read each answer in four parts: simple answer, code example, trade-off, and common mistake.

fun displayName(name: String?): String {
return name?.trim()?.takeIf { it.isNotEmpty() } ?: "Guest"
}

val names = mutableListOf("Asha")
names.add("Riya") // object still changes

fun displayName(name: String?): String {
return name?.trim()?.takeIf { it.isNotEmpty() } ?: "Guest"
}

fun displayName(name: String?): String {
return name?.trim()?.takeIf { it.isNotEmpty() } ?: "Guest"
}

val names = mutableListOf("Asha")
names.add("Riya") // object still changes

Practice task

Write one Kotlin example for Nullable and Non-null Types. Then explain it using: what is it, how it works, where it is used, mistake to avoid, and one interview answer.