Kotlin

Generate All Permutations of a String

How to Generate All Permutations of a String in Kotlin — Fast O(n) Approach (Handles Duplicates + Large Input Tips)

When most developers search for Generate All Permutations of a String, they find solutions that work but are often slow, overly complex, or hard to read.

Today, we’re going to cut through the noise and build a simple, fast, and easy-to-understand Kotlin solution that runs in O(n) time per permutation — which is as efficient as it gets.

We’ll cover:

  • What permutations actually are
  • Why naive solutions are slow
  • The O(n) approach using in-place swapping
  • Clean Kotlin code with full explanation

What Is a String Permutation?

A permutation is simply a different arrangement of the same characters.

For example, the string "ABC" has these permutations:

Kotlin
ABC, ACB, BAC, BCA, CAB, CBA

If a string has n unique characters, there are exactly n! permutations.

e.g 4!=4×3×2×1=24

That means 3 characters → 6 permutations, 4 characters → 24 permutations, and so on.

Why We Need an O(n) Approach

Many beginner solutions to generate all permutations of a string use recursion with string concatenation. That works, but it creates a lot of unnecessary string objects in memory — making it slow for larger strings.

We can do better by:

  • Avoiding extra strings (working on a mutable list of characters instead)
  • Swapping in-place to generate permutations
  • Recursing efficiently without repeated slicing or copying

This gives us O(n) work per permutation instead of heavier O(n²) string-building overhead.

The In-Place Swapping Algorithm

Here’s the idea:

  1. Convert the string into a mutable character array.
  2. Recursively swap the current index with each possible next character.
  3. When we reach the end, print or store the permutation.
  4. Swap back to restore the original state (backtracking).

By doing swaps in-place, we avoid creating new arrays or strings at each step.

Kotlin Implementation

Kotlin
fun generateUniquePermutations(str: String) {
    val chars = str.toCharArray().sortedArray() // Sort to group duplicates
    permuteUnique(chars, 0)
}

private fun permuteUnique(chars: CharArray, index: Int) {
    if (index == chars.size - 1) {
        println(String(chars))
        return
    }

    val seen = mutableSetOf<Char>()

    for (i in index until chars.size) {
        if (chars[i] in seen) continue // Skip duplicate characters
        seen.add(chars[i])
        swap(chars, index, i)          // Place chosen char at 'index'
        permuteUnique(chars, index + 1) // Recurse
        swap(chars, index, i)          // Backtrack
    }
}

private fun swap(chars: CharArray, i: Int, j: Int) {
    val temp = chars[i]
    chars[i] = chars[j]
    chars[j] = temp
}

fun main() {
    generateUniquePermutations("AAB")
}

How This Code Works

Let’s break it down:

generatePermutations

  • Converts the input string to a CharArray so we can modify it directly.
  • Starts recursion from the first index.

permute

  • Base case: If index is at the last character, we’ve found a full permutation, so we print it.
  • Loop: Swap the current index with every possible position (including itself).
  • Recursion: Move to the next index and repeat.
  • Backtrack: Swap back so the next iteration starts with the original order.

swap

  • Simple character swap using a temporary variable.
  • Works in constant time O(1).

Time Complexity

This program generates all permutations of a given string.
 If the string length is n:

  • The number of permutations = n!

For each permutation, the code does:

  • A series of swaps (O(1) each)
  • Recursive calls that together visit all permutations.

The total work is proportional to n × n! because:

  • At each permutation, you spend O(n) to print the result (constructing String(chars) is O(n)).
  • The recursive structure ensures we visit all n! permutations.

So:

T(n)=O(n×n!)

Space Complexity

There are two aspects:

Auxiliary space (call stack):

  • The recursion depth is n (one frame for each index position).
  • Each frame holds constant space aside from parameters and local variables.
  • So the recursion stack = O(n).

Extra storage:

  • You store the characters in a CharArray (size n).
  • No extra big data structures are used.
  • Output printing doesn’t count toward auxiliary space complexity (it’s external).

Thus:

S(n)=O(n)

(excluding the space needed for the output itself).

Why This Is O(n) Per Permutation

Each recursive level only requires:

  • One swap (O(1))
  • One swap back (O(1))
  • A constant amount of work for printing or storing

That’s O(n) for each permutation generated, which is optimal — you can’t generate n! permutations faster than that.

Benefits of This Approach

 Fast — avoids extra string copies
 Memory efficient — works in-place
 Readable — short and clear code
 Scalable — handles larger strings without choking your CPU

Output

Running generatePermutations("ABC") gives:

Kotlin
ABC
ACB
BAC
BCA
CBA
CAB

Exactly all possible permutations — no duplicates, no missing ones.

Handling Duplicate Characters

Without extra care, "AAB" will produce duplicate outputs.

To fix this:

  • Sort the characters first so duplicates are adjacent.
  • At each recursion level, use a Set<Char> to skip duplicates.

Kotlin Implementation (Fast + Duplicate-Safe)

Kotlin
fun generateUniquePermutations(str: String) {
    val chars = str.toCharArray().sortedArray() // Sort to group duplicates
    permuteUnique(chars, 0)
}

private fun permuteUnique(chars: CharArray, index: Int) {
    if (index == chars.size - 1) {
        println(String(chars))
        return
    }

    val seen = mutableSetOf<Char>()

    for (i in index until chars.size) {
        if (chars[i] in seen) continue // Skip duplicate characters
        seen.add(chars[i])
        swap(chars, index, i)          // Place chosen char at 'index'
        permuteUnique(chars, index + 1) // Recurse
        swap(chars, index, i)          // Backtrack
    }
}

private fun swap(chars: CharArray, i: Int, j: Int) {
    val temp = chars[i]
    chars[i] = chars[j]
    chars[j] = temp
}

fun main() {
    generateUniquePermutations("AAB")
}

For "AAB", output is:

Kotlin
AAB
ABA
BAA

— unique, no duplicates.

Wait, what if we used all 26 characters? Hmm… actually, let’s just go with 25. 

There are a few limitations we need to talk about.

Limitations & Large Input Handling

Even with an O(n) per permutation algorithm, the total permutations grow as n! (factorial).


 For "ABCDEFGHIJKLMNOPQRSTUWXYZ" (25 characters):

