# Coroutines Coroutines are suspendable computations used to write concurrent, asynchronous code that can suspend without blocking a thread. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## How Kotlin Flow Operator Fusion Works and When Ordinary Operators Break It DevFeed: [How Kotlin Flow Operator Fusion Works and When Ordinary Operators Break It]() Original publisher: [Read original article]() Author: Majidshahbaz Published: 2026-09-13T05:43:21Z Content type: article Language: en Sources: [ProAndroidDev - Medium]() Topics: [kotlin-flow](), [Coroutines](), [Code]() Tags: [android](), [code](), [coroutines](), [jetpack-compose](), [kotlin](), [kotlin-coroutines](), [kotlin-flow]() ### AI overview This article investigates Kotlin Flow operator fusion by instrumenting the runtime and comparing pipelines with adjacent fusible operators against pipelines interrupted by an ordinary map() call. It explains that adjacent channelFlow, flowOn, buffer, and produceIn calls can share one underlying channel through FusibleFlow, while an intervening non-fusible operator causes additional wrapper structure. ### Source excerpt Image Generated for the ArticleI Counted Every Hidden Channel Kotlin Flow Creates -- Most Devs Are Wrong About Which Operators Are Freebuffer() and flowOn() are supposed to fuse into one channel when chained. I wrote code to prove it -- and then found four "harmless" operators that quietly break it. Ask any experienced Kotlin developer what happens when you chain .buffer().flowOn(Dispatchers.IO).buffer(), and you'll usually get a confident answer: "it fuses into one channel." That's the folklore, repeated in talks, docs, and Stack Overflow answers. It's also only half true, and nobody seems to have actually checked the other half: which everyday operators quietly stop that fusion from happening. I decided to stop trusting folklore and instrument the actual runtime. Five separate experiments later, I had a very clear, very measurable answer -- and one of the results genuinely surprised me. The Myth, and the Mechanism Behind It Kotlin's coroutines library really does fuse adjacent channelFlow, flowOn, buffer, and produceIn calls into a single underlying channel instead of creating one per operator. This isn't a rumor -- it's real, deliberate behavior, implemented through an interface called FusibleFlow. Here's the actual check, straight from the source: https://medium.com/media/1cd3b407c1f2b2955b3df4be68ca18b5/href When flowOn() or buffer() is called, it checks whether the flow it's being called on already implements FusibleFlow. If it does, instead of wrapping it in a new object, it calls .fuse() -- which updates the existing object's settings (buffer size, dispatcher) in place. No new object. No new coroutine. No new channel. But that check only succeeds if the upstream is already a ChannelFlow. And that's where the folklore quietly stops being true. Building Something to Actually Measure This I wrote two nearly identical pipelines -- one where the fusible operators sit directly next to each other, and one where a completely ordinary map() sits in the middle: https://medi ## Introducing worker topologies for self-hosted Appwrite DevFeed: [Introducing worker topologies for self-hosted Appwrite]() Original publisher: [Read original article]() Author: Atharva Deosthale Published: 2026-09-07T00:00:00Z Content type: release Language: en Sources: [Appwrite Blog]() Topics: [Appwrite](), [Self-hosted](), [Containers](), [Coroutines](), [Docker Compose]() Tags: [announcements](), [compose](), [container](), [containers](), [coroutines](), [self-hosted]() ### AI overview Appwrite introduces two worker topologies for self-hosted instances. The combined topology is now the default and runs background work in two containers, while the separate topology preserves one container per queue and scheduler for installations needing independent scaling or resource controls. ### Source excerpt Self-hosted Appwrite now runs all background workers in a single container by default. Learn how the combined topology works and when to scale out with separate workers. ## WorkOS announces Agent Registration, Airlock, Relay, and native iOS and Android SDKs DevFeed: [WorkOS announces Agent Registration, Airlock, Relay, and native iOS and Android SDKs]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-09-02T00:00:00Z Content type: release Language: en Sources: [WorkOS Blog]() Topics: [SDKs](), [Android](), [iOS](), [Authorization](), [Mobile](), [Claude](), [Kotlin](), [Swift](), [MCP](), [Coroutines](), [Claude Code](), [codex]() Tags: [agent](), [android](), [api](), [authorization](), [await](), [claude](), [claude-code](), [coroutines](), [ios](), [kotlin](), [maven-central](), [mcp](), [sdks](), [swift](), [updates]() ### AI overview WorkOS announces August updates including Agent Registration for scoped, short-lived credentials, Airlock for authorizing AI-agent actions, Relay for proxying third-party application requests, and native Swift and Kotlin SDKs for iOS and Android. ### Source excerpt Agent Registration, Airlock, Relay, iOS & Android SDKs, & more ## Hyperloop B: the coroutine engine behind Appwrite 2.0 DevFeed: [Hyperloop B: the coroutine engine behind Appwrite 2.0]() Original publisher: [Read original article]() Author: Luke B. Silver Published: 2026-08-31T00:00:00Z Content type: article Language: en Sources: [Appwrite Blog]() Topics: [Appwrite](), [Coroutines](), [Concurrency](), [PHP](), [Benchmark]() Tags: [architectures](), [backend](), [benchmark](), [concurrency](), [coroutine](), [coroutines](), [cpu](), [memory](), [php](), [platform](), [process](), [redis]() ### AI overview The article explains Hyperloop B, a coroutine-based engine behind Appwrite 2.0. It describes how yielding during I/O lets one process serve many concurrent requests, reporting 7x higher requests per second and 6x lower memory use on an I/O-bound benchmark. ### Source excerpt Hyperloop B is the Swoole coroutine engine behind Appwrite 2.0. Here is what it is, the concurrency problem it solves, and the 7x I/O throughput it buys. ## Native Async/Coroutine Reads in RocksDB DevFeed: [Native Async/Coroutine Reads in RocksDB]() Original publisher: [Read original article]() Author: Josh Kang Published: 2026-08-24T00:00:00Z Content type: release Language: en Sources: [RocksDB]() Topics: [rocksdb](), [Coroutines](), [C++](), [IO](), [API]() Tags: [async](), [asynchronous](), [blog](), [c-plus-plus](), [coroutine](), [io](), [native](), [rocksdb](), [thread]() ### AI overview RocksDB introduces experimental asynchronous Get and MultiGet APIs backed by native C++ coroutines. The APIs can suspend storage-bound reads, allowing a small executor to run other ready tasks and maintain more storage queue depth without one blocked application thread per read. The feature targets throughput for I/O-bound point lookups rather than reducing individual device-read latency. ### Source excerpt A point lookup that misses RocksDB's block cache can spend most of its time waiting for storage. The traditional way to keep more reads in flight is to add threads. That works, but each outstanding read parks a thread, carries a stack, and adds context-switching overhead. RocksDB now has experimental asynchronous Get and MultiGet APIs backed by native C++ coroutines. When a read reaches storage, RocksDB can suspend the request, let its read-executor worker run another ready task, and resume the request when the filesystem reports completion. A small executor can therefore maintain more storage queue depth without requiring one blocked application thread per read. These APIs are available in RocksDB 11.10.0. This is primarily a throughput feature for I/O-bound point lookups. It does not make an individual device read faster. Its benefit comes from keeping the device busy and using CPU threads for runnable work. The API surface RocksDB exposes the new read path through two public interfaces: DB::GetAsync and DB::MultiGetAsync return immediately on the native path and report completion through AsyncCallback::OnComplete. CoroDB::CoGet and CoroDB::CoMultiGet return lazy folly::coro::Task objects. CoGet produces a Status; CoMultiGet fills the same per-key values and statuses as synchronous MultiGet. The callback APIs suit applications that do not expose Folly tasks at their boundaries. The CoroDB APIs let coroutine-based callers await RocksDB directly, avoiding an application-side callback-to-Baton adapter and its extra completion handoff. Native execution requires RocksDB to be built with Folly and USE_COROUTINES=1. Neither interface requires ReadOptions::async_io. That flag continues to control the older internal async-I/O optimizations for synchronous MultiGet and iterators. The task APIs are lazy: no read begins until a task is awaited or started. Both interfaces take pointer and reference parameters, so keep the DB, column-family handles, ReadOptions, keys and their ## Add sign-in to an Android app with the WorkOS Android SDK DevFeed: [Add sign-in to an Android app with the WorkOS Android SDK]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-08-24T00:00:00Z Content type: tutorial Language: en Sources: [WorkOS Blog]() Topics: [Android](), [SDKs](), [Kotlin](), [Authentication](), [pkce](), [Gradle](), [Coroutines](), [API keys](), [Security](), [Maven Central](), [Mobile]() Tags: [android](), [api](), [api-keys](), [authentication](), [coroutines](), [flow](), [gradle](), [kotlin](), [maven-central](), [pkce](), [sdk](), [security](), [sign-in](), [tutorial]() ### AI overview This tutorial shows how to add WorkOS AuthKit sign-in to a Kotlin Android app using the WorkOS Android SDK. It covers the Gradle dependency, Chrome Custom Tab authentication, custom-scheme redirects, PKCE token exchange, session storage and refresh, and logout without embedding a client secret in the APK. ### Source excerpt Build a complete AuthKit flow in Kotlin, from Gradle dependency to signed-out state, with no client secret in your APK. ## Coroutine Essentials DevFeed: [Coroutine Essentials]() Original publisher: [Read original article]() Author: author@typealias.com (Dave Leeds) Published: 2026-08-21T00:00:00Z Content type: tutorial Language: en Sources: [Dave Leeds on Kotlin - typealias.com]() Topics: [Coroutines](), [Kotlin](), [coding](), [Software]() Tags: [async](), [cancellation](), [coding](), [concurrency](), [coroutine](), [coroutines](), [deferred](), [dispatcher](), [exception-handling](), [introduction](), [job](), [kotlin](), [launch](), [learn-to-program](), [parallelism](), [programming](), [runblocking](), [software](), [structured-concurrency](), [suspend-function](), [withcontext](), [yield]() ### AI overview This tutorial introduces essential Kotlin coroutine concepts for performing multiple tasks concurrently, such as making network calls while updating a screen. It aims to provide a foundation for day-to-day coding and more advanced coroutine concepts. ### Source excerpt When you're on hold during a phone call, you might also check your email. While brewing coffee, you might also cook breakfast. And while driving a car, you might listen to a podcast. In the same way, sometimes it's helpful for the software that we write to do more than one thing at a time. For example, it could make two or three network calls at one time--all while updating the screen to show the progress of each call. ## How R8 made Kotlin Coroutines on Android 2x faster DevFeed: [How R8 made Kotlin Coroutines on Android 2x faster]() Original publisher: [Read original article]() Author: Android Developers (noreply@blogger.com) Published: 2026-07-27T13:00:00Z Content type: article Language: en Sources: [Android Developers Blog]() Topics: [Coroutines](), [Kotlin](), [R8](), [Android](), [Compose](), [Programming]() Tags: [android](), [android-gradle-plugin](), [app-performance](), [atomic](), [compose](), [coroutines](), [jetpack-compose](), [kotlin](), [perfetto](), [performance](), [programming](), [r8]() ### AI overview This article explains how R8 in AGP 9.2.0 optimizes Atomic*FieldUpdater calls into Unsafe variants, improving common operations by 2x to 4x. The optimization particularly benefits kotlinx.atomicfu and can make launching and cancelling Kotlin coroutines up to 2x faster. It also describes how coroutine overhead affected Jetpack Compose performance and how ART method traces helped identify bottlenecks. ### Source excerpt Posted by Andrei Shikov, Senior Software Engineer, Android Toolkit and Jonathan Starup, Software Engineer, R8 Team Starting from AGP 9.2.0, R8 optimizes most Atomic*FieldUpdater calls into Unsafe variants that perform 2x to 4x better on common operations. This has a particularly large impact on the kotlinx.atomicfu library that implements atomics for kotlinx.coroutines, making launching and cancelling coroutines up to 2x faster. In order to get the benefits, update your AGP to 9.2.0 or above. With the majority of Android apps adopting Kotlin as their main language of choice, kotlinx.coroutines has become a de-facto standard for asynchronous programming. The library offers a well-designed and structured way of managing concurrent flows that is native to Kotlin. Jetpack Compose was no exception, adopting coroutines for managing pointer events, animations and other interactions. At the time of writing, most concurrent APIs in Compose call suspend functions under the hood and are launching and/or cancelling coroutines to handle updates. As the Compose team started to investigate performance, coroutines were discovered to be a bottleneck for many operations that happen outside of composition. As an example, 80% of the time spent on creating and updating Modifier.clickable was consumed by launching and cancelling internal coroutines that handled InteractionSource updates. Based on those observations, much of early performance work was focused on removing coroutines from the default path and delaying initialization until necessary. The cost of a coroutine The easiest way to analyze a function's internal behavior on Android is to capture an Android Runtime (ART) method trace. An ART method trace is a tool that records the execution flow of an app, showing exactly which methods are called, their order, and how much time is spent in each, allowing developers to identify performance bottlenecks. For an empty LaunchedEffect { } call, it would look something like this: LaunchedE ## How R8 made Kotlin Coroutines on Android 2x faster DevFeed: [How R8 made Kotlin Coroutines on Android 2x faster]() Original publisher: [Read original article]() Author: Android Developers (noreply@blogger.com) Published: 2026-07-27T13:00:00Z Content type: article Language: en Sources: [Android Developers Blog](), [Android Developers Blog]() Topics: [Coroutines](), [Kotlin](), [R8](), [Android](), [Compose](), [Programming]() Tags: [android](), [android-gradle-plugin](), [app-performance](), [atomic](), [compose](), [coroutines](), [kotlin](), [performance](), [programming](), [r8]() ### AI overview This article explains how R8 optimization in AGP 9.2.0 improves Kotlin coroutines performance on Android. By optimizing AtomicFieldUpdater calls, the change makes launching and cancelling coroutines up to twice as fast, addressing coroutine-related bottlenecks in Jetpack Compose and other Android operations. ### Source excerpt Posted by Andrei Shikov, Senior Software Engineer, Android Toolkit and Jonathan Starup, Software Engineer, R8 Team Starting from AGP 9.2.0, R8 optimizes most Atomic*FieldUpdater calls into Unsafe variants that perform 2x to 4x better on common operations. This has a particularly large impact on the kotlinx.atomicfu library that implements atomics for kotlinx.coroutines, making launching and cancelling coroutines up to 2x faster. In order to get the benefits, update your AGP to 9.2.0 or above. With the majority of Android apps adopting Kotlin as their main language of choice, kotlinx.coroutines has become a de-facto standard for asynchronous programming. The library offers a well-designed and structured way of managing concurrent flows that is native to Kotlin. Jetpack Compose was no exception, adopting coroutines for managing pointer events, animations and other interactions. At the time of writing, most concurrent APIs in Compose call suspend functions under the hood and are launching and/or cancelling coroutines to handle updates. As the Compose team started to investigate performance, coroutines were discovered to be a bottleneck for many operations that happen outside of composition. As an example, 80% of the time spent on creating and updating Modifier.clickable was consumed by launching and cancelling internal coroutines that handled InteractionSource updates. Based on those observations, much of early performance work was focused on removing coroutines from the default path and delaying initialization until necessary. The cost of a coroutine The easiest way to analyze a function's internal behavior on Android is to capture an Android Runtime (ART) method trace. An ART method trace is a tool that records the execution flow of an app, showing exactly which methods are called, their order, and how much time is spent in each, allowing developers to identify performance bottlenecks. For an empty LaunchedEffect { } call, it would look something like this: LaunchedE ## Sliding Doors: ten years of RSS-Parser DevFeed: [Sliding Doors: ten years of RSS-Parser]() Original publisher: [Read original article]() Author: Marco Gomiero Published: 2026-06-17T00:00:00Z Content type: opinion Language: en Sources: [Posts on Marco Gomiero]() Topics: [RSS Feed](), [RSS](), [Mobile](), [Kotlin](), [Coroutines](), [Java](), [Android](), [iOS](), [macOS]() Tags: [android](), [coroutines](), [ios](), [java](), [kotlin](), [macos](), [mobile](), [rss](), [xml]() ### AI overview The author reflects on ten years of RSS-Parser, a library that began as part of an RSS-reading app and was later published for other developers. The article describes how the project contributed to the author's learning and career, including its move from Java to Kotlin and Coroutines, and its continued use in developing a new RSS app. ### Source excerpt Today marks ten years since the first commit of RSS-Parser. TEN YEARS. I want to use this opportunity to reflect on the journey of this library, the sliding doors moments along the way, and the chain of events that made RSS-Parser an important part of my career. The bare bones of the library started earlier, though; it was 2015 when I wrote my first app that I've published to the Play Store. This app was for reading the articles of the tech blog that I was collaborating with (for a while I was reviewing apps, phones, consumer tech - that's when I fell in love with mobile). The blog was built (of course) with the good old WordPress, and at the time I discovered that you can have the published articles formatted in XML - yes, I discovered the existence of RSS. ## Structured Concurrency DevFeed: [Structured Concurrency]() Original publisher: [Read original article]() Published: 2026-04-13T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [Structured concurrency](), [Coroutines](), [kotlin-coroutines](), [Concurrency](), [Error Handling]() Tags: [coroutines](), [error-handling](), [guide](), [kotlin](), [memory-leaks](), [processes](), [structured-concurrency](), [workshop-learning-programming]() ### AI overview A Kotlin-focused guide to structured concurrency explains how coroutine hierarchies establish ownership and completion guarantees. It covers cancellation of child coroutines, avoiding unnecessary work and resource leaks, awaiting completion, and handling errors. ### Source excerpt The only guide to structured concurrency you'll ever need. ## IntelliJ's New Kotlin Coroutine Inspections, Explained DevFeed: [IntelliJ's New Kotlin Coroutine Inspections, Explained]() Original publisher: [Read original article]() Published: 2026-03-30T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [IntelliJ IDEA](), [Kotlin](), [kotlin-coroutines](), [Coroutines](), [Android Studio](), [Exception]() Tags: [android-studio](), [exceptions](), [intellij-idea](), [kotlin](), [kotlin-coroutines](), [workshop-learning-programming]() ### AI overview This article explains new Kotlin coroutine inspections introduced in IntelliJ IDEA and also available in Android Studio. It describes warnings for coroutine usage patterns, including preferring awaitAll over await and currentCoroutineContext() over coroutineContext. ### Source excerpt Exploration and explanation of new Kotlin coroutine inspections in IntelliJ IDEA. ## Top Projects for Coroutines Mastery in 2025 DevFeed: [Top Projects for Coroutines Mastery in 2025]() Original publisher: [Read original article]() Published: 2026-02-09T00:00:00Z Content type: article Language: en Sources: [Kt. Academy]() Topics: [Coroutines](), [Learning](), [Android](), [App](), [Library](), [Bluetooth](), [data]() Tags: [2025](), [android](), [application](), [bluetooth-low-energy](), [coroutines](), [data](), [execution](), [library](), [project](), [workshop-learning-programming]() ### AI overview An overview of projects associated with the Coroutines Mastery course in 2025, including tools and applications for monitoring coroutine execution, testing Android dispatchers, simplifying Bluetooth Low Energy usage, and observing stock market data. ### Source excerpt Overview of the best projects for Coroutines Mastery course in 2025 ## Don't Block Suspend Functions DevFeed: [Don't Block Suspend Functions]() Original publisher: [Read original article]() Author: Jesse Wilson Published: 2026-01-22T04:32:49Z Content type: tutorial Language: en Sources: [Public Object]() Topics: [Coroutines](), [Kotlin](), [Concurrent Programming](), [Concurrency](), [async](), [Job](), [IO]() Tags: [async](), [await](), [blocking](), [blog-post](), [concurrency](), [coroutines](), [dispatcher](), [kotlin](), [thread](), [threads]() ### AI overview This Kotlin tutorial explains why blocking calls inside suspend functions can prevent other coroutines from running. It contrasts preemptive thread concurrency with cooperative coroutine concurrency and recommends avoiding blocking functions in suspending code, using the I/O dispatcher when necessary, and avoiding runBlocking. ### Source excerpt Here's a program that launches 3 jobs. The first runs forever and the other two exchange a value. @Test fun test() = runTest { val channel = Channel() val deferredA = async { while (isActive) { delay(1_000) } } val deferredB = async { channel.send("hello") } val deferredC = async { channel.receive() } deferredB.await( ## How to Prevent Race Conditions in Coroutines DevFeed: [How to Prevent Race Conditions in Coroutines]() Original publisher: [Read original article]() Author: author@typealias.com (Dave Leeds) Published: 2025-11-24T00:00:00Z Content type: tutorial Language: en Sources: [Dave Leeds on Kotlin - typealias.com]() Topics: [Coroutines](), [kotlin-coroutines](), [Kotlin](), [Concurrency]() Tags: [actor](), [atomicint](), [atomics](), [concurrency](), [coroutine](), [coroutines](), [how-to](), [kotlin](), [kotlin-coroutines](), [limitedparallelism](), [mutex](), [programming](), [race-condition](), [shared-mutable-state](), [state](), [stateflow](), [structured-concurrency]() ### AI overview This tutorial explains that Kotlin coroutines and structured concurrency do not automatically protect shared mutable state from race conditions. It introduces the issue using an example that creates 100,000 random bakery orders. ### Source excerpt Thanks to structured concurrency, there are a lot of concerns that we don't have to handle manually when working with Kotlin coroutines. For example, parent coroutines automatically wait for their children to complete before completing themselves. And when a parent coroutine is cancelled, its children are automatically cancelled, too. But when it comes to shared mutable state - mutable data that multiple coroutines could update at the same time - there's nothing magical in the design of coroutines to ensure that the state is updated properly. ## Suspending functions vs. Flow: When to use which? DevFeed: [Suspending functions vs. Flow: When to use which?]() Original publisher: [Read original article]() Published: 2025-10-28T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [Kotlin](), [kotlin-coroutines](), [Coroutines]() Tags: [coroutines](), [flow](), [guide](), [kotlin](), [kotlin-coroutines](), [workshop-learning-programming]() ### AI overview A guide to the differences between suspending functions and Flow in Kotlin Coroutines, including when to use each. ### Source excerpt A comprehensive guide to understanding the differences between suspending functions and Flow in Kotlin Coroutines, and when to use each. ## Discussing Kotlin Coroutines on Talking Kotlin Podcast DevFeed: [Discussing Kotlin Coroutines on Talking Kotlin Podcast]() Original publisher: [Read original article]() Published: 2025-10-17T00:00:00Z Content type: article Language: en Sources: [Kt. Academy]() Topics: [kotlin-coroutines](), [Coroutines](), [Kotlin](), [Development]() Tags: [coroutines](), [development](), [kotlin](), [kotlin-coroutines](), [podcast](), [workshop-learning-programming]() ### AI overview A discussion about Kotlin Coroutines on the Talking Kotlin podcast. The supplied evidence identifies Marcin Moskala as the author and Kotlin instructor, but does not provide further details about the discussion. ### Source excerpt An insightful discussion about Kotlin Coroutines on the Talking Kotlin podcast. ## Kotlin Coroutines Compared with Reactor for Sequential and Asynchronous Operations DevFeed: [Kotlin Coroutines Compared with Reactor for Sequential and Asynchronous Operations]() Original publisher: [Read original article]() Published: 2025-10-06T00:00:00Z Content type: comparison Language: en Sources: [Kt. Academy]() Topics: [Coroutines](), [Kotlin](), [kotlin-coroutines](), [Reactive Streams](), [RxJava](), [async/await](), [Android](), [Back end]() Tags: [android](), [async](), [asynchronous](), [await](), [backend](), [compare](), [comparison](), [coroutines](), [kotlin](), [kotlin-coroutines](), [programming](), [programming-languages](), [reactive-streams](), [rxjava](), [simple](), [time](), [workshop-learning-programming]() ### AI overview This article compares Kotlin Coroutines with Reactor for backend and Android development. It argues that coroutines provide more readable and straightforward syntax for sequential and asynchronous operations, while Reactor requires additional operators, concepts, and patterns. ### Source excerpt A comparison of Kotlin Coroutines and Reactor, highlighting the elegance and simplicity of Coroutines over the complexity of Reactor. ## Suspending functions into blocking functions or CompletableFuture DevFeed: [Suspending functions into blocking functions or CompletableFuture]() Original publisher: [Read original article]() Published: 2025-09-29T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [Kotlin](), [kotlin-coroutines](), [Coroutines](), [Java](), [functions]() Tags: [blocking](), [coroutines](), [guide](), [how-to](), [kotlin](), [kotlin-coroutines](), [workshop-learning-programming]() ### AI overview A guide to converting suspending functions into blocking functions or CompletableFuture in Kotlin Coroutines, with advice for APIs used by Java or non-coroutine Kotlin callers. ### Source excerpt A guide on how to correctly convert suspending functions into blocking functions or CompletableFuture in Kotlin Coroutines. ## runBlocking in practice: Where it should be used and where not DevFeed: [runBlocking in practice: Where it should be used and where not]() Original publisher: [Read original article]() Published: 2025-09-01T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [runBlocking](), [Coroutines](), [Kotlin](), [kotlin-coroutines]() Tags: [android](), [async](), [await](), [best-practices](), [blocking](), [coroutines](), [dispatcher](), [guide](), [kotlin](), [pitfalls](), [retrofit](), [runblocking](), [workshop-learning-programming]() ### AI overview A practical guide to runBlocking in Kotlin Coroutines. It explains how runBlocking converts suspending calls into blocking calls, blocks the calling thread until completion, and creates a new coroutine hierarchy. The article discusses appropriate uses, code smells, and alternatives, including an Android Retrofit interceptor example. ### Source excerpt A comprehensive guide to using runBlocking in Kotlin Coroutines, including best practices and common pitfalls. ## Flow from suspending functions and vice versa DevFeed: [Flow from suspending functions and vice versa]() Original publisher: [Read original article]() Published: 2025-08-18T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [Kotlin](), [kotlin-coroutines](), [Coroutines](), [functions]() Tags: [coroutines](), [functions](), [guide](), [how-to](), [kotlin](), [kotlin-coroutines](), [workshop-learning-programming]() ### AI overview A guide to converting suspending functions to Flow and converting Flow back to suspending functions in Kotlin Coroutines. ### Source excerpt A guide on how to convert suspending functions to Flow and vice versa in Kotlin Coroutines. ## Suspending functions or flows into callbacks DevFeed: [Suspending functions or flows into callbacks]() Original publisher: [Read original article]() Published: 2025-08-11T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [kotlin-coroutines](), [Kotlin](), [Coroutines](), [callback]() Tags: [callback](), [coroutines](), [guide](), [how-to](), [kotlin](), [kotlin-coroutines](), [workshop-learning-programming]() ### AI overview A practical guide to converting Kotlin suspending functions and flows into callback-based functions using Kotlin Coroutines. ### Source excerpt A guide on how to correctly convert suspending functions or flows into callback-based functions in Kotlin Coroutines. ## Calling blocking functions from suspending functions DevFeed: [Calling blocking functions from suspending functions]() Original publisher: [Read original article]() Published: 2025-07-21T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [Coroutines](), [kotlin-coroutines](), [Kotlin](), [interoperability](), [Concurrency]() Tags: [blocking](), [guide](), [how-to](), [interoperability](), [kotlin](), [kotlin-coroutines](), [workshop-learning-programming]() ### AI overview A guide to using blocking library functions with Kotlin Coroutines by converting them into suspending functions or flows. It explains how blocking operations affect the current thread and how to identify whether a function is blocking. ### Source excerpt A guide on how to correctly convert blocking functions into suspending functions in Kotlin Coroutines. ## KotlinConf 2025 Recordings DevFeed: [KotlinConf 2025 Recordings]() Original publisher: [Read original article]() Published: 2025-07-01T00:00:00Z Content type: article Language: en Sources: [Kt. Academy]() Topics: [Kotlin](), [recommendations](), [Compiler](), [Project Valhalla](), [Coroutines](), [debugging]() Tags: [2025](), [compiler](), [coroutines](), [debugging](), [kotlinconf](), [project-valhalla](), [recommendations](), [workshop-learning-programming](), [writing]() ### AI overview An opinionated list of recommended recordings from KotlinConf 2025, including the keynote, Rich Errors in Kotlin, compiler plugins, Project Valhalla, and debugging and performance tuning in a coroutine world. ### Source excerpt My list of must-watch from KotlinConf 2025. [Next page]()