# Announcing Landscapist Core: A New Image Loading Library for Android & Compose Multiplatform

DevFeed: [Announcing Landscapist Core: A New Image Loading Library for Android & Compose Multiplatform](<https://devfeed.tech/articles/announcing-landscapist-core-a-new-image-loading-library-for-android-compose-multiplatform-25918.md>)

Original publisher: [Read original article](<https://proandroiddev.com/announcing-landscapist-core-a-new-image-loading-library-for-android-compose-multiplatform-6a4f408cba00?source=rss-9bb203a4ab2e------2>)

Author: Jaewoong Eum

Published: 2026-01-04T09:21:25Z

Content type: release

Language: en

Sources: [Stories by Jaewoong Eum on Medium](<https://devfeed.tech/sources/stories-by-jaewoong-eum-on-medium.md>)

Topics: [Kotlin Multiplatform](<https://devfeed.tech/topics/kotlin-multiplatform.md>), [compose-multiplatform](<https://devfeed.tech/topics/compose-multiplatform.md>), [Library](<https://devfeed.tech/topics/library.md>), [cross-platform](<https://devfeed.tech/topics/cross-platform.md>), [Android](<https://devfeed.tech/topics/android.md>), [ui](<https://devfeed.tech/topics/ui.md>), [Mobile](<https://devfeed.tech/topics/mobile.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [code](<https://devfeed.tech/tags/code.md>), [compose](<https://devfeed.tech/tags/compose.md>), [compose-multiplatform](<https://devfeed.tech/tags/compose-multiplatform.md>), [cross-platform](<https://devfeed.tech/tags/cross-platform.md>), [jetpack-compose](<https://devfeed.tech/tags/jetpack-compose.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [kotlin-multiplatform](<https://devfeed.tech/tags/kotlin-multiplatform.md>), [library](<https://devfeed.tech/tags/library.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [multiplatform](<https://devfeed.tech/tags/multiplatform.md>), [ui](<https://devfeed.tech/tags/ui.md>)

## AI overview

The article introduces Landscapist Core, a standalone Kotlin Multiplatform image-loading engine, along with Landscapist Image, its Compose Multiplatform UI companion. It explains the libraries' goal of providing consistent image loading across Android, iOS, Desktop, and Wasm without duplicated or platform-specific implementations.

## Source excerpt

Unsplash@britishlibrary Image loading has always been a fundamental challenge in mobile and cross-platform development. While Android developers have relied on battle-tested libraries like Glide, Coil, and Fresco for years, the rise of Kotlin Multiplatform has created a gap: how do you load images consistently across Android, iOS, Desktop, and Wasm without duplicating code or depending on platform-specific solutions? This is precisely the problem Landscapist Core solves. In this article, you'll explore the architecture behind Landscapist Core, a standalone Kotlin Multiplatform image loading engine, and Landscapist Image, its Compose Multiplatform UI companion. You'll examine the design decisions that make this library exceptionally lightweight, understand how it achieves cross-platform consistency, and learn practical patterns for integrating it into your applications. Whether you're building a consumer app or a library/SDK that needs to minimize its footprint, understanding Landscapist's approach offers valuable insights into modern image loading architecture. If you want to deeply explore the how and why behind Kotlin, from core language fundamentals and internal mechanisms to API design, check out Practical Kotlin Deep Dive, a new Kotlin book by this author. Practical Kotlin Deep Dive | Master Kotlin, Coroutines, Flow & Multiplatform The problem with existing solutions Before diving into Landscapist Core, it's worth understanding why a new image loading library is needed when mature solutions already exist. When Compose Multiplatform emerged as a serious cross-platform UI framework, the image loading story remained fragmented. Developers cobbled together solutions: Glide/Coil on Android, platform-specific loaders elsewhere, or custom implementations that duplicated effort. This has been a long-standing item on my TODO list since the initial launch of the Landscapist library in 2020. Over time, I found myself looking for: A unified solution: consistent APIs and be