25!≈1.55×10²⁵ permutations

This number is so huge that:

  • You can’t generate all permutations in your lifetime.
  • You can’t store them — it would require trillions of terabytes.
  • Even printing them will eventually cause OutOfMemoryError in the JVM because the output stream and StringBuilder can’t keep up.

How to Avoid Crashes for Large Strings

  1. Generate Lazily (Streaming)
     Use Kotlin sequences to yield one permutation at a time:
Kotlin
fun permutationsSequence(chars: CharArray, index: Int = 0): Sequence<String> = sequence {
    if (index == chars.size - 1) {
        yield(String(chars))
    } else {
        for (i in index until chars.size) {
            swap(chars, index, i)
            yieldAll(permutationsSequence(chars, index + 1))
            swap(chars, index, i)
        }
    }
}

With this, you process each permutation immediately, instead of storing them.

2. Limit Output
 If you just need the first k permutations:

Kotlin
var count = 0
val maxCount = 1000
for (p in permutationsSequence("ABCDEFGHIJKLMNOP".toCharArray())) {
    println(p)
    if (++count >= maxCount) break
}

3. Use Next-Permutation Algorithm
 Instead of generating all permutations at once, generate only the next one on demand — useful for lexicographic iteration without memory blow-up.

Why This Approach Stands Out

O(n) time per permutation — optimal.
Memory-friendly with in-place swaps.
Duplicate-safe.
Large input advice so you don’t crash your program.

Conslusion

If you need to generate all permutations of a string in Kotlin, the in-place swapping method is your best friend for performance and readability. But remember — factorial growth is unavoidable, so for very large strings, think streaming, limiting, or on-demand generation instead of trying to produce everything at once.

With this, you’ve got a production-ready, safe, and scalable solution for permutations in Kotlin.

Fibonacci in Kotlin Using Dynamic Programming

Fibonacci in Kotlin Using Dynamic Programming: The Ultimate Guide

If you’ve ever dived into programming, chances are you’ve come across the famous Fibonacci sequence. It’s a classic problem that teaches us a lot about algorithms and optimization techniques. In this ultimate guide, we’ll explore Fibonacci in Kotlin Using Dynamic Programming in a friendly and easy-to-understand way. Whether you’re a beginner or an experienced Kotlin...

Membership Required

You must be a member to access this content.

View Membership Levels

Already a member? Log in here
Fibonacci Using Loops in Kotlin

Fibonacci Using Loops in Kotlin: A Simple & Efficient Approach

If you’ve just started learning Kotlin and want to practice loops in a real-world example, generating the Fibonacci series is a perfect choice. It’s simple enough to grasp, yet teaches you how to handle variables, loops, and logic in Kotlin efficiently.

In this guide, we’ll explore Fibonacci Using Loops in Kotlin, break down the code step-by-step, and keep it beginner-friendly — without skipping important details.

What is the Fibonacci Sequence?

The Fibonacci sequence is a series of numbers where each number is the sum of the two before it.

It starts like this:

Kotlin
0, 1, 1, 2, 3, 5, 8, 13, 21, 34...

Mathematically:

Kotlin
F(n) = F(n-1) + F(n-2)

Where:

  • F(0) = 0
  • F(1) = 1

Why Use Loops Instead of Recursion?

While recursion can generate Fibonacci numbers, it’s less efficient for large sequences because:

  • It repeats calculations unnecessarily.
  • It uses more memory due to function calls.

Using loops in Kotlin:
 Saves memory.
 Runs faster.
 Easier to understand for beginners.

That’s why Fibonacci Using Loops in Kotlin is both simple and efficient.

Kotlin Program for Fibonacci Using Loops

Here’s the complete Kotlin code:

Kotlin
fun main() {
    val terms = 10  // Number of Fibonacci numbers to print
    var first = 0
    var second = 1

    println("Fibonacci Series using loops:")

    for (i in 1..terms) {
        print("$first ")
        // Calculate the next number
        val next = first + second
        first = second
        second = next
    }
}

Step-by-Step Code Explanation

Let’s break it down so you truly understand:

1. Declaring Variables

Kotlin
fun main() {
    val terms = 10  // Number of Fibonacci numbers to print
    var first = 0
    var second = 1

    println("Fibonacci Series using loops:")

    for (i in 1..terms) {
        print("$first ")
        // Calculate the next number
        val next = first + second
        first = second
        second = next
    }
}
  • terms → how many numbers you want to print.
  • first and second → the first two Fibonacci numbers.

2. Using a Loop

Kotlin
for (i in 1..terms) {
    print("$first ")
    val next = first + second
    first = second
    second = next
}
  • Loop runs from 1 to terms → controls how many numbers are printed.
  • print("$first ") → displays the current number.
  • val next = first + second → calculates the next Fibonacci number.

We then shift the values:

  • first becomes the old second.
  • second becomes the new next.

Not clear — let’s dry run it for better understanding.

Iteration 1 (i = 1)

  • Print first → prints 0
  • next = first + second = 0 + 1 = 1
  • Update:
     first = second = 1
     second = next = 1

Output: 0

Iteration 2 (i = 2)

  • Print first → prints 1
  • next = 1 + 1 = 2
  • Update:
     first = 1
     second = 2

Output: 0 1

Iteration 3 (i = 3)

  • Print first → prints 1
  • next = 1 + 2 = 3
  • Update:
     first = 2
     second = 3

Output: 0 1 1

Iteration 4 (i = 4)

  • Print first → prints 2
  • next = 2 + 3 = 5
  • Update:
     first = 3
     second = 5

Output: 0 1 1 2

Iteration 5 (i = 5)

  • Print first → prints 3
  • next = 3 + 5 = 8
  • Update:
     first = 5
     second = 8

Output: 0 1 1 2 3

Iteration 6 (i = 6)

  • Print first → prints 5
  • next = 5 + 8 = 13
  • Update:
     first = 8
     second = 13

Output: 0 1 1 2 3 5

Iteration 7 (i = 7)

  • Print first → prints 8
  • next = 8 + 13 = 21
  • Update:
     first = 13
     second = 21

Output: 0 1 1 2 3 5 8

Iteration 8 (i = 8)

  • Print first → prints 13
  • next = 13 + 21 = 34
  • Update:
     first = 21
     second = 34

