# multiplatform A software-development approach that shares code across different target platforms while accommodating platform-specific code. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## 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. ## Kotlin Toolchain 0.12: Multiplatform Library Publishing, Wasm Apps, and More DevFeed: [Kotlin Toolchain 0.12: Multiplatform Library Publishing, Wasm Apps, and More]() Original publisher: [Read original article]() Author: Joffrey Bion Published: 2026-09-03T10:40:05Z Content type: release Language: en Sources: [Kotlin : A concise multiplatform language developed by JetBrains | The JetBrains Blog]() Topics: [toolchain](), [multiplatform](), [compose-hot-reload](), [web applications](), [Spring Boot 4]() Tags: [compose-hot-reload](), [gradle](), [intellij-idea](), [kotlin](), [multiplatform](), [news](), [publication](), [releases](), [toolchain](), [toolchains](), [wasm]() ### AI overview Kotlin Toolchain 0.12.0 adds multiplatform library publishing and previews support for building Wasm modules as web applications. It also includes command-line Compose Hot Reload and changes intended to reduce Maven Central publication files. ### Source excerpt Kotlin Toolchain 0.12.0 is out. This release brings some long-awaited features: multiplatform libraries publication, a preview of Wasm application support, Compose Hot Reload from the command line, and more. Read on for the details, and check the release notes for the full list of changes and bug fixes. Additionally, klibs.io now uses the Kotlin Toolchain [...] ## 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. ## Engineering log: fine-tuning Gemma 4 E4B with LoRA to bring FormAI's coaching on-device DevFeed: [Engineering log: fine-tuning Gemma 4 E4B with LoRA to bring FormAI's coaching on-device]() Original publisher: [Read original article]() Published: 2026-08-28T23:00:00Z Content type: article Language: en Sources: [John O'Reilly]() Topics: [gemma4](), [Fine-tuning](), [lora](), [On-device AI](), [multiplatform](), [LiteRT](), [Android](), [Artificial Intelligence](), [API]() Tags: [ai](), [android](), [api](), [data](), [data-quality](), [engineering](), [fine-tuning](), [gemini](), [gemma](), [gemma-4](), [inference](), [kotlin-multiplatform](), [litert](), [lora](), [multiplatform](), [on-device]() ### AI overview This engineering log describes a prototype that distils FormAI's Gemini-based sports coaching feedback into Gemma 4 E4B fine-tuned with LoRA. The local pipeline uses seed videos, filters inadequate critiques, extracts frames, trains and merges the adapter, then converts the model to LiteRT-LM for possible on-device Android inference. ### Source excerpt ⚠ Note: this post is AI-generated. The text below was written by Claude, and documents findings from a series of Claude Code sessions working on this project -- the experiments, bugs and measurements described are ones that came out of those sessions. The engineering work is real and the numbers were measured rather than estimated, but the write-up is the model's own account of what it did, not a human's independent retelling of it. ## Compose Multiplatform 1.12.0 Released DevFeed: [Compose Multiplatform 1.12.0 Released]() Original publisher: [Read original article]() Author: Elvira Mustafina Published: 2026-08-26T13:28:41Z Content type: release Language: en Sources: [Kotlin : A concise multiplatform language developed by JetBrains | The JetBrains Blog]() Topics: [multiplatform](), [compose-hot-reload](), [MCP Server](), [Model Context Protocol](), [releases](), [Web](), [compose-for-desktop](), [Font]() Tags: [compose-for-desktop](), [compose-for-web](), [compose-hot-reload](), [compose-multiplatform](), [fonts](), [mcp](), [mcp-server](), [model-context-protocol](), [multiplatform](), [releases](), [ui](), [web]() ### AI overview Compose Multiplatform 1.12.0 introduces an experimental MCP server for Compose Hot Reload, enabling AI coding agents to reload applications, inspect rendered UI and semantic trees, simulate interactions, and read logs. The release also adds automatic web font fallback and a more flexible desktop window and dialog API. ### Source excerpt Compose Multiplatform 1.12.0 is out! This version brings new tooling for AI assistants, improvements to web resource management, and finer control over desktop window states. Here are the highlights of this release: For a complete overview of the changes, check out What's new in Compose Multiplatform 1.12.0 or the release notes on GitHub. Get Started [...] ## An insider argues that Google remains committed to Flutter and Dart DevFeed: [An insider argues that Google remains committed to Flutter and Dart]() Original publisher: [Read original article]() Author: Randal L. Schwartz Published: 2026-08-19T16:02:19Z Content type: opinion Language: en Sources: [Flutter Community - Medium]() Topics: [Flutter](), [Dart](), [Google](), [multiplatform](), [WebAssembly]() Tags: [cross-platform](), [dart](), [devrel](), [flutter](), [google](), [mobile-app-development](), [programming](), [software-development](), [wasm](), [webassembly]() ### AI overview This commentary argues, from the author's stated experience as a Flutter Google Developer Expert, that Google remains committed to Flutter and Dart despite restructuring-related concerns and reduced public communication. It cites renewed advocacy and investment in rendering, Dart ergonomics, WebAssembly compilation, and multiplatform performance. ### Source excerpt Every few months, like clockwork, the tech blogosphere gets flooded with the same recycled headline: "Is Flutter Dying?", "Why CTOs Are Quietly Leaving Flutter", or "Why Google is Killing Its Cross-Platform Bet." As someone who has been a Flutter Google Developer Expert for eight years now -- literally from day one of the GDE program -- and a five-decade software industry veteran, I usually just chuckle at the clickbait. "Flutter is dead." -- Said every six months since 2018. Meanwhile: Flutter is kicking tail on every single measurable scale. The alarmist articles point to standard corporate reorganizations, shifting tech job boards, and "state management fatigue" as evidence of Flutter's demise. But having watched this ecosystem evolve from an experimental alpha into an enterprise powerhouse, the reality on the ground is the exact opposite. Here is the real insider story on what's actually happening with Dart and Flutter. 1. The Inside Story: What Happened at Google? When tech companies restructured engineering teams recently, the internet spun a wild narrative that "Google put Flutter on life support." Having direct access to internal teams, I watched the commitment to Dart and Flutter remain steadfast within the organization. However, there was a temporary disconnect: internal engineering activity was roaring, but external communications and public advocacy had slowed down, leaving an information vacuum that clickbait writers eagerly filled. I personally called out to team leaders and senior VPs that this perception gap needed immediate correction. And the leadership responded strongly: Revitalized DevRel & Advocacy: A renewed surge in active community engagement, tutorials, and public roadmaps. Enterprise Adoption Transparency: Showcasing massive internal and external production milestones. Aggressive Core Investment: Deep work on the Impeller rendering engine, Dart 3.x ergonomics, WebAssembly (Wasm) compilation, and native multiplatform performance. Flutter is no ## Exploring Compose HTML for Server Side Rendering DevFeed: [Exploring Compose HTML for Server Side Rendering]() Original publisher: [Read original article]() Author: Frederik Pietzko Published: 2026-08-14T12:15:09Z Content type: article Language: en Sources: [Kotlin : A concise multiplatform language developed by JetBrains | The JetBrains Blog]() Topics: [Compose](), [Server-side rendering](), [Web Development](), [Kotlin](), [multiplatform](), [HTML](), [React](), [Next.js](), [Nuxt.js](), [Svelte]() Tags: [backend](), [compose](), [compose-multiplatform](), [development](), [framework](), [html](), [kotlin](), [multiplatform](), [news](), [react](), [server](), [svelte](), [ui](), [vue](), [web](), [web-development]() ### AI overview An exploratory proposal for extending Compose HTML with a JVM target to support server-side rendering. It argues that Kotlin and Compose components could provide type-safe, reusable server-rendered UI without a separate templating language, while discussing the trade-offs of canvas-based web rendering for SEO, loading times, and accessibility. ### Source excerpt Something is happening in server-rendered web development. React shipped Server Components. HTMX made "hypermedia" cool again. Phoenix LiveView proved a server can push interactive UI updates without a client framework in sight. Every ecosystem seems to be rediscovering the server as a place to render UI, except one: the JVM. What if Compose, the UI [...] ## jetc.dev Newsletter Issue #325 DevFeed: [jetc.dev Newsletter Issue #325]() Original publisher: [Read original article]() Author: CommonsWare Published: 2026-08-04T14:00:00Z Content type: article Language: en Sources: [jetc.dev | Issues]() Topics: [Jetpack Compose](), [releases](), [debug](), [Memory Leaks](), [multiplatform]() Tags: [2026](), [agents](), [compose](), [compose-multiplatform](), [debugging](), [dev](), [jetbrains](), [memory-leaks](), [multiplatform](), [published](), [remote]() ### AI overview jetc.dev Newsletter Issue #325 reviews recent Jetpack Compose releases and related artifacts, including BOM, Material3, Remote Compose, and Wear Compose updates. It also covers the five-year anniversary of Compose 1.0, composition debugging research, Compose Multiplatform content, and a reported memory leak in a Compose for Desktop design system. ### Source excerpt Compose 1.0 five-year anniversary! 1.12.0 RC! Memory leaks! Remote Compose for debugging! And... have you been through the desert with a state with no name?!? ## Kodee's Kotlin Roundup: Birthday Wishes, Shipaton 2026, and the New Kotlin AI Benchmark DevFeed: [Kodee's Kotlin Roundup: Birthday Wishes, Shipaton 2026, and the New Kotlin AI Benchmark]() Original publisher: [Read original article]() Author: Kodee Published: 2026-08-04T08:14:27Z Content type: article Language: en Sources: [Kotlin : A concise multiplatform language developed by JetBrains | The JetBrains Blog]() Topics: [Kotlin](), [AI-assisted coding](), [Benchmark](), [multiplatform](), [Artificial Intelligence](), [App]() Tags: [ai-coding](), [app](), [benchmark](), [developers](), [kotlin](), [kotlin-roundup](), [multiplatform](), [news]() ### AI overview A Kotlin roundup covering Kotlin's 15th anniversary, a public benchmark for AI coding agents, Kotlin's availability in BlueJ, the 2.4.10 release, and RevenueCat Shipaton 2026, where developers can build a Kotlin Multiplatform app. ### Source excerpt Hi everyone! July gave me plenty to celebrate: Kotlin turned 15, got its first public benchmark for AI coding agents, became available in BlueJ, and shipped its 2.4.10 release. Developers can also demonstrate their skills at RevenueCat Shipaton 2026 by building a Kotlin Multiplatform app and competing for the Ship Kotlin Everywhere Award. Meanwhile, X [...] ## jetc.dev Newsletter Issue #324 DevFeed: [jetc.dev Newsletter Issue #324]() Original publisher: [Read original article]() Author: CommonsWare Published: 2026-07-28T14:00:00Z Content type: article Language: en Sources: [jetc.dev | Issues]() Topics: [Compose](), [multiplatform](), [Testing](), [Accessibility](), [Playwright](), [media3](), [ExoPlayer]() Tags: [accessibility](), [compose](), [compose-multiplatform](), [dev](), [exoplayer](), [media3](), [playwright](), [testing]() ### AI overview jetc.dev Newsletter Issue #324 reviews recent Jetpack Compose and Media3 updates, highlights Kotlin and Compose guidance, and presents resources for Compose Multiplatform testing, accessibility scanning, dockable panels, charting, and photo editing. ### Source excerpt PinnableContainer! End-to-end testing! Accessibility scanner! Docked panels! Photo editing! And... do we *really* need Canvas() everywhere?!? ## Everything You Need to Know About Patrol in 2026 DevFeed: [Everything You Need to Know About Patrol in 2026]() Original publisher: [Read original article]() Author: LeanCode Published: 2026-07-24T02:52:52Z Content type: tutorial Language: en Sources: [Flutter Community - Medium]() Topics: [Flutter](), [Mobile Testing](), [ui-testing](), [multiplatform](), [ci](), [Android](), [iOS](), [Web](), [Open Source]() Tags: [ai](), [android](), [automation-testing](), [ci](), [e2e-testing](), [flutter](), [flutter-app-development](), [ios](), [mobile](), [mobile-testing](), [multiplatform](), [open-source](), [ui-testing](), [web]() ### AI overview This article explains Patrol, an open-source multiplatform end-to-end UI testing framework for Flutter apps. It describes how Patrol combines Flutter testing APIs with native Android and iOS UI automation to test Flutter widgets alongside system dialogs, biometric prompts, notifications, and other native interfaces, while integrating with CI pipelines and device farms. ### Source excerpt Author: Katarzyna Szulc from LeanCode Patrol has come a long way from being "just another Flutter testing tool." Today, it powers end-to-end testing across Android, iOS, and Web, integrates with native testing infrastructure, runs on cloud device farms, offers AI-powered testing capabilities, and continues to push the boundaries of what's possible in the Flutter ecosystem. No matter if you've been following Patrol for a while or you're simply looking for the best way to handle Flutter E2E testing, this article is the perfect place to catch up. What exactly is Patrol? Let's break it down Developed by LeanCode, Patrol is a powerful, open-source, multiplatform E2E UI testing framework for Flutter apps that overcomes the limitations of integration_test by handling native interactions. Let's dig deeper into that. Flutter's greatest strength also creates one of its biggest testing challenges. Unlike native apps, Flutter renders its entire UI using its own graphics engine instead of platform-native components. This enables a consistent, pixel-perfect experience across devices, but it also means that native UI automation tools often see a Flutter app as little more than a single canvas. They simply cannot interact with Flutter widgets. The official solution is the integration_test package, which gives tests direct access to the Flutter widget tree. As long as everything happens inside Flutter, it works well. But real apps rarely stay there. System permission dialogs, biometric prompts, notifications, WebViews, and other native UI all exist outside the Flutter runtime, making them inaccessible to integration_test. Patrol bridges this gap. It lets tests interact with both Flutter widgets and native UI elements in a single test. Because Patrol builds on native frameworks such as JUnit and XCTest, it also integrates seamlessly with existing CI pipelines, device farms, and the broader mobile testing ecosystem. If you are new to automating E2E testing in Flutter, you can start by ## The challenge of adding a Web target to DroidconKotlin - Kevin Schildhorn DevFeed: [The challenge of adding a Web target to DroidconKotlin - Kevin Schildhorn]() Original publisher: [Read original article]() Published: 2026-07-22T18:00:00Z Content type: tutorial Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Web](), [multiplatform](), [Kotlin](), [compose-multiplatform](), [wasm](), [browser](), [Firebase]() Tags: [browser](), [browsers](), [compose-multiplatform](), [crashlytics](), [dependencies](), [droidcon](), [firebase](), [kotlin](), [kotlin-multiplatform](), [project](), [wasm](), [web]() ### AI overview This post explains how Touchlab added browser Web support to the DroidconKotlin multiplatform app. It covers dependency limitations, the decision to use Web instead of Kotlin WASM, SQLDelight support, Coil and Okio filesystem issues, the lack of Firebase Crashlytics Web support, and localization and resource handling with Compose Multiplatform. ### Source excerpt We recently added support for Web to our DroidconKotlin app. In this post we'll go over our process and the difficulties of adding a Web target to an existing project. ## jetc.dev Newsletter Issue #323 DevFeed: [jetc.dev Newsletter Issue #323]() Original publisher: [Read original article]() Author: CommonsWare Published: 2026-07-21T14:00:00Z Content type: article Language: en Sources: [jetc.dev | Issues]() Topics: [Compose](), [releases](), [multiplatform](), [Kotlin](), [ui]() Tags: [compose](), [compose-multiplatform](), [dev](), [kotlin](), [newsletter](), [release](), [release-notes](), [ui]() ### AI overview Newsletter Issue #323 reviews new Jetpack Compose alpha updates, discusses reorganizing common behaviors in Compose UI, and highlights official Lottie support for Compose. It also links to Compose Multiplatform projects and resources. ### Source excerpt Alphas! Replacing your base fragment! Official Lottie Compose support! And, I don't think you're ready for this... JellyFab?!? ## Bring your KMP library to NuGet DevFeed: [Bring your KMP library to NuGet]() Original publisher: [Read original article]() Author: Isuru Rajapakse Published: 2026-07-19T13:17:14Z Content type: tutorial Language: en Sources: [Stories by Isuru Rajapakse on Medium]() Topics: [Kotlin Multiplatform](), [NuGet](), [Kotlin](), [C#](), [.NET](), [Gradle](), [multiplatform](), [Library](), [API]() Tags: [android](), [android-app-development](), [androiddev](), [c-sharp](), [gradle](), [interfaces](), [kmp](), [kotlin](), [kotlin-multiplatform](), [library](), [multiplatform](), [net](), [nuget](), [nuget-package]() ### AI overview The article introduces kotlin-native-nuget, a Gradle plugin that packages Kotlin/Native libraries as NuGet packages with generated idiomatic C# bindings. It explains the motivation, configuration, publishing workflow, and supported mappings for Kotlin features such as classes, enums, data classes, coroutines, generics, interfaces, and exceptions. ### Source excerpt with kotlin-native-nuget plugin, you can bring your Kotlin to C# idiomaticallyhttps://medium.com/media/0f185efc67390bbf440bfc33f5675f42/href A little while ago, I gave a talk where I tried to take a library written in Kotlin and hand it to a .NET developer as a NuGet package. By hand. It is 30 minutes of me walking into every brick wall you can imagine - the C ABI, marshalling strings, keeping objects alive across the boundary, making any of it look like C# a human would actually want to use. Introducing kotlin-native-nuget 🪟kotlin-native-nuget plugin auto-binds your kotlin api into C# I turned all of that into a plugin, so you don't have to hit a single one of those walls. You write Kotlin, and out the other side comes a NuGet package with a proper, idiomatic C# API: classes, enums, data classes, coroutines, Flow, generics, interfaces, the works. No FFI boilerplate, no hand-written [DllImport], no "here's a C header, good luck". Your friends over in .NET just `dotnet add package` it and use it like it was C# all along. It's called kotlin-native-nuget, and it's a Gradle plugin. Here's the pitch: GitHub - xxfast/kotlin-native-nuget: A plugin that packages a Kotlin/Native library as a NuGet package with generated C# bindings, and consumes C# NuGet packages from Kotlin The pitch 🛗plugins { kotlin("multiplatform") id("io.github.xxfast.kotlin.native.nuget") version "" } kotlin { mingwX64 { binaries { sharedLib { baseName = "mycatlib" } } } macosArm64 { binaries { sharedLib { baseName = "mycatlib" } } } } nuget { publish { packageId = "MyCatLib" version = "1.0.0" authors = "yourname" description = "My Kotlin/Native library" rootPackage = "com.example.cats" } } That's it. Add the plugin, point it at your native targets, and run the publish task. Out pops a .nupkg. Why though? 🤔 It's a fair question. I got it a lot (even on that talk) Kotlin Multiplatform already reaches an absurd number of places: the JVM, Android, iOS, JS, Wasm, and native desktop. But there's th ## 15 July 2026 Artifact Wave DevFeed: [15 July 2026 Artifact Wave]() Original publisher: [Read original article]() Author: CommonsWare Published: 2026-07-15T21:39:38Z Content type: release Language: en Sources: [The CommonsBlog]() Topics: [Jetpack](), [multiplatform]() Tags: [2026](), [blog](), [jetpack](), [material3](), [multiplatform](), [release](), [sdk](), [updates]() ### AI overview This release update covers five newly observed Jetpack artifacts, including Material3 Ripple receiving multiplatform support, alongside nearly 200 artifact updates overall. ### Source excerpt Here is what we got as new Jetpack artifacts this week! ## jetc.dev Newsletter Issue #322 DevFeed: [jetc.dev Newsletter Issue #322]() Original publisher: [Read original article]() Author: CommonsWare Published: 2026-07-14T14:00:00Z Content type: article Language: en Sources: [jetc.dev | Issues]() Topics: [Jetpack Compose](), [compose-for-desktop](), [multiplatform](), [Android](), [navigation]() Tags: [android](), [compose](), [compose-for-desktop](), [compose-multiplatform](), [dev](), [jetpack-compose](), [module](), [navigation]() ### AI overview This newsletter issue rounds up recent Jetpack Compose developments and related community content, including Compose updates, TV Compose performance, navigation, filter bars, settings-screen DSLs, Compose Multiplatform with SwiftUI, and Compose for Desktop performance. ### Source excerpt SubcomposeLayout! TV Compose! Nav3! Filter bars! Setting screens! And... can we make Compose for Desktop better?!? ## Our Droidcon US 2026 Picks - Sam Hill DevFeed: [Our Droidcon US 2026 Picks - Sam Hill]() Original publisher: [Read original article]() Published: 2026-07-14T00:00:00Z Content type: article Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Mobile](), [multiplatform](), [Kotlin](), [kotlin-native](), [AI Development](), [Artificial Intelligence](), [Rust](), [Testing](), [Gradle](), [scaling]() Tags: [2026](), [ai](), [ai-development](), [android](), [droidcon](), [gradle](), [ios](), [js](), [kmp](), [kotlin](), [kotlin-multiplatform](), [kotlin-native](), [multiplatform](), [rust]() ### AI overview Touchlab previews selected Droidcon USA 2026 talks covering AI and cross-platform mobile development, Kotlin Native project structures, KMP integration with Rust, migration decisions, and mobile testing. ### Source excerpt With Droidcon right around the corner, here are the talks we are most excited about ## Monitor your .NET MAUI apps with Datadog RUM DevFeed: [Monitor your .NET MAUI apps with Datadog RUM]() Original publisher: [Read original article]() Author: Jessica Manheimer; Maël Lilensten Published: 2026-07-08T00:00:00Z Content type: article Language: en Sources: [Datadog | The Monitor blog]() Topics: [.NET MAUI](), [real user monitoring](), [Monitoring](), [SDKs](), [error tracking](), [Network](), [session replay](), [multiplatform](), [Android](), [iOS]() Tags: [android](), [cross-platform](), [digital-experience-monitoring](), [error-tracking](), [ios](), [microsoft](), [monitoring](), [net-maui](), [network](), [real-user-monitoring](), [sdks](), [session-replay]() ### AI overview This article explains how to monitor .NET MAUI mobile applications with the Datadog Real User Monitoring SDK. It covers supported NuGet-based instrumentation for crash reporting, error tracking, network monitoring, Session Replay, and telemetry across iOS and Android apps. ### Source excerpt Use the Datadog .NET MAUI SDK to monitor crashes, errors, ANR events, network performance, and user sessions across iOS and Android apps. ## jetc.dev Newsletter Issue #321 DevFeed: [jetc.dev Newsletter Issue #321]() Original publisher: [Read original article]() Author: CommonsWare Published: 2026-07-07T14:00:00Z Content type: article Language: en Sources: [jetc.dev | Issues]() Topics: [Compose](), [compose-multiplatform](), [navigation](), [multiplatform](), [ui]() Tags: [compose](), [compose-multiplatform](), [dev](), [migration](), [navigation](), [newsletter](), [ui](), [updates]() ### AI overview Jetc.dev Newsletter Issue #321 reviews recent Jetpack Compose updates, including bug fixes and library releases, Nav3 migration experiences, a new 2D layout component, theme-aware Maps for Compose, Compose Multiplatform migration, and other Compose UI developments. ### Source excerpt Compose stable and beta updates! Nav3 migrations! Grid! Effects! And GLFW for Compose for Desktop?!? ## On programming languages, targets, and platforms DevFeed: [On programming languages, targets, and platforms]() Original publisher: [Read original article]() Author: Nicolas Fränkel Published: 2026-06-21T00:00:00Z Content type: opinion Language: en Sources: [Nicolas Fränkel]() Topics: [Programming](), [Programming language](), [multiplatform](), [Scala](), [Java](), [JavaScript]() Tags: [developer](), [development](), [java](), [javascript](), [kotlin](), [languages](), [multiplatform](), [programming](), [programming-languages](), [python](), [rust](), [scala]() ### AI overview A personal discussion of how programming languages have evolved from targeting a single compilation target and platform toward supporting multiple targets. It uses Scala.js as an example and mentions Kotlin and Clojure as other JVM-originated languages targeting JavaScript. ### Source excerpt I started as a Java developer, but for some time now, I have broadened my horizons. Recently, I thought about how early languages were dedicated to a single target and platform, and now they are broadening their focus. In this post, I want to write down my thoughts in the hope that it may be useful to others, probably to my future self. Definitions You may have been wondering about the title terms. ## Antigravity TagSpotter - KotlinMultiPlatform evolve DevFeed: [Antigravity TagSpotter - KotlinMultiPlatform evolve]() Original publisher: [Read original article]() Published: 2026-06-14T19:10:33Z Content type: opinion Language: en Sources: [maiatoday]() Topics: [kotlinmultiplatform](), [multiplatform](), [Android](), [compose-multiplatform](), [Kotlin](), [iOS](), [Gradle](), [Web](), [Open Source]() Tags: [ai](), [ai-agents](), [android](), [antigravity](), [code](), [compose](), [compose-multiplatform](), [git](), [kmp](), [kotlin](), [kotlinmultiplatform](), [migration](), [tests]() ### AI overview The article documents an attempt to migrate the TagSpotter Android app toward Kotlin Multiplatform using Antigravity 2.0 and parallel agents. It describes preparation such as modularizing the codebase, adding tests, researching KMP migration, and planning support for iOS, Android, Desktop, and Web, while retaining Android-specific features such as the Wear app. ### Source excerpt The Challenge - bring on the subagents Can I make my TagSpotter Android app be multi-platform in a weekend using Antigravity 2.0 and a swarm of agents running in parallel? Can I do this even though I don't know how to use Xcode and I don't want to break my existing app. This was the question I had. TagSpotter is medium featured Android app I built two weeks ago. I use it to capture interesting and favourite spots in the city like unusual graffiti or yarn bombed sculptures. It has a fair few features including: Capture the places by camera with location Upload a photo AI lookup to find info on the internet from the photo, links, title, artist and suggested tags Export the spots in a zip file and import them again. This is how I share my favourite spots with friends. Make field notes by typing or speaking Share my favourites to Google maps for easy navigation Good category and location based filtering Wear app that can list started spots and navigate to a spot on the watch A good challenge because it isn't just a hello world app. The prep Because the clock would be ticking, I did a little bit of prep to make sure I had everything ready. Prep the codebase Clean up the app, no warnings, lint issues or unused imports Make sure the screens work in landscape, desktop mode will need this Split the app into feature based and pure kotlin modules. I know Compose multiplatform and pure kotlin modules can easily be re-used. Put some tests in place Checked everything works and make a tag in git incase Antigravity borked the project. Light research I collected a few salient links about KMP migration. A good blog post, some info on project structure and a link to the open source kmp libraries I might need. Nitty Gritty Friday evening, let's go. Make a plan I want to convert this app to a KMP app that supports iOS, Android, Desktop and Web. The other platforms do not have to support all features, e.g. the wear app. But Android still has to support this feature. I want to share as mu ## The Future of KMP's iOS Interop - Daniel Bertoldi DevFeed: [The Future of KMP's iOS Interop - Daniel Bertoldi]() Original publisher: [Read original article]() Published: 2026-06-12T00:00:00Z Content type: comparison Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Kotlin Multiplatform](), [Swift](), [Objective-C](), [Compiler](), [multiplatform]() Tags: [compare](), [experimental](), [interop](), [ios](), [kmp](), [kotlin](), [kotlin-multiplatform](), [native](), [objective-c](), [production](), [skie](), [swift](), [swift-export]() ### AI overview This comparison examines Kotlin Multiplatform iOS interoperability through Kotlin's experimental Swift Export and the Objective-C bridge enhanced by SKIE. It compares their generated output, capabilities, limitations, and tradeoffs. ### Source excerpt Kotlin's new Swift Export feature promises to eliminate the Objective-C middleman and generate native Swift APIs directly from your KMP code. But with SKIE already solving many of the same pain points in production today, which approach should your team bet on? We break down the capabilities, limitations, and tradeoffs of both. ## How to use Koin Compiler in a Multimodule Project? DevFeed: [How to use Koin Compiler in a Multimodule Project?]() Original publisher: [Read original article]() Author: Gabriel Bronzatti Moro Published: 2026-06-11T08:47:55Z Content type: tutorial Language: en Sources: [Koin developers - Medium]() Topics: [koin](), [compose-multiplatform](), [multiplatform](), [Gradle](), [Kotlin](), [implementation]() Tags: [build](), [compose](), [compose-multiplatform](), [gradle](), [how-to](), [implementation](), [koin](), [kotlin](), [migrate](), [multi-module-project](), [plugin]() ### AI overview A tutorial on migrating a Compose Multiplatform multi-module project to the Koin Compiler. It covers the required Kotlin and Koin versions, configuring the compiler dependency through Gradle, creating a convention plugin, applying it to modules, and updating module initialization. The article reports replacing an approximately 80-line custom Gradle plugin with a simpler approximately 30-line setup while retaining compile-time safety through the K2 compiler. ### Source excerpt Hey everyone! Today we're diving into how to use the Koin Compiler in a Compose Multiplatform multi-module project. In the previous article, we explored how to migrate a multimodule setup to Koin Annotations, using a convention Gradle plugin to move forward in small, safe steps. We'll follow that same approach diving deep into a project called MovieDB-App👋 A sticky note attached to a wall with the words "how to" written on it - Unsplash by walls_ioFirst step: Update your project, if necessary 🚀 Your project is eligible to support the Koin Compiler if it meets at least the following requirements: ✅ Kotlin 2.3.x or higher (K2 is required) ✅ Koin 4.2.x or higher Our sample project is using the following stack overview: 🤖 AGP: 9.1.0 🧩 Kotlin: 2.3.20 💉 Koin: 4.2.1 🏷 Koin Annotations: 2.3.1 Second step: Configure Koin compiler dependency Let's add our Koin Compiler dependency into the libs.versions.toml : #gradle/libs.versions.toml [versions] koin-compiler-plugin = "1.0.0" ... [libraries] koin-compiler-plugin = { group = "io.insert-koin", name = "koin-compiler-gradle-plugin", version.ref = "koin-compiler-plugin" } Now, let's run Gradle Sync 🐘 Our mission is to create a conventional plugin in our build-logic so we can migrate the project module by module, taking small and safe steps along the way. To achieve that let's add the koin compiler dependency as a depency of our build-logic: // build-logic/build.gradle.kts ... dependencies { implementation(libs.koin.compiler.plugin) } After syncing Gradle, it's time to create our conventional plugin: // build-logic/src/main/kotlin/plugins/KoinCompilerSetupPlugin.kt package plugins import org.gradle.accessors.dm.LibrariesForLibs import org.gradle.api.Plugin import org.gradle.api.Project import org.gradle.kotlin.dsl.configure import org.gradle.kotlin.dsl.dependencies import org.gradle.kotlin.dsl.the import org.koin.compiler.plugin.KoinGradleExtension // Ref: https://github.com/InsertKoinIO/koin-compiler-plugin/blob/main/docs/CASE_S ## The future of mobile development DevFeed: [The future of mobile development]() Original publisher: [Read original article]() Published: 2026-06-01T00:00:00Z Content type: opinion Language: en Sources: [Kt. Academy]() Topics: [Mobile](), [Compose](), [Jetpack Compose](), [multiplatform](), [Development](), [SwiftUI](), [Web Development]() Tags: [compose](), [css](), [ios](), [jetpack-compose](), [kotlin](), [mobile](), [mobile-development](), [multiplatform](), [react](), [workshop-learning-programming]() ### AI overview This video transcript examines how mobile development has changed, arguing that declarative UI frameworks--especially Jetpack Compose and SwiftUI--have improved the development experience. It emphasizes Compose's multiplatform support across Android, iOS, desktop, and web, along with responsive design, animations, and Kotlin-based concurrency features. ### Source excerpt What the future holds for mobile development, and how it changed in recent years. [Next page]()