Let’s Talk About Collections — a Love Story of Grouped Things

Let’s Talk About Collections — a Love Story of Grouped Things

If you’ve ever tried organizing your life with a to-do list (and failed), congratulations — you already understand the spirit of collections in programming. They're just a way to group things together. Sometimes they’re long and messy. Sometimes they’re short and sweet. And sometimes... they’re just plain empty (like your motivation on a Monday morning).

But in Kotlin? Collections come with structure, behavior, and some fancy rules.


LIST: The Overachieving Sibling

A List is like your arranged Spotify playlist — everything’s in order, and you can play your favorite song by number.

  • Ordered: Items stay exactly where you put them.

  • Indexed: Want the third item? Ask for it by number.

  • Duplicates allowed: If you like “Halo By Beyonce” three times, go ahead. Nobody’s judging.

Oh, and yes — it’s immutable, so if you want to change it, you’re out of luck. (But don’t worry, we’ll get to mutable lists soon.)


SET: The “No Duplicates Allowed” Bouncer

Imagine a nightclub that only lets in unique guests. That’s a Set.

  • No duplicates: One “blue” per list, please.

  • No order: It doesn’t care who came first.

  • Iterable: You can still loop through it. Just don’t expect a neat line.

Think of it like a deck of cards: there may be an Ace of Spades, but there aren’t two.


MAP: The Keymaster

A Map is your digital address book. You’ve got names (keys), and each name leads to a phone number (value).

  • 🔑 Keys are unique

  • 💬 Values can repeat

  • 🧭 Order? Depends on the type of map.

You can think of a Map as a dictionary. Just... less likely to get dusty on a shelf.


Mutable vs Immutable: Choose Your Fighter

Kotlin draws a line in the sand: either your collection can change (mutable) or it can’t (immutable). No flip-flopping.

  • Immutable: ❌ Can’t add or remove elements

  • Great for fixed data you don’t want changed

  • Mutable: ✅ Can add and remove elements

  • Perfect when your list needs to grow or shrink

  • Immutable: ❌ Can’t add or remove elements

  • Ensures uniqueness, but stays as-is once created

  • Mutable: ✅ Can add and remove elements

  • Combines uniqueness with flexibility


ARRAYLIST: Your Go-To Mutable Buddy

Need to change things up? ArrayList is your best friend.

You can also remove entire groups:

Want to replace an item?

Need a break from everything?


LIST FUNCTIONS (a.k.a. Your Toolkit)

  • – How many items are we talking?

  • – Is “pen” hiding in there?

  • – Got the full checklist?

For , you get some bonus features:

  • – Grab a slice of the list.

  • – Swap one item for another.

  • – Feeling empty today?


ITERATORS: The Collection Whisperer

Iterators walk through your collection, one step at a time. They’re polite, predictable, and never skip anyone. Whether it’s a List, Set, or Map — if it's iterable, it’s loopable.


In Closing: Collections Aren’t Just Containers

They’re smart, flexible (when you want them to be), and make your code cleaner, faster, and less likely to throw a tantrum (unless you try accessing index 300 on a 5-item list — don’t do that).

Whether you're organizing words, colors, or chaos — Kotlin’s collections have got your back.

To view or add a comment, sign in

Others also viewed

Explore topics