Output: 0 1 1 2 3 5 8 13

Iteration 9 (i = 9)

  • Print first → prints 21
  • next = 21 + 34 = 55
  • Update:
     first = 34
     second = 55

Output: 0 1 1 2 3 5 8 13 21

Iteration 10 (i = 10)

  • Print first → prints 34
  • next = 34 + 55 = 89
  • Update:
     first = 55
     second = 89

Output: 0 1 1 2 3 5 8 13 21 34

Final Output

If terms = 10, output will be:

Kotlin
Fibonacci Series using loops:
0 1 1 2 3 5 8 13 21 34

Tips to Make It Even Better

  • User Input: Instead of hardcoding terms, ask the user how many numbers they want.
Kotlin
print("Enter the number of terms: ")
   
val n = readLine()!!.toInt()
  • Formatting: Add commas or line breaks for readability.
  • Performance: This loop method already runs in O(n) time, making it efficient even for large terms.

Why This Approach Works Well

The Fibonacci Using Loops in Kotlin approach is ideal for:

  • Beginners learning loops.
  • Anyone needing quick and efficient Fibonacci generation.
  • Avoiding recursion stack overflow for large sequences.

It’s clean, easy to debug, and performs well.

Conclusion

The Fibonacci sequence is a timeless example for learning programming logic. By using loops in Kotlin, you get the perfect balance between simplicity and efficiency. Whether you’re practicing for interviews or just improving your coding skills, this method will serve you well.

Next time you think about Fibonacci, remember — you don’t always need recursion. A good old loop can do the job beautifully.

Kotlin Flow

Kotlin Flow vs LiveData: Why Android Developers Are Moving On (And How to Migrate Smoothly)

If you’ve been building Android apps for a few years, you’ve probably written your fair share of LiveData. For a long time, it was the go-to choice for exposing observable data from a ViewModel to the UI. It solved an important problem: lifecycle awareness.

But the Android world has changed. Kotlin coroutines have become the default for async programming, and along with them, Flow and StateFlow have emerged as powerful, coroutine-native reactive streams. Many developers are now replacing LiveData entirely.

In this article, I’ll explain why the shift is happening, what makes Flow and StateFlow better in modern Android development, and give you a practical, code-focused migration guide that won’t break your existing architecture.

LiveData’s Origin and Limitations

LiveData was introduced back in 2017 as part of Android Architecture Components. At that time:

  • Kotlin coroutines were experimental.
  • Most apps used callbacks or RxJava for reactive streams.
  • We needed something lifecycle-aware to avoid leaks and crashes from background updates.

LiveData solved these problems well for the time, but it has some hard limitations:

  • It’s Android-specific (not usable in Kotlin Multiplatform projects).
  • It has very few transformation operators (map, switchMap).
  • Integration with coroutines feels bolted on via adapters.
  • You can’t use it directly in non-UI layers without bringing in Android dependencies.

Why Flow and StateFlow are Taking Over

Flow is platform-agnostic

Flow comes from the kotlinx.coroutines library — meaning it works in Android, server-side Kotlin, desktop apps, and KMP projects. It’s not tied to the Android lifecycle or framework.

Rich operator support

Flow offers powerful operators like map, filter, combine, debounce, retry, flatMapLatest, and more. These allow you to build complex data pipelines with minimal boilerplate.

Kotlin
repository.getUsersFlow()
    .debounce(300)
    .map { users -> users.filter { it.isActive } }
    .flowOn(Dispatchers.IO)
    .collect { activeUsers ->
        // Update UI
    }

Doing this in LiveData would be awkward at best.

Coroutine-native

Flow integrates directly with coroutines:

  • You can collect it in a coroutine scope.
  • Context switching is built in (flowOn).
  • Structured concurrency ensures proper cleanup.

LiveData requires a bridge (asLiveData or liveData {}) to fit into coroutine-based code.

Lifecycle awareness without coupling

While Flow itself isn’t lifecycle-aware, you can make it so with repeatOnLifecycle or launchWhenStarted:

Kotlin
lifecycleScope.launch {
    repeatOnLifecycle(Lifecycle.State.STARTED) {
        viewModel.dataFlow.collect { data ->
            render(data)
        }
    }
}

This cancels the collection automatically when the UI stops, just like LiveData.

Works for hot and cold streams

  • Cold streams: Only emit when collected (default Flow behavior).
  • Hot streams: Always active, emit latest values (StateFlow, SharedFlow).

LiveData is always “hot” and always keeps the last value.

Why Google is Leaning Toward Flow

Many Jetpack libraries have switched to Flow-first APIs:

  • Room: Can return Flow<T> directly.
  • DataStore: Uses Flow for reading values.
  • Paging 3: Exposes Flow<PagingData<T>> as the default.

The trend is clear — Flow is becoming the reactive backbone of Android development.

StateFlow: The Modern LiveData

For most UI state, the direct replacement for LiveData is StateFlow:

  • Always holds a current value (.value).
  • Hot stream — new collectors get the latest value instantly.
  • Fully coroutine-native.

With a small helper like repeatOnLifecycle, you get the same lifecycle safety as LiveData, but with more control and flexibility.

Migration Guide: LiveData → StateFlow

Basic property migration

Before (LiveData):

Kotlin
private val _name = MutableLiveData<String>()
val name: LiveData<String> = _name

After (StateFlow):

Kotlin
private val _name = MutableStateFlow("")
val name: StateFlow<String> = _name

Observing in the UI

Before:

Kotlin
viewModel.name.observe(viewLifecycleOwner) { name ->
    binding.textView.text = name
}

After:

Kotlin
lifecycleScope.launch {
    repeatOnLifecycle(Lifecycle.State.STARTED) {
        viewModel.name.collect { name ->
            binding.textView.text = name
        }
    }
}

Transformations

map:

Kotlin
val upperName: StateFlow<String> =
    name.map { it.uppercase() }
        .stateIn(viewModelScope, SharingStarted.Eagerly, "")

switchMapflatMapLatest:

Kotlin
val user: StateFlow<User?> =
    userId.flatMapLatest { id ->
        repository.getUserFlow(id)
    }.stateIn(viewModelScope, SharingStarted.Lazily, null)

MediatorLiveData → combine

