Skip to main content

Blog: Organization is Key - Packages and Imports in Kotlin

Blog: Organization is Key - Packages and Imports in Kotlin

Day 19! Today I looked at the "filing cabinet" system of Kotlin: Packages and Imports.

Beyond the Single File

As projects grow, you can't just keep everything in one place. Kotlin makes it easy to group related functions and classes into packages. But what happens when you have two classes with the same name? In Java, you'd have to use their full names (like com.a.User and com.b.User), which makes the code messy.

The Power of Aliases

Kotlin’s as keyword is a lifesaver. You can import a class and give it a local nickname.

import learn_kotlin.other.Message as OtherMessage

Now I can use Message for my local logic and OtherMessage for the one from the other package. It keeps the code readable and resolves conflicts instantly.

Batteries Included (Again)

I was surprised to learn just how many packages Kotlin imports for you by default. You never have to import kotlin.collections.List because the compiler just assumes you want it. It’s another example of how Kotlin tries to get the "boilerplate" out of your way.

Flexible Structure

One interesting fact: Kotlin doesn't force your package name to match your folder structure. While it's best to keep them aligned, this flexibility can be useful in certain multiplatform or specialized build scenarios.

Summary

Understanding packages and imports is about more than just finding files—it's about designing a clean, conflict-free namespace for your entire application.

Check out the full technical breakdown!

Kotlin #Packages #Imports #CleanArchitecture #CodingTips #JavaToKotlin

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