Skip to main content

Blog: Composition Made Perfect - Native Class Delegation in Kotlin

Blog: Composition Made Perfect - Native Class Delegation in Kotlin

Day 47! Today I focused on Class Delegation in Kotlin. Every experienced software architect knows the classic design rule: Prefer Composition over Inheritance. While inheritance can look convenient early on, it tightly couples subclasses to parent structures, creating fragile codebases that break easily during refactoring.

The Boilerplate Trap of Composition

To avoid inheritance issues, developers use the Decorator Pattern: your class implements an interface and wraps an internal instance of that same interface, manually forwarding calls.

The downside? If your interface has twenty methods, you have to write twenty tedious forwarding methods yourself. It’s boring, error-prone boilerplate.

The Kotlin Magic: The by Keyword

Kotlin completely eliminates this trade-off by handling delegation natively at the compiler level using the by keyword:

class SmartVehicle(engine: Engine) : Engine by engine

With that single line, the Kotlin compiler automatically generates all necessary forwarding methods behind the scenes! If anyone calls vehicle.getFuelType(), the call is instantly forwarded to the underlying engine instance with zero runtime performance cost.

Flexible Interception

You are never locked into the automated delegation. If you want to change or enrich a specific interface method, you simply write a normal override block inside your class body:

override fun startEngine() {
    println("Performing validation check before starting engine...")
}

The compiler seamlessly routes calls to your custom override for that specific method, while continuing to auto-forward all other unmentioned methods to your delegated target object.

Summary

Class delegation via the by keyword allows developers to achieve the structural safety of composition with the visual simplicity of inheritance, completely eliminating tedious boilerplate code.

Check out the full technical breakdown!

Kotlin #ClassDelegation #Composition #DesignPatterns #CleanCode #AndroidDev #JVM #SoftwareArchitecture

Comments

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 (...

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...
  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 ...