Kotlin
val combined: StateFlow<Pair<String, Int>> =
    combine(name, age) { n, a -> n to a }
        .stateIn(viewModelScope, SharingStarted.Eagerly, "" to 0)

SingleLiveEvent → SharedFlow

Kotlin
private val _events = MutableSharedFlow<String>()
val events: SharedFlow<String> = _events

fun sendEvent(msg: String) {
    viewModelScope.launch { _events.emit(msg) }
}

UI:

Kotlin
lifecycleScope.launch {
    repeatOnLifecycle(Lifecycle.State.STARTED) {
        viewModel.events.collect { showSnackbar(it) }
    }
}

Best Practices

  • Use StateFlow for UI state, SharedFlow for events.
  • Wrap mutable flows in immutable StateFlow/SharedFlow when exposing from ViewModel.
  • Always collect flows inside repeatOnLifecycle in UI components to avoid leaks.
  • For background layers, use Flow freely without lifecycle bindings.

Conclusion

LiveData isn’t “bad” — it still works fine for many apps. But the Android ecosystem has moved on. With coroutines and Flow, you get a unified, powerful, cross-platform reactive framework that covers more cases with less friction.

If you start new projects today, building with Flow and StateFlow from the ground up will keep your architecture modern and future-proof. And if you’re migrating an existing app, the step-by-step transformations above should make it painless.

Fibonacci Sequence in Kotlin Using Recursion

Fibonacci Sequence in Kotlin Using Recursion — From Theory to Code

If you’ve ever been fascinated by numbers that seem to appear everywhere in nature — from the petals of flowers to the spirals in seashells — then you’ve already met the Fibonacci sequence.

In this blog, we’ll explore Fibonacci Sequence in Kotlin Using Recursion step by step. We’ll start with the theory, then move into writing simple yet powerful Kotlin code. Everything will be easy to follow, and beginner-friendly.

Understanding the Fibonacci Sequence

The Fibonacci sequence is a series of numbers where:

Kotlin
F(n) = F(n-1) + F(n-2)

with:

Kotlin
F(0) = 0
F(1) = 1

So, the sequence begins like this:

Kotlin
0, 1, 1, 2, 3, 5, 8, 13, 21, ...

Each term is the sum of the previous two terms. It’s a simple rule with surprisingly deep applications — mathematics, art, computer science, and even stock market analysis.

Why Use Recursion?

Recursion is when a function calls itself to solve smaller parts of a problem.
 In the case of the Fibonacci sequence, recursion works naturally because the definition of Fibonacci is already recursive in nature:

  • To find F(n), you find F(n-1) and F(n-2) and add them.
  • Each of those smaller problems breaks down further until you hit the base case (F(0) or F(1)).

Think of it like climbing stairs:

  • To reach the nth step, you must have come from either step (n-1) or (n-2).
  • You keep breaking it down until you reach the first or second step.

Writing Fibonacci Sequence in Kotlin Using Recursion

Here’s the code:

Kotlin
fun fibonacci(n: Int): Int {
    // Base cases: when n is 0 or 1
    if (n == 0) return 0
    if (n == 1) return 1

// Recursive call
    return fibonacci(n - 1) + fibonacci(n - 2)
}

fun main() {
    val terms = 10

    println("Fibonacci sequence up to $terms terms:")

    for (i in 0 until terms) {
        print("${fibonacci(i)} ")
    }
}

Code Explanation

1. Base Cases

Kotlin
if (n == 0) return 0
if (n == 1) return 1

These are our stopping points. If n is 0 or 1, we simply return the value without further calculations.

2. Recursive Step

Kotlin
return fibonacci(n - 1) + fibonacci(n - 2)

The function calls itself twice:

  • Once for the previous term (n-1)
  • Once for the term before that (n-2)
     It then adds them together to produce the nth term.

3. Main Function

Kotlin
for (i in 0 until terms) {
    print("${fibonacci(i)} ")
}

We loop through and print the first terms Fibonacci numbers, giving us a clean, readable sequence.

A Note on Performance

While Fibonacci Sequence in Kotlin Using Recursion is elegant and easy to understand, pure recursion can be slow for large n because it recalculates the same values multiple times.

Example:

  • fibonacci(5) calls fibonacci(4) and fibonacci(3).
  • But fibonacci(4) again calls fibonacci(3) — we’re repeating work.

Solution: Use memoization or dynamic programming to store results and avoid recalculations. But for learning recursion, the basic approach is perfect.

Real-World Applications

  • Algorithm practice: Great for learning recursion and problem-solving.
  • Mathematical modeling: Growth patterns in populations or financial data.
  • Computer graphics: Spiral designs and procedural patterns.

Key Takeaways

  • The Fibonacci sequence is naturally suited to recursion because of its self-referential definition.
  • Kotlin makes it clean and readable with its concise syntax.
  • For small inputs, recursion works perfectly, but for larger inputs, optimization is needed.

Conclusion

Recursion is like magic — it hides complexity behind a few lines of code. With the Fibonacci Sequence in Kotlin Using Recursion, you get both an elegant algorithm and a deep understanding of how problems can solve themselves step by step.

Use-Site

What Happens If You Don’t Specify a Use-Site Target in Kotlin?

In Kotlin, annotations can target multiple elements of a declaration — such as a field, getter, or constructor parameter. When you apply an annotation without explicitly specifying a use-site target (e.g., @MyAnnotation instead of @field:MyAnnotation), Kotlin tries to infer the most appropriate placement.

This default behavior often works well — but in some cases, especially when interoperating with Java frameworks, it can produce unexpected results. Let’s dive into how it works, and what’s changing with Kotlin 2.2.0.

Default Target Inference in Kotlin (Before 2.2.0)

If the annotation supports multiple targets (defined via its @Target declaration), Kotlin infers where to apply the annotation based on context. This is especially relevant for primary constructor properties.

Kotlin
annotation class MyAnnotation
class User(
    @MyAnnotation val name: String
)

In this case, Kotlin might apply @MyAnnotation to the constructor parameter, property, or field—depending on what @MyAnnotation allows.

Approximate Priority Order:

When multiple targets are applicable, Kotlin historically followed a rough order of priority:

  1. param – Constructor parameter
  2. property – The Kotlin property itself
  3. field – The backing field generated in bytecode

