Show Notes
Watch the Talk Here: https://youtu.be/VVf6txPZk3YIn this KotlinConfersations'26 episode, Sony engineer Sergio Carrilho shares how his team used Kotlin Multiplatform to build and evolve the Sony Sound Connect app. He talks about the challenges of Bluetooth development, hardware-software integration, and merging apps built on different tech stacks. Sergio also explains why architecture was the key to creating a seamless experience across Android and iOS.
More from Talking Kotlin
In this Kotlin Conversations episode from KotlinConf 2026, Dan Kim shares how he’s building full-stack web apps entirely in Kotlin using Ktor, Compose, and WebAssembly. He talks about KMP, the future of WASM on the web, and whether Android developers can finally become frontend developers without writing JavaScript. The conversation also explores AI tools, vibe coding, and why the human side of engineering still matters most.
How can Kotlin help teams build safer financial software, migrate legacy systems, and move faster without increasing risk?In this episode of Kotlin Conversations from KotlinConf 2026, we talk with Yuri Geronimus, Senior Staff Engineer and Chief Architect at Verifone, about using Kotlin in the world of payments and financial technology — where software defects, compliance requirements, and certification tests can have serious consequences.
Three Android developers. Zero Swift experience. A two-month deadline.At KotlinConfersations'2026, Suhyeon (Leah) Kim shares how her team used KMP to build and ship a brand-new iOS app despite having no iOS developers on the team.
In this KotlinConf'26 interview, Huyen sat down with Jake Wharton to talk about the past, present, and future of Kotlin and software development. And, of course, a bit about AI.
The Kotlin ecosystem is full of powerful tools and frameworks — and in this episode of Talking Kotlin, we’re diving deep into Exposed, JetBrains’ Kotlin SQL library, which recently reached its 1.0 release.Sebastian and Márton sit down with Chantal from the Exposed team to explore what Exposed is, where it came from, and how it helps developers work with databases in a Kotlin-first way. From type-safe SQL DSLs and lightweight DAO support to JDBC, R2DBC, Ktor, Spring Boot, migrations, and future KMP plans — this episode covers the past, present, and future of Exposed.You’ll learn:What makes Exposed different from traditional ORMsHow the DSL and DAO APIs work togetherWhy Exposed 1.0 required a major architecture redesignHow R2DBC support enables non-blocking database accessHow Exposed integrates with Ktor and Spring BootWhat’s coming next: migrations, plugins, DAO improvements, and KMP supportThe surprisingly charming origin story behind the Exposed cuttlefish mascotWhether you’re already using Exposed or just looking for a Kotlin-friendly way to work with SQL databases, this episode is packed with practical insights and behind-the-scenes stories from the team building it.Try Exposed Read the docs Join the discussion on Kotlin Slack Report issues or share feedback on YouTrack