Low-latency audio, adaptive UI, and real-time networking – for web, desktop, and Android. Phil Burk shows how KMP, WebAudio, coroutines, and Ktor power two cross-platform music creation apps. Hear how it all comes together: kotl.in/j3i0ww

What's great about Kotlin? What's frustrating? What should we finally fix? Tell us in our annual developer survey (15 min). 🎟️ Bonus: a chance to win KotlinConf tickets! jb.gg/e5bb41

📢 Kotlin 2.5.0-Beta2 is out! Here are some of the highlights: ✅ Language: Stable name-based destructuring in only-syntax mode, unused return value checker, and improved compile-time constants ✅ Standard library: New experimental functions for simplifying common patterns with if expressions and experimental support for Unicode code points ✅ Kotlin/JVM: Support for Java 28 ✅ Kotlin/Native: Incremental compilation enabled by default on Apple targets and Swift export in Beta with a new DSL ✅ Kotlin Multiplatform: New publication format for multiplatform libraries ✅ Kotlin/JS: Support for the es2020 target ✅ Kotlin compiler: More consistent inline function behavior during klib compilation Try it out: kotl.in/2-5-0-beta2

Can web developers use KMP without leaving Cursor? Denis Ambatenne demonstrates how Kotlin LSP, Hot Reload, and AI can help web teams build KMP apps and share Kotlin business logic with existing JavaScript and TypeScript projects. Open the door to KMP: kotl.in/crqgvg

🧭 As an Android developer, you already know NavController and NavHost. Move them into common code and use the same navigation model – with type-safe routes, one graph, and one back stack – across Android, iOS, desktop, and web. Set up navigation 👇 kotl.in/sjj4dl

Kotlin and Swift may look similar, but their semantic differences make perfect interoperability a serious challenge. Gleb Lukianets explored the compromises behind Kotlin Swift Export at KotlinConf’26. Watch the talk kotl.in/7bwxao

Building production services with Ktor? Simon Vergauwen’s #KotlinConf talk is a practical walkthrough of the trade-offs that matter: configuration, routes, DI, lifecycle, coroutines, testing, security, deployment, and observability. Watch 👇 kotl.in/kvdf8x

🗂️ Three takes on Compose Multiplatform navigation: ⚓ Voyager – screen-based navigation, small API surface. kotl.in/xil84o 🌳 Decompose – lifecycle-aware components with routing. kotl.in/015i59 🔌 Circuit – presenters, state, and navigation, from Slack. kotl.in/nbegww Compare them on Klibs.io 👇 kotl.in/z70oa9

📢 The Kotlin compiler will soon require JDK 17 or newer to run. 2.5.0: Running the compiler on older JDKs produces an error, with a flag to opt out. 2.5.20-Beta1 and later: JDK 17 or newer is required, with no opt-out. If this affects your setup or CI, share your use case on YouTrack 👇 kotl.in/w6kjee

Conference season is in full swing! After two great days at @swift_leeds, we’re now at @KotlinLeeds for the next two days. Check out the agenda 👉kotlinleeds.co.uk/schedule. And if you’re here, stop by and say hi! 👋💜

Cobrainer’s six-person team supports 10,000+ active users with a production AI stack built in Kotlin. Type-safe contracts, coroutines, cross-provider fallbacks, and 5× higher throughput after removing blocking code from affected workflows. Read more: kotl.in/sav2z6

What happens when Compose Multiplatform meets agentic AI? John O’Reilly demonstrates how Koog can power Android, iOS, and desktop apps using local tools, an MCP server, and both cloud and on-device LLMs. See the full-stack approach: kotl.in/lln3g8

What if Kotlin developers could bring powerful AI directly onto devices? Michal Harakal introduces SKaiNET, an open-source multiplatform AI framework that helps developers build apps with local, on-device AI and run lightweight models completely offline. Check out SKaiNET: kotl.in/99p8qd

Moving from Java to Kotlin isn’t a single switch you flip. It’s a decision tree. If you are planning a migration, here are the four proven paths used by teams adopting Kotlin: 1️⃣ The complete rewrite Best for: Small codebases. The catch: Rewriting a codebase from scratch gives you the cleanest, most idiomatic Kotlin code. This is a great approach for a new microservice, but for large codebases, this approach tends to be prohibitively expensive. 2️⃣ IDE auto-conversion Best for: Medium-sized codebases with dedicated refactoring time. The catch: Manual refinements are mandatory. The IDE provides a starting point, but the raw output is literal and far from idiomatic. Pro Tip: Add NonNull / Nullable annotations (like jspecify) to your Java code first – the auto-conversion produces much better results. 3️⃣ AI-assisted conversion Best for: Larger codebases with robust testing infrastructure. The catch: Manual review is mandatory. AI can potentially produce more idiomatic results than basic auto-conversion, but you need comprehensive testing coverage to catch AI hallucinations and extensive code review for logical correctness. 4️⃣ Auto-conversion at scale Best for: Massive codebases requiring systematic transformation. The catch: Currently, there's no official tooling for converting Java codebases to idiomatic Kotlin at scale. Additionally, if not planned carefully, engineers can easily be overwhelmed by the flood of pull requests resulting from the automated conversion. The solution: Success requires building custom rule-based, deterministic processes. Tech giants like Meta and Uber had to build their own internal tools to safely migrate their massive repositories. You'll need a similar strategy to ensure consistency across millions of lines of code. Evaluate your architecture, assess your test coverage, and choose your path wisely. Ready to build your migration strategy? Get the full Kotlin Adoption Guide with a detailed decision matrix here: 👉 kotl.in/guide

⚙️ Your KMP project builds on your machine. Does it build on every pull request? Set up GitHub Actions for a KMP project, with shared tests, an Android APK, an iOS simulator build on every push to main, and a single reusable Gradle setup shared across all jobs. Copy the workflow 👇 kotl.in/q8sn2c

Can a Compose app feel native on both Android and iOS? Mohamed Ben Rejeb showed how Calf maps components to their native counterparts – Material on Android and Cupertino on iOS – all while sharing the same codebase. Watch the talk from KotlinConf’26: kotl.in/gpajuh

They call it Penguin Island! 🐧 Kodee recently visited Tencent's new headquarters to celebrate Kotlin's 15th birthday with the Kuikly team. It was great to spend some time together and see what the team is working on with Kotlin Multiplatform. Thanks for the warm welcome and a lovely celebration!

What does a database-first workflow look like with Exposed? This #KotlinConf talk shows how the IntelliJ IDEA Exposed plugin lets you generate Exposed table definitions from an existing database, and then use Kotlin’s SQL DSL for clean, reusable queries. Watch 👇 kotl.in/5dilho

🚀 Starting a new Kotlin Multiplatform project? Try the Kotlin Toolchain! Create a project with `kotlin new` and enjoy automatic setup, smoother agentic workflows, SwiftPM support, and faster Kotlin/Native rebuilds. Explore what's new 👇 kotl.in/3atm8d