But this is not a strict rule — the behavior varies by context and Kotlin version.

Interop with Java Frameworks: Why Target Matters

Kotlin properties can generate several elements in Java bytecode:

  • A backing field
  • A getter method (and setter for var)
  • A constructor parameter (for primary constructor properties)

Java frameworks (like Jackson, Spring, Hibernate) often look for annotations in specific places — typically on the field or getter. If Kotlin places the annotation somewhere else (e.g., the property), the framework might not recognize it.

Kotlin
class User(
    @JsonProperty("username") val name: String
)

If @JsonProperty is placed on the property instead of the field, Jackson may not detect it correctly. The fix is to use an explicit target:

Kotlin
class User(
    @field:JsonProperty("username") val name: String
)

Kotlin 2.2.0: Refined Defaulting with -Xannotation-default-target

Kotlin 2.2.0 introduces a new experimental compiler flag:

Kotlin
-Xannotation-default-target=param-property

When enabled, this flag enforces a consistent and more predictable defaulting strategy, especially suited for Java interop.

New Priority Order:

  1. param – If valid, apply to the constructor parameter
  2. property – If param isn’t valid, and property is
  3. field – If neither param nor property is valid, but field is
  4. Error — If none of these are allowed, compilation fails

This makes annotation behavior more intuitive, especially when integrating with Java-based tools and frameworks.

The @all: Meta-Target (Experimental)

Kotlin 2.2.0 also introduces the experimental @all: use-site target, which applies an annotation to all applicable parts of a property:

  • param (constructor parameter)
  • property (Kotlin-level property)
  • field (backing field)
  • get (getter)
  • set (setter, if var)

Example:

Kotlin
@all:MyAnnotation<br>var name: String = ""

This is equivalent to writing:

Kotlin
@param:MyAnnotation
@property:MyAnnotation
@field:MyAnnotation
@get:MyAnnotation
@set:MyAnnotation

Only the targets supported in the annotation’s @Target list will be applied.

Best Practices

Here’s how to work with Kotlin annotations effectively:

ScenarioRecommendation
Using annotations with Java frameworksUse explicit use-site targets (@field:, @get:)
Want consistent defaultingEnable -Xannotation-default-target=param-property
Want broad annotation coverageUse @all: (if supported by the annotation)
Unsure where an annotation is being appliedUse the Kotlin compiler flag -Xemit-jvm-type-annotations and inspect bytecode or decompiled Java

Conclusion

While Kotlin’s inferred annotation targets are convenient, they don’t always align with Java’s expectations. Starting with Kotlin 2.2.0, you get more control and predictability with:

  • Explicit use-site targets
  • A refined defaulting flag (-Xannotation-default-target)
  • The @all: meta-target for multi-component coverage

By understanding and controlling annotation placement, you’ll avoid hidden bugs and ensure smooth Kotlin–Java interop.

how to apply annotations in Kotlin

How to Apply Annotations in Kotlin: Best Practices & Examples

Annotations are a powerful feature in Kotlin that let you add metadata to your code. Whether you’re working with frameworks like Spring, Dagger, or Jetpack Compose, or building your own tools, knowing how to apply annotations in Kotlin can drastically improve your code’s readability, structure, and behavior.

In this guide, we’ll walk through everything step by step, using real examples to show how annotations work in Kotlin. You’ll see how to use them effectively, with clean code and clear explanations along the way..

What Are Annotations in Kotlin?

Annotations are like sticky notes for the compiler. They don’t directly change the logic of your code but tell tools (like compilers, IDEs, and libraries) how to handle certain elements.

If you use @JvmStatic, Kotlin will generate a static method that Java can call without needing to create an object. It helps bridge Kotlin and Java more smoothly.?

Kotlin
object Utils {
    @JvmStatic
    fun printMessage(msg: String) {
        println(msg)
    }
}

This makes printMessage() callable from Java without creating an instance of Utils.

How to Apply Annotations in Kotlin

To apply an annotation in Kotlin, you use the @ symbol followed by the annotation’s name at the beginning of the declaration you want to annotate. You can apply annotations to functions, classes, and other code elements. Let’s see some examples:

Here’s an example using the JUnit framework, where a test method is marked with the @Test annotation:

Kotlin
import org.junit.*

class MyTest {
    @Test
    fun testTrue() {
        Assert.assertTrue(true)
    }
}

In Kotlin, annotations can have parameters. Let’s take a look at the @Deprecated annotation as a more interesting example. It has a replaceWith parameter, which allows you to provide a replacement pattern to facilitate a smooth transition to a new version of the API. The following code demonstrates the usage of annotation arguments, including a deprecation message and a replacement pattern:

Kotlin
@Deprecated("Use removeAt(index) instead.", ReplaceWith("removeAt(index)"))
fun remove(index: Int) { ... }

In this case, when someone uses the remove function in their code, the IDE will not only show a suggestion to use removeAt instead, but it will also offer a quick fix to automatically replace the remove function with removeAt. This makes it easier to update your code and follow the recommended practices.

Annotations in Kotlin can have arguments of specific types, such as primitive types, strings, enums, class references, other annotation classes, and arrays of these types. The syntax for specifying annotation arguments is slightly different from Java:

To specify a class as an annotation argument, use the ::class syntax:

When you want to specify a class as an argument for an annotation, you can use the ::class syntax.

Kotlin
@MyAnnotation(MyClass::class)

In this case, let’s say you have a custom annotation called @MyAnnotation, and you want to pass a class called MyClass as an argument to that annotation. In this case, you can use the ::class syntax like this: @MyAnnotation(MyClass::class).

By using ::class, you are referring to the class itself as an object. It allows you to pass the class reference as an argument to the annotation, indicating which class the annotation is associated with.

To specify another annotation as an argument, don’t use the @ character before the annotation name:

when specifying an annotation as an argument for another annotation, you don’t need to use the “@” symbol before the annotation name.

Kotlin
@Deprecated(replaceWith = ReplaceWith("removeAt(index)"))
fun remove(index: Int) { ... }

In the above example, the @Deprecated annotation. It allows you to provide a replacement pattern using the ReplaceWith annotation. In this case, you simply specify the ReplaceWith annotation without the “@” symbol when using it as an argument for @Deprecated .

By omitting the “@” symbol, you indicate that the argument is another annotation.

