Skip to main content

Blog: Organizing Data with Kotlin Collections

Blog: Organizing Data with Kotlin Collections

Day 4! Today was all about Collections. Coming from a Java background, I was pleasantly surprised by how Kotlin handles Lists, Sets, and Maps.

The Power of "No"

The biggest shift in mindset is Kotlin's default stance on mutability. In Java, most collections are mutable by default. In Kotlin, you start with listOf(), setOf(), or mapOf(), which are read-only.

If you want to add or remove things, you have to explicitly ask for a mutableListOf(). This small change makes code much safer—if a function receives a List, you know for a fact it won't change under your feet!

Clean Syntax

Look at how maps are created:

val menu = mapOf(
    "Coffee" to 2.50,
    "Tea" to 2.00
)

The to keyword is so much more readable than traditional .put() calls.

Unique is Easy

I love how Sets automatically handle duplicates. setOf("apple", "apple", "banana") just gives you a set with one apple and one banana. No manual checking required.

Interop Check

Once again, calling these from Java was a breeze. Kotlin's List maps directly to java.util.List, and CollectionsKt makes the top-level functions accessible without any friction.

My project is starting to look like a real Kotlin library!

Kotlin #Collections #CleanCode #JavaInterop #LearningKotlin

Labels:

Comments

Post a Comment

Popular posts from this blog

Mastering Per-App Language Preferences: From Android 10 to Android 13+

  One of the most requested features by users is the ability to use an app in a language different from the system language. While Android 13 (API 33) introduced "Per-App Language" settings at the system level, implementing this backward-compatibly for older devices like Android 10 (API 29) used to be a challenge involving manual configuration wrapping. Today, thanks to AppCompat 1.6.0+ , we have a unified, standard way to handle this. Here is the modern guide to implementing seamless language switching. The Architecture: How it Works On Android 13 and above, the system handles the storage and application of your app's locale. On older versions, the AppCompat library manages this behavior by storing your preference in an internal XML file and injecting the resources during the activity lifecycle. Step 1: The Locale Helper Utility Instead of scattering logic across your app, use a clean LocaleHelper object. This handles the distinction between the system LocaleManager (...
Post a Comment
Read more

Beyond Scanning: Meet the All-in-One AI Document Assistant by Digitify Vision Technology

In an era where efficiency is the ultimate currency, information is scattered everywhere—on physical paper, within QR codes, and inside lengthy digital documents. The challenge isn't just capturing this data; it’s making it work for you. At Digitify Vision Technology , we believe your smartphone should be more than just a camera—it should be a high-performance engine for your daily workflow. Today, we are proud to unveil our most powerful update yet: a total evolution in AI-driven document management. 💡 Key Features of the New Update We’ve bridged the gap between physical information and digital action by integrating advanced vision and audio intelligence into a single, seamless experience. 🔍 Precision Scanning for Everything Our advanced vision engine is now more versatile than ever. Intelligent Document Scanning: Capture crisp, professional-grade scans of physical papers, contracts, or handwritten notes. QR Code Extraction: Instantly scan any QR code to extract text, read URL...
Post a Comment
Read more
  Optimising Android Launch: Mastering App Startup & The Modern Splash Screen The first few seconds of an app’s life determine a user's first impression. A slow start or a flickering white screen can lead to immediate uninstalls. In this guide, we’ll look at how to streamline your initialisation using the App Startup Library and ensure a seamless visual transition with the Android 12 Splash Screen API (with full backward compatibility for API 29). Part 1: The App Startup Library Traditionally, apps initialised multiple components using separate content providers. This adds overhead and slows down launch time. The Jetpack App Startup library allows all components to share a single content provider, significantly improving performance. Why use it? Performance: Shared content provider reduces overhead. Order: Explicitly set the initialisation sequence. Simplicity: Both library creators and app developers use a unified interface. Part 2: The Modern Splash Screen API Starting ...
Post a Comment
Read more