# Kotlin Kotlin is a programming language for multiplatform, backend, and Android development. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Релиз OpenIDE 2026.2: одна IDE для Java, Kotlin, Go, Python и веб-разработки DevFeed: [Релиз OpenIDE 2026.2: одна IDE для Java, Kotlin, Go, Python и веб-разработки]() Original publisher: [Read original article]() Author: honest\_niceman (Haulmont) Published: 2026-09-17T09:12:16Z Content type: release Language: ru Sources: [Tagir Valeev]() Topics: [intellij-platform](), [Java](), [Git](), [Kotlin](), [Gradle](), [Databases](), [Docker](), [Go](), [Python](), [SQL](), [JSON]() Tags: [2](), [2026](), [2026-2](), [compose](), [db-eaa4bca15522](), [docker](), [docker-bdf52bf499c4](), [git](), [go](), [gradle](), [ide-1f5689fe989b](), [ide-af948443b041](), [ide-java-0ad4946a0e57](), [intellij-idea-27f15aabb340](), [intellij-platform](), [java](), [javascript](), [json](), [kotlin](), [openide](), [openide-2026-2](), [openide-pro](), [oracle](), [sql](), [structure]() ### AI overview OpenIDE 2026.2 updates its base platform, expands Java and Kotlin support, improves Git and Gradle workflows, and updates its Java profiler. The release also includes improvements to the DB client and Docker plugin, including SQL formatting, Greenplum support, JSON highlighting, and enhanced Compose service management. ### Source excerpt Обновили базовую платформу до версии 2026.2, расширили поддержку Java и Kotlin, улучшили работу с Git и обновили Java-профилировщик. Доработали редактор и подсказки в терминале, добавили проверки настроек Gradle и упростили переход к исходникам библиотек. Через Git worktrees теперь можно работать с несколькими ветками одновременно. Читать далее ## Shopify Drops React Native for Swift and Kotlin as AI Changes Cross-Platform Development Tradeoffs DevFeed: [Shopify Drops React Native for Swift and Kotlin as AI Changes Cross-Platform Development Tradeoffs]() Original publisher: [Read original article]() Author: Bruno Couriol Published: 2026-09-16T12:45:00Z Content type: news Language: en Sources: [InfoQ]() Topics: [React Native](), [Shopify](), [Mobile](), [cross-platform](), [Kotlin](), [Swift](), [AI Models]() Tags: [ai](), [ai-coding](), [android](), [apple](), [cross-platform](), [declarative](), [development](), [kotlin](), [mobile](), [news](), [react-native](), [shopify](), [shopify-drops-react-native](), [swift](), [web-development]() ### AI overview Shopify is rewriting its flagship mobile apps in Swift and Kotlin after reassessing React Native. The decision followed the expected work to adopt React Native's New Architecture and improvements in AI coding models, which Shopify said made a clean-slate native rewrite more attractive than migration. ### Source excerpt Shopify recently announced it is abandoning React Native to rewrite its flagship apps in Swift and Kotlin. With the significant jump in the quality of AI models, Head of Mobile Mustafa Ali reassessed Shopify's commitment to React Native, estimating that the benefit/cost ratio of maintaining native codebases across mobile platforms was now above that of using an abstraction layer. By Bruno Couriol ## Kotlin on the server at Khan Academy DevFeed: [Kotlin on the server at Khan Academy]() Original publisher: [Read original article]() Author: Khan Academy Published: 2018-06-28T22:00:00Z Content type: article Language: en Sources: [Khan Academy]() Topics: [Kotlin](), [backend-development](), [Python](), [Google]() Tags: [api](), [bigquery](), [blog-post](), [developer-experience](), [engineering](), [google](), [http](), [infrastructure](), [java](), [kotlin](), [news](), [python](), [server-side-development]() ### AI overview Khan Academy describes testing Kotlin for user-facing server requests during a 2018 hackathon and deciding to adopt Kotlin as a second server-side language after reporting positive efficiency results and a positive developer experience. ### Source excerpt By Colin Fuller At Khan Academy, we run our web application using Python 2.7 on Google's App Engine ... Read more ## Go + Services = One Goliath Project DevFeed: [Go + Services = One Goliath Project]() Original publisher: [Read original article]() Author: Khan Academy Published: 2019-12-20T23:00:00Z Content type: opinion Language: en Sources: [Khan Academy]() Topics: [Go Language](), [Python](), [Back end](), [Kotlin](), [Server]() Tags: [backend](), [end-of-life](), [engineering](), [go](), [infrastructure](), [kotlin](), [news](), [performance](), [services]() ### AI overview Khan Academy describes its effort to rebuild server software on Go's modern stack. The article explains why moving from Python 2 to Python 3 offered limited benefits, considers Kotlin and other options, and presents faster languages as a way to improve responsiveness and reduce server costs. ### Source excerpt By Kevin Dangoor Go + Services = One Goliath Project Khan Academy is embarking on a huge effort ... Read more ## Kotlin for Python developers DevFeed: [Kotlin for Python developers]() Original publisher: [Read original article]() Author: Khan Academy Published: 2018-11-29T23:00:00Z Content type: tutorial Language: en Sources: [Khan Academy]() Topics: [Kotlin](), [Python](), [Learning](), [Programming]() Tags: [content-platform](), [developers](), [engineering](), [guide](), [kotlin](), [learning](), [news](), [programming](), [python]() ### AI overview Khan Academy Engineering publicly released a Kotlin for Python developers guide after adopting Kotlin as an alternative backend language alongside Python. The textbook-style resource explains Kotlin in terms familiar to Python developers, while noting that it is not comprehensive and is provided as-is. ### Source excerpt By Aasmund Eldhuset Earlier this year, the Khan Academy Engineering organization decided to introduce Kotlin as an alternative ... Read more ## Kotlin 2.4.20 Collection Checks and Experimental Context-Sensitive Resolution DevFeed: [Kotlin 2.4.20 Collection Checks and Experimental Context-Sensitive Resolution]() Original publisher: [Read original article]() Author: Andrii Dubovyk Published: 2026-09-14T06:32:51Z Content type: tutorial Language: en Sources: [ProAndroidDev - Medium]() Topics: [Kotlin](), [Compiler](), [Code]() Tags: [android](), [android-development](), [collections](), [compiler](), [experimental](), [features](), [kotlin](), [list](), [mobile-app-development](), [syntax](), [technology]() ### AI overview The article explains two Kotlin features: allDistinctBy and allEqualBy in Kotlin 2.4.20 for checking collection values, and experimental context-sensitive resolution introduced in Kotlin 2.2 to reduce repetition when the expected type is known. ### Source excerpt Kotlin 2.4.20 gives your collections opinions, and 2.2's compiler finally learns to read the room Some Kotlin features get a lot of attention when they arrive. Others are much less noticeable, but still make everyday code a little easier to write. Two examples of the latter are allDistinctBy/ allEqualBy in Kotlin 2.4.20 and context-sensitive resolution, which was introduced experimentally in Kotlin 2.2. allDistinctBy/ allEqualBy: A Simpler Way to Check Collections For years, checking whether all values in a collection were unique often looked something like this: val users = listOf( User(name = "A", age = 20), User(name = "B", age = 25), User(name = "C", age = 30) ) users.map { it.age }.distinct().size == users.size // true It works, but it creates another list, removes duplicates, counts the result, and then compares the sizes just to get a Boolean answer. Kotlin 2.4.20 adds a more direct way to express the same check: users.allDistinctBy { it.age } // true users.allEqualBy { it.age } // false allDistinctBy returns false as soon as it finds a duplicate, so it doesn't need to process the entire collection or create a separate Set. allEqualBy does the opposite: it checks whether all elements produce the same value when passed through the selector. Both functions work with Iterable, Sequence, and arrays. They use structural equality. For floating-point values, they follow Double.equals semantics, so NaN is considered equal to NaN, while -0.0 is different from 0.0. They're still @ExperimentalStdlibApi, so you'll need to opt in before using them in production code. The underlying allDistinct() and allEqual() requests have also been around in YouTrack for quite a while, which makes their appearance in the standard library feel long overdue. Context-Sensitive Resolution: Less Repetition in when The second feature is more about syntax. When the compiler already knows the type you're working with, you can sometimes leave out the type qualifier. Before: enum class Problem { ## Kotlin Explicit Backing Fields: Encapsulation Tradeoffs and Downcasting Risks DevFeed: [Kotlin Explicit Backing Fields: Encapsulation Tradeoffs and Downcasting Risks]() Original publisher: [Read original article]() Author: Ehab Elwan Published: 2026-09-13T05:31:32Z Content type: opinion Language: en Sources: [ProAndroidDev - Medium]() Topics: [Kotlin](), [Code](), [Jetpack Compose]() Tags: [android](), [android-development](), [architecture](), [article](), [clean-code](), [code](), [compiler](), [kotlin](), [memory](), [software-architecture](), [stateflow]() ### AI overview This article compares Kotlin's traditional private mutable property plus public read-only wrapper with explicit backing fields. It explains that explicit backing fields can avoid an extra wrapper allocation, but because the underlying object remains mutable, an external downcast may bypass the intended read-only restriction and mutate internal state. ### Source excerpt Why eliminating the double-property boilerplate changes how we protect our architecture Image generated by AIDisclosure: This article was drafted by me and refined with the help of AI tools. If you have written Kotlin in the last few years, you are intimately familiar with the double-property boilerplate. Whether in Android ViewModels or general state holders, maintaining a private mutable property alongside a public read-only property is a chore we have all accepted in the name of strict encapsulation to prevent our internal state from being hijacked by outside classes. It makes the code significantly cleaner (and slightly more memory efficient). However, it fundamentally changes how we protect our state, moving from a physical object boundary to a simple type restriction. Let's look at the tradeoff. The Old Way: Wrapper Protection For years, the standard approach to encapsulating state has looked like this: class OldViewModel { // 1. The private mutable state private val _uiState = MutableStateFlow(UiState()) // 2. The public read-only state val uiState: StateFlow = _uiState.asStateFlow() } This is tedious to write, but it provides a strict architectural guarantee. When you call .asStateFlow(), Kotlin does not just change the type; it creates a brand new wrapper object in memory (ReadonlyStateFlow). While this physical barrier is fantastic for safety, it does mean you are incurring a minor memory allocation overhead by creating a secondary wrapper object for every exposed state. The New Way: Upcasting Explicit Backing Fields allow you to merge these two properties into one concise declaration, bypassing that extra memory allocation entirely: class NewViewModel { val uiState: StateFlow field = MutableStateFlow(UiState()) } Inside your class, the Kotlin compiler smart-casts the field so you can mutate it internally. Outside the class, the compiler restricts callers to the read-only StateFlow interface. It looks incredibly clean and saves an allocat ## Announcing ADK for Kotlin 1.0: Building Production-Ready AI Agents in Kotlin, Android, and Beyond DevFeed: [Announcing ADK for Kotlin 1.0: Building Production-Ready AI Agents in Kotlin, Android, and Beyond]() Original publisher: [Read original article]() Author: Guillaume Laforge Published: 2026-09-12T11:04:33.891311Z Content type: release Language: en Sources: [Google Developers Blog]() Topics: [Artificial Intelligence](), [Kotlin](), [AI Development](), [Android](), [Kotlin Multiplatform](), [multiplatform](), [Orchestration](), [Google](), [Persistence](), [Agent Skill](), [LiteRT](), [Cloud]() Tags: [agent-skill](), [agents](), [ai](), [ai-agent](), [ai-agents](), [android](), [building](), [database](), [development-kit](), [firebase](), [incident](), [kotlin](), [multiplatform](), [orchestration](), [persistence](), [production]() ### AI overview Google announces the 1.0 general availability release of the Agent Development Kit (ADK) for Kotlin, a production-ready toolkit for building multi-agent applications with Kotlin, Java, and Android. Built on Kotlin Multiplatform, it provides feature parity with the ADK 1.0 Core and adds Android-first extensions for on-device agents with LiteRT-LM and ML Kit, hybrid cloud workflows through Firebase AI Logic, and state persistence with Room and AppSearch. The release also includes type-safe, compile-time function calling through KSP and declarative agent skills. ### Source excerpt Google has officially released version 1.0 of the Agent Development Kit (ADK) for Kotlin, achieving full feature parity with the Python and Java ADK cores to enable idiomatic, multi-agent AI development. Built on Kotlin Multiplatform (KMP), the framework leverages Kotlin Symbol Processing (KSP) for zero-reflection, type-safe function calling, alongside advanced orchestration capabilities like human-in-the-loop workflows and context compaction. Additionally, the release introduces a robust suite of Android-first extensions, allowing mobile developers to integrate local models via LiteRT-LM, cloud reasoning through Firebase AI, session persistence using Room, and semantic memory powered by AppSearch. ## Native is now the future of mobile at Shopify DevFeed: [Native is now the future of mobile at Shopify]() Original publisher: [Read original article]() Author: Simon Willison Published: 2026-09-10T21:11:15Z Content type: opinion Language: en Sources: [Simon Willison's Weblog]() Topics: [Mobile](), [React Native](), [Shopify](), [AI-assisted coding](), [Kotlin](), [Swift](), [Open Source](), [Android](), [Generative AI](), [iOS]() Tags: [ai](), [ai-2-236](), [ai-assisted-search](), [ai-assisted-search-36](), [android](), [android-14](), [coding-agents](), [coding-agents-248](), [generative-ai](), [generative-ai-1-982](), [ios](), [ios-26](), [kotlin](), [llms](), [llms-1-948](), [mobile](), [mobile-41](), [open-source](), [open-source-320](), [react](), [react-43](), [react-native](), [shopify](), [shopify-8](), [swift](), [swift-12]() ### AI overview Shopify is moving its mobile apps from React Native back to separate Swift and Kotlin codebases. The article explains that AI agents can now handle enough implementation, translation, testing, and review work to reduce the cost of maintaining separate platforms. It also notes the planned relocation or archival of Shopify's React Native libraries. ### Source excerpt Native is now the future of mobile at Shopify Shopify are moving from React Native back to separate Swift and Kotlin codebases for their native apps, for the exact reason you would expect: We decided to switch from native to React Native in 2020 for three reasons: Stop building the same features twice Allow developers to work across the stack Spend less time chasing feature parity and more time shipping value [...] Native still means building and maintaining software on two platforms, that cost has not disappeared. What changed is that agents can now do enough of the implementation, translation, testing, and review work that it's no longer the deciding factor it was in 2020. It's a well-written post, which gives full credit to React Native as a great platform for the six years they were using it. Shopify are the maintainers of three significant React Native libraries: react-native-skia, flash-list, and restyle. The first two are finding new homes; the third "has a smaller user base than our other libraries" and will be archived at the end of 2026. Via Hacker News Tags: android, mobile, open-source, ios, ai, react, generative-ai, llms, ai-assisted-search, coding-agents, swift, shopify ## Kodebits Day 90: Named Arguments \[FREE\] DevFeed: [Kodebits Day 90: Named Arguments \[FREE\]]() Original publisher: [Read original article]() Published: 2026-09-10T17:00:05Z Content type: tutorial Language: en Sources: [Kodeco | High quality programming tutorials: iOS, Android, Swift, Kotlin, Unity, and more]() Topics: [Kotlin]() Tags: [article](), [development](), [free](), [kotlin]() ### AI overview A short Kotlin challenge for practicing named arguments. ### Source excerpt Practice arguments with a short kotlin challenge. ## Koin Compiler 1.2: Compile-Time Safety for ALL Koin DSL DevFeed: [Koin Compiler 1.2: Compile-Time Safety for ALL Koin DSL]() Original publisher: [Read original article]() Author: Arnaud Giuliani Published: 2026-09-10T12:01:01Z Content type: release Language: en Sources: [Koin developers - Medium]() Topics: [Compiler](), [Kotlin](), [Gradle]() Tags: [compiler](), [dependencies](), [dependency-injection](), [gradle](), [implementation](), [koin](), [kotlin](), [kotlin-multiplatform]() ### AI overview Koin Compiler Plugin 1.2, with 1.2.1 as the latest patch, extends compile-time validation to Koin's reified, constructor, and classic lambda DSLs. It also adds visibility across Gradle modules, supports additional entry points, and provides one artifact for Kotlin 2.3.20 through 2.4.20 without requiring a DSL migration. ### Source excerpt Hello, dear Koin community 👋 I'm happy to share that Koin Compiler Plugin 1.2 is out, with 1.2.1 already available as the latest patch. Developer mascott unboxing new Koin Features!TL;DR Compile-time validation now works on the Koin application you already have, where before 1.2 it only covered code written specifically for the compiler plugin. Koin DSL -- All now covered! All Koin DSL: the plugin's reified DSL, Koin's constructor DSL (singleOf(::T)), and the classic lambda DSL (single { Foo(get()) }). Across Gradle modules: definitions are now visible two or more implementation hops away. More entry points: Ktor's install(Koin) and KoinApplication.withConfiguration(). One artifact for Kotlin 2.3.20 through 2.4.20. You get there with no migration to a new DSL, and nothing to rewrite. Let's go through what shipped. Covering now all Koin DSL Until now, compile-time safety only covered the plugin's own reified DSL, which means the two DSL styles you have most likely already written were invisible to it. val appModule = module { single() // checked singleOf(::UserRepository) // not checked before 1.2 single { AnalyticsHelper(get()) } // not checked before 1.2 } Three ways to declare a definition, and only the first was validated. If your UserRepository needed a Database that no module provided, your build passed and Koin threw at runtime. In 1.2, all three are validated. The two DSL styles get there differently. For the constructor DSL, the referenced constructor's parameters become real requirements, exactly like single(), and any named() qualifier you put on the registration is matched against the consumers that ask for it. The classic lambda DSL works differently. The plugin doesn't try to work out dependencies from free-form lambda code. What it validates instead are the get() calls you wrote inside the lambda, treated as ordinary resolution call sites. Before 1.2 those calls were skipped on purpose, because a hand-written get() is difficult to dis ## A Multi-Module Android Template with Kotlin Convention Plugins, Lint Rules, and Design System Tokens DevFeed: [A Multi-Module Android Template with Kotlin Convention Plugins, Lint Rules, and Design System Tokens]() Original publisher: [Read original article]() Author: Shamil Gulmetov Published: 2026-09-09T01:34:18Z Content type: tutorial Language: en Sources: [ProAndroidDev - Medium]() Topics: [Template](), [Android](), [Architecture & Design](), [Kotlin](), [Gradle](), [Jetpack Compose](), [Dependency injection](), [Automation](), [Refactoring](), [now-in-android]() Tags: [android](), [android-app-development](), [android-architecture](), [android-studio](), [architecture](), [automation](), [best-practices](), [build](), [compose](), [dependency-injection](), [gradle](), [how-to](), [jetpack-compose](), [kotlin](), [now-in-android](), [refactoring]() ### AI overview This tutorial presents an Android Architecture Template based on patterns from Google's Now in Android repository. It describes a multi-module structure with Gradle Version Catalogs, Kotlin Convention Plugins, Jetpack Compose design tokens and dark-theme support, dependency injection, custom Lint rules, and a terminal-based renaming tool. ### Source excerpt How to streamline your development workflow with pre-configured Kotlin Convention Plugins, custom Lint rules, and unified design system tokens. Creating a new Android application from scratch in modern engineering is rarely as simple as clicking File -> New -> New Project in Android Studio. Before writing a single line of business logic, developers face hours -- or even days -- of repetitive infrastructure setup: Configuring a scalable multi-module architecture. Setting up Gradle Version Catalogs and writing custom Kotlin Convention Plugins to eliminate build script duplication. Standardizing design tokens and dark theme support in Jetpack Compose. Wiring up Hilt Dependency Injection for Coroutine Dispatchers, network, and Application Scopes. Enforcing architectural boundaries and team coding standards using custom static analysis (Lint) rules. Google's official Now in Android (NiA) repository is the recognized gold standard for modern Android engineering. However, because NiA is a full-featured showcase app with domain logic (news feeds, authors, bookmarks, offline sync), using it as a starter kit is cumbersome: developers must strip out existing features while risking breaking build pipelines. This Android Architecture Template bridges that gap: a clean, production-ready starter kit that extracts NiA's best architectural patterns into an isolated foundation. To make it enterprise-ready with zero room for error, it includes a standalone automation tool. Instead of manual refactoring, run a single terminal command to rename and brand the entire architecture in seconds. Acknowledgments & Credits Core architectural decisions, build-logic convention plugins, and static analysis infrastructure in this template are directly inspired by Google's official Now in Android (NiA) repository. Rather than reinventing the wheel, this template focuses on developer ergonomics--making Google's best practices instantly usable out of the box. 1. Modular Project Architecture The repository ## Setting Up Koin in a Real Kotlin Multiplatform Project: A Step-by-Step Guide DevFeed: [Setting Up Koin in a Real Kotlin Multiplatform Project: A Step-by-Step Guide]() Original publisher: [Read original article]() Author: Gabriel Bronzatti Moro Published: 2026-09-07T12:01:03Z Content type: tutorial Language: en Sources: [Koin developers - Medium]() Topics: [Kotlin Multiplatform](), [compose-multiplatform](), [Kotlin](), [Android](), [iOS](), [ui]() Tags: [android](), [compose-multiplatform](), [dependencies](), [guide](), [implementation](), [ios](), [kmp](), [koin](), [kotlin](), [kotlin-multiplatform](), [mobile-app-development](), [module](), [viewmodel]() ### AI overview A step-by-step tutorial for setting up Koin in a Kotlin Multiplatform project targeting Android and iOS. It covers dependencies, data, domain, and UI modules, a platform bridge, platform entry points, and dependency injection in Composables. ### Source excerpt Hi everyone! 👋 In this article, we'll take a practical, step-by-step approach to setting up Koin in a real-world Kotlin Multiplatform (KMP) project. Instead of starting with an isolated example or a simple Hello World, we'll work with a project created by the CodandoTV community: the World Cup Best Team Simulator. The app allows users to browse football players by country and build their own dream team. It runs on both Android and iOS, using Kotlin Multiplatform for sharing business and data logic, and Compose Multiplatform to share the UI across platforms. Step 1: Add Koin Dependencies Add the Koin libraries to your version catalog: # gradle/libs.versions.toml [versions] koin = "4.2.2" [libraries] koin_core = { group = "io.insert-koin", name = "koin-core", version.ref = "koin" } koin_android = { group = "io.insert-koin", name = "koin-android", version.ref = "koin" } koin_compose = { module = "io.insert-koin:koin-compose", version.ref = "koin" } koin_compose_viewmodel = { module = "io.insert-koin:koin-compose-viewmodel", version.ref = "koin" } In the shared module shared/build.gradle.kts, split the dependencies by source set -- commonMain gets the shared Koin libraries, androidMain gets the Android-specific one: // shared/build.gradle.kts sourceSets { commonMain.dependencies { implementation(libs.koin.core) implementation(libs.koin.compose) implementation(libs.koin.compose.viewmodel) } androidMain.dependencies { implementation(libs.koin.android) } } In the Android app module androidApp/build.gradle.kts , add the Android Koin dependency: // androidApp/build.gradle.kts dependencies { implementation(libs.koin.android) implementation(libs.koin.core) }Step 2: Create the Data Module Create shared/src/commonMain/.../data/DataModule.kt . This module provides singleton instances -- repositories, and data sources that live for the entire app lifecycle. val dataModule = module { single { WorldCupRepositoryImpl(ioDispatcher = Dispatchers.IO) } }Step 3: Create ## Kodebits Day 87: Default Parameters \[FREE\] DevFeed: [Kodebits Day 87: Default Parameters \[FREE\]]() Original publisher: [Read original article]() Published: 2026-09-06T16:00:57Z Content type: tutorial Language: en Sources: [Kodeco | High quality programming tutorials: iOS, Android, Swift, Kotlin, Unity, and more]() Topics: [Kotlin]() Tags: [article](), [development](), [free](), [kotlin](), [learn]() ### AI overview A short Kotlin challenge focused on practicing default parameters. ### Source excerpt Practice parameters with a short kotlin challenge. ## Using the new Google Gen AI SDK for Kotlin DevFeed: [Using the new Google Gen AI SDK for Kotlin]() Original publisher: [Read original article]() Published: 2026-09-04T23:00:00Z Content type: tutorial Language: en Sources: [John O'Reilly]() Topics: [Kotlin](), [SDKs](), [Google](), [Artificial Intelligence](), [API]() Tags: [ai](), [apis](), [google](), [kotlin](), [sdk]() ### AI overview This tutorial shows how to replace hand-written Gemini REST calls with Google's version 1.0 Gen AI SDK for Kotlin. It covers the SDK's coroutine- and Flow-based client, video and text requests, and structured JSON output. ### Source excerpt Google have just released version 1.0 of the Gen AI SDK for Kotlin, an idiomatic Kotlin client for the Gemini APIs. Up to now, calling Gemini from Kotlin has generally meant use of one of the Firebase SDKs, a community wrapper, an agent framework like Koog, or (as in the code below) just talking to the REST endpoint yourself. This is Google's own Kotlin library for it, built around coroutines and Flow. ## Kodebits August 2026: Kotlin Takes the Lead \[FREE\] DevFeed: [Kodebits August 2026: Kotlin Takes the Lead \[FREE\]]() Original publisher: [Read original article]() Author: samdavies Published: 2026-09-03T19:54:55Z Content type: article Language: en Sources: [Kodeco | High quality programming tutorials: iOS, Android, Swift, Kotlin, Unity, and more]() Topics: [Kotlin](), [Android](), [Swift](), [Dart]() Tags: [2026](), [android](), [article](), [beginner](), [comparison](), [dart](), [free](), [kotlin](), [swift]() ### AI overview Kodebits August 2026 presents 18 programming puzzles grouped by platform and ordered from beginner to advanced. Kotlin leads the month with eight entries, followed by Swift with seven and Dart with three. The Kotlin material covers everyday topics including collections, ranges, string templates, null safety, and type checking, while the roundup also highlights comparisons across Kotlin, Swift, and Dart. ### Source excerpt Kotlin outnumbered Swift for the first time in August, and the month eased off after July's hard streak. Here's all 18 bits grouped by platform and sorted from beginner to advanced. ## 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 ## Compose Multiplatform Is a Business Decision, Not a Technical One - Justin Mancinelli DevFeed: [Compose Multiplatform Is a Business Decision, Not a Technical One - Justin Mancinelli]() Original publisher: [Read original article]() Published: 2026-09-01T18:00:00Z Content type: opinion Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [compose-multiplatform](), [multiplatform](), [Compose](), [Flutter](), [Jetpack Compose](), [React Native](), [Kotlin](), [jetbrains]() Tags: [compose-multiplatform](), [cross-platform](), [flutter](), [javascript](), [jetbrains](), [kotlin](), [kotlin-multiplatform](), [multiplatform](), [react](), [technical](), [ui]() ### AI overview This opinion article argues that Compose Multiplatform is a strategic business choice for sharing UI across Android, iOS, desktop, and web. It compares CMP with Flutter and React Native, emphasizing its Kotlin and Jetpack Compose foundations and its native status on Android. ### Source excerpt If you are weighing Flutter, maintaining two native UI codebases "for now", or assuming cross-platform means giving something up, read this before your next roadmap conversation. ## Kodebits Day 85: Type Check As Cast \[FREE\] DevFeed: [Kodebits Day 85: Type Check As Cast \[FREE\]]() Original publisher: [Read original article]() Published: 2026-08-31T18:00:49Z Content type: tutorial Language: en Sources: [Kodeco | High quality programming tutorials: iOS, Android, Swift, Kotlin, Unity, and more]() Topics: [Kotlin]() Tags: [article](), [development](), [free](), [kotlin](), [learn]() ### AI overview A short Kodeco challenge for practicing Kotlin type checks. ### Source excerpt Practice type checks with a short kotlin challenge. ## Consuming SKIE Flows in SwiftUI - Gustavo Fão Valvassori DevFeed: [Consuming SKIE Flows in SwiftUI - Gustavo Fão Valvassori]() Original publisher: [Read original article]() Published: 2026-08-29T00:00:00Z Content type: tutorial Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [SwiftUI](), [Kotlin](), [Swift](), [Extension]() Tags: [boilerplate](), [community](), [extensions](), [interop](), [kmp](), [kotlin](), [kotlin-multiplatform](), [libraries](), [open-source](), [skie](), [swiftui]() ### AI overview This tutorial explains how to consume Kotlin Flows in SwiftUI using SKIE. It covers enabling SKIE extensions in Gradle and collecting StateFlow values through an async collect approach, a modifier, or a view wrapper to reduce repetitive UI-layer code. ### Source excerpt SKIE already makes the interop between Kotlin and Swift smooth, but SwiftUI adds a layer of complexity. We've included a series of extensions in SKIE to enable easy KMP usage from SwiftUI ## Kodebits Day 83: Smart Cast \[FREE\] DevFeed: [Kodebits Day 83: Smart Cast \[FREE\]]() Original publisher: [Read original article]() Published: 2026-08-28T18:00:52Z Content type: tutorial Language: en Sources: [Kodeco | High quality programming tutorials: iOS, Android, Swift, Kotlin, Unity, and more]() Topics: [Kotlin]() Tags: [article](), [free](), [kotlin](), [learn]() ### AI overview A short Kotlin challenge about smart casts and type checks. It explains that after an `is` check, Kotlin treats the value as the checked type within the `if` block, allowing direct access to String properties such as `.length`. ### Source excerpt Practice type checks with a short kotlin challenge. ## 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. ## Kodebits Day 80: Safe Call Operator \[FREE\] DevFeed: [Kodebits Day 80: Safe Call Operator \[FREE\]]() Original publisher: [Read original article]() Published: 2026-08-23T16:00:47Z Content type: article Language: en Sources: [Kodeco | High quality programming tutorials: iOS, Android, Swift, Kotlin, Unity, and more]() Topics: [Kotlin]() Tags: [article](), [development](), [free](), [kotlin](), [learn]() ### AI overview A short Kotlin challenge for practicing null-safety and the safe call operator. ### Source excerpt Practice null-safety with a short kotlin challenge. ## 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. [Next page]()