To specify an array as an argument, use the arrayOf function:

if you want to specify an array as an argument for an annotation, you can use the arrayOf function.

For example, let’s say you have an annotation called @RequestMapping with a parameter called path, and you want to pass an array of strings ["/foo", "/bar"] as the value for that parameter. In this case, you can use the arrayOf function like this:

Kotlin
@RequestMapping(path = arrayOf("/foo", "/bar"))

However, if the annotation class is declared in Java, you don’t need to use the arrayOf function. In Java, the parameter named value in the annotation is automatically converted to a vararg parameter if necessary. This means you can directly provide the values without using the arrayOf function.

To use a property as an annotation argument, you need to mark it with a const modifier:

In Kotlin, annotation arguments need to be known at compile time, which means you cannot refer to arbitrary properties as arguments. However, you can use the const modifier to mark a property as a compile-time constant, allowing you to use it as an annotation argument.

To use a property as an annotation argument, follow these steps:

  1. Declare the property using the const modifier at the top level of a file or inside an object.
  2. Initialize the property with a value of a primitive type or a String.

Here’s an example using JUnit’s @Test annotation that specifies a timeout for a test:

Kotlin
const val TEST_TIMEOUT = 100L

@Test(timeout = TEST_TIMEOUT)
fun testMethod() {
    // Test code goes here
}

In this example, TEST_TIMEOUT is declared as a const property with a value of 100L. The timeout parameter of the @Test annotation is then set to the value of TEST_TIMEOUT. This allows you to specify the timeout value as a constant that can be reused and easily changed if needed.

Remember that properties marked with const need to be declared at the top level of a file or inside an object, and they must be initialized with values of primitive types or String. Using regular properties without the const modifier will result in a compilation error with the message “Only ‘const val’ can be used in constant expressions.”

Best Practices for Using Annotations

Using annotations the right way keeps your Kotlin code clean and powerful. Here are some tips:

1. Use Target and Retention Wisely

  • @Target specifies where your annotation can be applied: classes, functions, properties, etc.
  • @Retention controls how long the annotation is kept: source code only, compiled classes, or runtime.
Kotlin
@Target(AnnotationTarget.FUNCTION)
@Retention(AnnotationRetention.RUNTIME)
annotation class LogExecutionTime

Use RUNTIME if your annotation will be read by reflection.

2. Keep Annotations Lightweight

Avoid stuffing annotations with too many parameters. Use defaults whenever possible to reduce clutter.

Kotlin
annotation class Audit(val user: String = "system")

3. Document Custom Annotations

Treat annotations like part of your public API. Always include comments and KDoc.

Kotlin
/**
 * Indicates that the method execution time should be logged.
 */
@Target(AnnotationTarget.FUNCTION)
@Retention(AnnotationRetention.RUNTIME)
annotation class LogExecutionTime

Example: Logging Execution Time

Let’s say you want to log how long your functions take to execute. You can create a custom annotation and use reflection to handle it.

Kotlin
@Target(AnnotationTarget.FUNCTION)
@Retention(AnnotationRetention.RUNTIME)
annotation class LogExecutionTime

class Worker {
    @LogExecutionTime
    fun doWork() {
        Thread.sleep(1000)
        println("Work done!")
    }
}

Now add logic to read the annotation:

Kotlin
fun runWithLogging(obj: Any) {
    obj::class.members.forEach { member ->
        if (member.annotations.any { it is LogExecutionTime }) {
            val start = System.currentTimeMillis()
            (member as? KFunction<*>)?.call(obj)
            val end = System.currentTimeMillis()
            println("Execution time: ${end - start} ms")
        }
    }
}

fun main() {
    val worker = Worker()
    runWithLogging(worker)
}

This will automatically time any function marked with @LogExecutionTime. Clean and effective.

Advanced Use Case: Dependency Injection with Dagger

In Dagger or Hilt, annotations are essential. You don’t write much logic yourself; instead, annotations do the work.

Kotlin
@Module
@InstallIn(SingletonComponent::class)
object NetworkModule {

    @Provides
    fun provideApiService(): ApiService {
        return Retrofit.Builder()
            .baseUrl("https://api.softaai.com")
            .build()
            .create(ApiService::class.java)
    }
}

Here, @Module, @Provides, and @InstallIn drive the dependency injection system. Once you learn how to apply annotations in Kotlin, libraries like Dagger become far less intimidating.

Conclusion

Annotations in Kotlin are more than decoration — they’re metadata with a purpose. Whether you’re customizing behavior, interfacing with Java, or using advanced frameworks, knowing how to apply annotations in Kotlin gives you a real edge.

Quick Recap:

  • Use annotations to add metadata.
  • Apply built-in annotations to boost interoperability and performance.
  • Create your own annotations for clean, reusable logic.
  • Follow best practices: target, retention, defaults, and documentation.

With the right approach, annotations make your Kotlin code smarter, cleaner, and easier to scale.

@Target in Kotlin

Everything About @Target in Kotlin: What It Is, Why It Matters, and How to Use It

Kotlin is known for being expressive, concise, and fully interoperable with Java. But when working with annotations in Kotlin, especially when defining your own, you might encounter something called @Target. If you’re wondering what @Target in Kotlin is, why it matters, and how to use it effectively—this guide is for you.

Let’s break it down, step-by-step.

What Is @Target in Kotlin?

In Kotlin, @Target is a meta-annotation. That means it’s an annotation used to annotate other annotations. It specifies where your custom annotation can be applied in the code.

For example, can your annotation be used on a class? A function? A property? That’s what @Target defines.

Kotlin uses the AnnotationTarget enum to list all possible valid locations.

Basic Syntax:

Kotlin
@Target(AnnotationTarget.CLASS, AnnotationTarget.FUNCTION)
annotation class MyAnnotation

In this example, MyAnnotation can only be used on classes and functions.

Why @Target in Kotlin Matters

Without @Target, your custom annotation could be misused. Kotlin wouldn’t know where it should or shouldn’t be applied. That could lead to:

  • Confusing code
  • Compilation warnings or errors
  • Unintended behavior, especially when interoperating with Java

By clearly defining usage points, you make your code more maintainable, readable, and safe.

Understanding AnnotationTarget Options

Kotlin gives you a range of options for @Target. Here are the most common ones:

Different options for @Target

You can use more than one if needed:

Kotlin
@Target(AnnotationTarget.CLASS, AnnotationTarget.FUNCTION, AnnotationTarget.CONSTRUCTOR)
annotation class AuditLog

This lets you use @AuditLog on multiple types of declarations.

Example: Creating a Custom Annotation

Let’s say you’re building a system where you want to mark certain functions as “experimental”.

Step 1: Define the Annotation

Kotlin
@Target(AnnotationTarget.FUNCTION)
@Retention(AnnotationRetention.RUNTIME)
annotation class ExperimentalFeature(val message: String = "This is experimental")
  • @Target(AnnotationTarget.FUNCTION): Only allows this annotation on functions.
  • @Retention(RUNTIME): Keeps the annotation at runtime (optional but useful).

Step 2: Use the Annotation

Kotlin
@ExperimentalFeature("Might be unstable in production")
fun newAlgorithm() {
    println("Running experimental algorithm...")
}

Step 3: Read the Annotation at Runtime (Optional)

Kotlin
fun checkExperimentalAnnotations() {
    val method = ::newAlgorithm
    val annotation = method.annotations.find { it is ExperimentalFeature } as? ExperimentalFeature

    if (annotation != null) {
        println("Warning: ${annotation.message}")
    }
}

This prints:

Kotlin
Warning: Might be unstable in production

Tips for Using @Target in Kotlin

  1. Be specific: The more targeted your annotation, the less chance of misuse.
  2. Use multiple targets wisely: Don’t overgeneralize.
  3. Pair with @Retention: Decide whether your annotation should be available at runtime, compile time, or source level.
  4. Think Java Interop: If you’re interoperating with Java, know that @Target in Kotlin maps to @Target in Java too.

Conclusion

@Target in Kotlin is more than just a syntactic detail. It controls how annotations behave, where they’re valid, and how your tools (including the compiler and IDE) handle them.

If you’re building libraries, frameworks, or just want clean annotation usage, understanding @Target in Kotlin is essential. With the right @Target settings, your custom annotations stay safe, purposeful, and powerful.

Kotlin annotations

Kotlin Annotations 101: Learn the Basics in Under 10 Minutes

New to Kotlin and wondering what the @ symbol means? That symbol introduces Kotlin annotations — a simple yet powerful feature that adds useful metadata to your code, making it smarter, cleaner, and easier to manage.

This quick guide will show you what Kotlin annotations are, why they matter, and how to use them effectively. No complex jargon, just the essentials — all in under 10 minutes.

What Are Kotlin Annotations?

Annotations in Kotlin are a way to attach metadata to code elements such as classes, functions, properties, and parameters. Metadata is like extra information about the code that can be used by the compiler, libraries, or even runtime frameworks.

Think of Kotlin annotations as digital sticky notes. They’re not actual instructions for logic, but they tell tools how to treat your code.

Kotlin
@Deprecated("Use newFunction() instead", ReplaceWith("newFunction()"))
fun oldFunction() {
    println("This function is deprecated.")
}

Here,

  • @Deprecated tells both the developer and the compiler that oldFunction() shouldn’t be used.
  • ReplaceWith("newFunction()") offers a suggestion.

Pretty straightforward, right?

Why Use Kotlin Annotations?

Kotlin annotations let you:

  • Communicate intent clearly (e.g., deprecate functions)
  • Influence compiler behavior
  • Hook into frameworks like Android or Spring
  • Enable code generation tools

They’re also essential when working with Java interoperability, which is a key strength of Kotlin.

Built-in Kotlin Annotations You Should Know

1. @Deprecated

Used to mark something as outdated.

Kotlin
@Deprecated("Don't use this")
fun oldApi() {}

2. @JvmStatic

Useful when writing Kotlin code that will be used from Java.

Kotlin
companion object {
    @JvmStatic
    fun create() = MyClass()
}

This makes create() callable as a static method from Java.

3. @JvmOverloads

Generates Java-compatible overloads for functions with default parameters.

Kotlin
@JvmOverloads
fun greet(name: String = "World") {
    println("Hello, $name")
}

Java doesn’t support default arguments natively, so this helps bridge the gap.

4. @Target

Specifies where an annotation can be used (e.g., class, property, function).

Kotlin
@Target(AnnotationTarget.CLASS)
annotation class MyAnnotation

5. @Retention

Defines how long the annotation is kept: source, binary, or runtime.

Kotlin
@Retention(AnnotationRetention.RUNTIME)
annotation class Loggable

Runtime retention means reflection tools can access this annotation at runtime.

How to Create Your Own Kotlin Annotations

Creating custom Kotlin annotations is easy.

Kotlin
@Target(AnnotationTarget.FUNCTION)
@Retention(AnnotationRetention.RUNTIME)
annotation class LogExecutionTime

This annotation can now be used on functions where you want to measure execution time.

Kotlin
@LogExecutionTime
fun performTask() {
    // Some logic here
}

Of course, this is just a tag. You’d need reflection or an AOP (Aspect-Oriented Programming) tool to act on it.

Kotlin Annotations in Android Development

In Android, Kotlin annotations are everywhere. A few you’ve probably seen:

  • @UiThread, @MainThread, @WorkerThread — indicate expected thread usage.
  • @Nullable and @NonNull — help with null safety, especially in Java interop.
  • @Parcelize — works with Kotlin’s Parcelize plugin to simplify Parcelable implementation.
Kotlin
@Parcelize
data class User(val name: String, val age: Int) : Parcelable

This eliminates boilerplate, making Android dev smoother.

Best Practices When Using Kotlin Annotations

  • Be intentional. Don’t slap annotations on everything. Know what they do.
  • Check retention policies. Source-retained annotations won’t be available at runtime.
  • Avoid clutter. Annotations should clarify, not complicate.
  • Test interop. If you’re writing code to be used in Java, test how annotations behave.

Conclusion

Kotlin annotations might seem like just extra syntax, but they play a powerful role in shaping how your code behaves, communicates, and integrates with other systems.

They reduce boilerplate, enforce contracts, and help the compiler help you.

Whether you’re building Android apps, writing libraries, or just learning the ropes, understanding Kotlin annotations will make you a stronger, more fluent Kotlin developer.

Unit Testing in Kotlin

How to Do Unit Testing in Kotlin Like a Google Engineer

Unit testing in Kotlin isn’t just about making sure your code works. It’s about writing tests that prove your code works, stays reliable over time, and catches bugs before they hit production. Google engineers treat testing as a core development skill, not an afterthought. And you can do the same.

In this guide, we’ll break down unit testing in Kotlin in a simple way. We’ll show you how to write clean, maintainable tests just like a pro. Whether you’re building Android apps or server-side Kotlin applications, this blog will give you the confidence to write bulletproof unit tests.

What is Unit Testing in Kotlin?

Unit testing is the process of testing individual units of code (like functions or classes) in isolation to ensure they work as expected. Unlike integration or UI tests, unit tests focus on your own logic, not external libraries or frameworks.

Unit Test is a piece of code that is not a part of your application. It can create and call all of your application’s public classes and methods… You want to verify whether application code works as you expect.

Why Google Engineers Prioritize Unit Testing

  • Fast feedback: Tests run in milliseconds. You catch bugs fast.
  • Safe refactoring: When you change code, tests confirm nothing breaks.
  • Confidence in deployment: You ship faster because you trust your code.
  • Documents behavior: Tests show how code is supposed to work.

Now let’s get to the fun part — how to actually do this in Kotlin.

Setting Up Unit Testing in Kotlin

Most Kotlin projects use JUnit as the test framework. Android Studio and IntelliJ IDEA make setup easy:

1. Add JUnit to your project dependencies (usually already included in Android projects). Use JUnit5 for unit testing in Kotlin. It’s modern, fast, and integrates well.

Kotlin
dependencies {
    testImplementation("org.junit.jupiter:junit-jupiter:5.10.0")
    testImplementation("org.jetbrains.kotlin:kotlin-test:1.9.0")
}

test {
    useJUnitPlatform()
}

2. Create a test class for the code you want to test.

3. Write test methods using the @Test annotation.

Basic Unit Test in Kotlin

Let’s say you have a function that adds two numbers:

Kotlin
fun add(a: Int, b: Int): Int = a + b

Here’s how you write a test for it:

Kotlin
import org.junit.jupiter.api.Assertions.*
import org.junit.jupiter.api.Test

class MathUtilsTest {
    @Test
    fun `add should return sum of two numbers`() {
        val result = add(3, 4)
        assertEquals(7, result)
    }
}

What’s happening here?

  • @Test marks the method as a test case.
  • assertEquals checks the expected and actual values.
  • The function name is written in backticks for clarity.

Best Practices for Unit Testing in Kotlin

Google engineers follow these principles to ensure effective unit testing in Kotlin:

1. Keep Tests Small and Focused

Each test should verify one behavior or scenario. This makes tests easy to read and maintain.

2. Use Immutable Test Data

Initialize objects as val and avoid mutating shared state between tests. This prevents flaky tests and makes debugging easier.

3. Leverage Kotlin Features

Kotlin’s concise syntax (like data classes and extension functions) makes tests more readable and expressive.

4. Test Lifecycle Annotations

  • @Before: Setup code before each test.
  • @After: Cleanup after each test.
  • @TestInstance(Lifecycle.PER_CLASS): Reuse test class instance for all tests (avoids static members).

5. Mock Dependencies

Use libraries like MockK or Mockito to replace dependencies with mock objects, so you only test your own code’s logic.

Testing with Mocks in Kotlin

Sometimes, your code depends on external systems (like APIs or databases). For true unit testing in Kotlin, you should mock those dependencies.

Use MockK — a Kotlin-first mocking library.

Add MockK to Your Project

Kotlin
dependencies {
    testImplementation("io.mockk:mockk:1.13.8")
}

Example with MockK

Kotlin
interface UserRepository {
    fun getUser(id: Int): String
}

class UserService(private val repository: UserRepository) {
    fun getUsername(id: Int): String = repository.getUser(id).uppercase()
}

class UserServiceTest {
    private val repository = mockk<UserRepository>()
    private val service = UserService(repository)
    @Test
    fun `getUsername returns uppercased username`() {
        every { repository.getUser(1) } returns "amol"
        val result = service.getUsername(1)
        assertEquals("AMOL", result)
    }
}

Key Points

  • mockk<UserRepository>() creates a mock object.
  • every { ... } returns ... defines behavior for the mock.
  • Test checks the result of the service method in isolation.

Testing Coroutines in Kotlin

Kotlin’s coroutines make asynchronous code easier, but they require special handling in tests.

Example: Testing a Coroutine Function

Suppose you have:

Kotlin
suspend fun fetchData(): String {
    delay(1000) // Simulate network call
    return "Data"
}

Test with runBlocking:

Kotlin
import kotlinx.coroutines.runBlocking
import org.junit.Test
import org.junit.Assert.assertEquals

class DataFetchTest {
    @Test
    fun fetchDataReturnsCorrectValue() = runBlocking {
        val result = fetchData()
        assertEquals("Data", result)
    }
}

Tips:

  • Use runBlocking to execute suspending functions in tests.
  • For more advanced coroutine testing, use CoroutineTestRule and TestCoroutineDispatcher to control coroutine execution and skip delays.

Running and Maintaining Tests

  • Run tests frequently: Use your IDE or command line to run all tests after every change.
  • Fix failing tests immediately: Don’t ignore red tests.
  • Refactor tests as needed: Keep them clean and up-to-date as your code evolves.

Tips for Writing Great Unit Tests

  1. Name tests clearly: Describe what the test checks.
  2. Test one thing at a time: Keep tests focused.
  3. Keep tests fast: No real network/database.
  4. Avoid logic in tests: Use literal values.
  5. Use setup methods for repetitive boilerplate.

Common Mistakes to Avoid

  • Testing too much in one test
  • Using real APIs in unit tests
  • Not asserting outcomes
  • Ignoring failed tests
  • Skipping tests because “it works on my machine

Conclusion

Unit Testing in Kotlin isn’t just for Google engineers — it’s a superpower for every developer. By writing small, focused tests, leveraging Kotlin’s features, and using the right tools, you’ll catch bugs early and build robust applications with confidence. 

Start small, keep practicing, and soon unit testing will be second nature..!

error: Content is protected !!