# KotlinConf Published articles for KotlinConf. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Three Gradle Talks from KotlinConf 2026 (and What to Steal from Each) DevFeed: [Three Gradle Talks from KotlinConf 2026 (and What to Steal from Each)]() Original publisher: [Read original article]() Author: Laura Kassovic Published: 2026-07-28T04:00:00Z Content type: article Language: en Sources: [The Gradle Blog]() Topics: [Gradle](), [Kotlin](), [Groovy](), [ide](), [Scripting](), [Refactoring]() Tags: [2026](), [best-practices](), [build](), [build-tool](), [conference](), [developer](), [dsl](), [event](), [gradle](), [groovy](), [ide](), [kotlin](), [kotlinconf](), [refactoring](), [script](), [scripting](), [talk](), [talks]() ### AI overview The article reviews three Gradle talks from KotlinConf 2026. It explains the progression from Groovy build scripts to the Kotlin DSL and early Declarative Gradle, emphasizing the problems each approach addresses. It also introduces Gradle best practices for organizing and optimizing builds. ### Source excerpt Every year I tell myself I'll watch every conference talk I missed. Every year I get through maybe three before a build breaks and I get pulled back into real life. KotlinConf is the one event where I actually follow through, partly because the talks are short and dense, and partly because a good chunk of my coworkers and friends are on stage. This year in Munich, three of them talked about Gradle: Paul Merlin on the history of our DSLs, Stefan Wolf on best practices, and Marcin Mycek on Declarative Gradle for Kotlin. I watched all three so you can decide which ones are worth your fifteen minutes. A Tale of the Gradle DSLs -- Paul Merlin Paul has been inside Gradle's DSL machinery for years, which makes him exactly the right person to tell this story and exactly the wrong person to pretend the early days were clean. The talk traces how build logic went from Groovy, to the Kotlin DSL, to Declarative Gradle. The useful part isn't the timeline. It's that each of those was solving a real problem the previous one couldn't. Groovy gave us a flexible, dynamic scripting language, which was great right up until you wanted your IDE to tell you what was valid. The Kotlin DSL brought static typing, real autocompletion, and refactoring that doesn't rely on hope. That's why the Kotlin DSL is now the default for new Gradle builds. Declarative Gradle is the next swing: describe what your build is rather than script how it runs. The honest through-line is that none of these fully replaces the last one. Kotlin DSL is where most people should be today. Groovy still runs an enormous amount of the world's build logic and isn't going anywhere fast. Declarative Gradle is early but points at where things are headed. Real talk: if your build scripts are still Groovy and still working, you don't have to panic-migrate this weekend. But if you're starting something new, reach for the Kotlin DSL and let the IDE carry some of the weight. 📺 Watch the talk 10 Gradle Best Practices Every Kotlin Deve ## Live coding with dir stepper DevFeed: [Live coding with dir stepper]() Original publisher: [Read original article]() Published: 2026-07-16T00:00:00Z Content type: article Language: en Sources: [Jake Wharton]() Topics: [intellij-platform](), [IntelliJ IDEA](), [Git](), [ide](), [Code](), [Documentation]() Tags: [code](), [coding](), [git](), [ide](), [intellij-idea](), [intellij-platform](), [kotlinconf](), [plugin](), [presentation](), [procedural](), [refactoring]() ### AI overview The article describes creating a workflow for live-coding presentations after finding that Git commits and interactive rebases were cumbersome for managing sequential coding steps. It explores using IntelliJ IDEA as an extensible platform for a tool that can move through steps, jump to completed states, refactor steps, and keep the process unobtrusive for the presenter and audience. ### Source excerpt Two months ago I gave my first ever live programming talk at KotlinConf. It was called "Talking to terminals (and how they talk back)", and you can watch it here. I've previously done slide-heavy talks which contained small demos or navigating through an existing codebase. Since this talk was starting from nothing, I decided to just write all the code from nothing. This meant spending the majority of the time in the IDE, but also figuring out how to remember what I was supposed to be writing at each step. Making the wrong choice The exceedingly obvious solution to having a series of steps in a live coding presentation is a git repo and a commit for each step. Unfortunately, this is a huge pain in the ass and really doesn't work at all (at least not for me). I started with commits, but by the 7th or 8th commit I was spending more than half my time doing interactive rebases over the entire history. Need a function in step 8 that should've been extracted between step 3 and 4? That's another 10 minutes rewriting history. Because it's a small set of files that are changing, every commit conflicts with any changes to history. It's also not clear how you actually move through the history. We want to start from nothing and move forward through history. Generally, git helps you jump backwards from the latest, not stepping forward from the oldest. It's not impossible, it's just clearly going against the grain. The problem, defined Now thoroughly enjoying this distraction from writing the actual talk, I distilled what I was trying to solve. Ability to manually write the changes required or to simply jump to the finished step. Some steps are important to watch unfold while others are procedural. This also can help with time management when I (inevitably) run low on time. Easily refactor steps as I go. Later steps often requiring refactoring previous ones to minimize the diff. As the talk evolves I want to add or merge steps. Nearly invisible to me and the viewer. I don't want t ## Deconstructing OkHttp DevFeed: [Deconstructing OkHttp]() Original publisher: [Read original article]() Author: Jesse Wilson Published: 2026-05-22T12:00:00Z Content type: article Language: en Sources: [Public Object]() Topics: [Library](), [Network](), [Code](), [Kotlin](), [implementation](), [Cache](), [certificates]() Tags: [architecture](), [cache](), [certificates](), [https](), [implementation](), [kotlinconf](), [ktor](), [library](), [network](), [okhttp](), [performance](), [presentation](), [retrofit](), [testing]() ### AI overview A KotlinConf talk examines OkHttp's implementation rather than its basic usage, covering interceptor-based architecture, connection lifecycles, cache state machines, URL decoders, HTTPS testing certificates, performance, and extension mechanisms. ### Source excerpt I presented this at KotlinConf on May 22, 2026. Also available on slides, YouTube, and Speaker Deck. OkHttp is a popular library for making network calls. You might use it directly, or with Ktor, Retrofit, Coil, or gRPC. But this is not a talk on how to use OkHttp. Instead, ## Opinionated Ktor Services DevFeed: [Opinionated Ktor Services]() Original publisher: [Read original article]() Author: Simon Vergauwen Published: 2026-05-21T00:00:00Z Content type: opinion Language: en Sources: [nomisRev]() Topics: [Ktor](), [Kotlin]() Tags: [2026](), [conference](), [kotlin](), [kotlinconf](), [ktor](), [microservices](), [opinions](), [services](), [talk]() ### AI overview The author describes a KotlinConf 2026 talk about using Ktor and the Kotlin ecosystem to build robust, maintainable, and scalable services. The talk presents the author's opinions on structuring Ktor services and choosing libraries, based on experience with teams. ### Source excerpt Today I gave a talk at KotlinConf 2026 in Munich about "Opinionated Ktor Services". In this talk, I shared my experience and opinions on how to build robust, maintainable, and scalable services using Ktor and the Kotlin ecosystem. ## Achieving Fast Inner Dev Loops with Gradle: Configuration Cache and Beyond DevFeed: [Achieving Fast Inner Dev Loops with Gradle: Configuration Cache and Beyond]() Original publisher: [Read original article]() Author: Alex Semin Published: 2026-05-20T04:00:00Z Content type: article Language: en Sources: [The Gradle Blog]() Topics: [Gradle](), [code productivity](), [build performance](), [build times](), [Development]() Tags: [build](), [build-tool](), [compilation](), [context](), [developer-productivity](), [flow](), [gradle](), [incremental](), [kotlinconf](), [parallelism](), [productivity]() ### AI overview This article explains how Gradle is working to accelerate inner developer loops. It describes the shift from execution time to configuration time as the main build bottleneck in large codebases, while highlighting configuration cache, incremental builds, build cache, and parallelism as approaches to reduce waiting and preserve developer flow. ### Source excerpt How many engineers in your organization have to sit idle for 10 or more minutes just to rebuild the app locally after a small change? If you're an engineering leader, build engineer, or part of a developer productivity team, you're not alone in facing this challenge. Building complex software is inherently demanding, but the time your developers spend waiting has a profound impact beyond just the literal minutes lost. It fundamentally disrupts their psychological flow. "There are like these time scales of psychological flow, right? So if something takes longer than a minute, you already start planning for it... you suffer from context switch as well. If it's 1 second, that's where we want to be right in that seamless state of flow. And if it's less than one second, then you feel it's like magic... productive developers are happy developers." -- Rodrigo Oliveira When developers have to wait, their attention drifts, and the cost of context switching destroys their momentum. Our goal as enablers of developer productivity should be to eliminate this friction, bringing that feedback loop as close as possible to the "magical one second". In a recent presentation at KotlinConf 2025, Gradle engineers Rodrigo Oliveira and Alex Semin detailed how Gradle Build Tool is evolving to keep developers in that productive, happy "flow state". By tackling the most significant bottlenecks in modern software builds, Gradle is paving the way for incredibly fast inner developer loops. If you prefer to watch the presentation recording, you can find it here. The shifting bottleneck: From execution to configuration On every invocation, Gradle goes through three distinct phases: initialization, configuration, and execution. Historically, when we optimized Gradle builds, we focused almost exclusively on the execution phase. This is when the majority of work expected by a developer happens: production sources compilation, test execution, etc. For years, execution was the longest phase. We tackled thi ## The KotlinConf 2026 talks that we're excited about - Kevin Schildhorn DevFeed: [The KotlinConf 2026 talks that we're excited about - Kevin Schildhorn]() Original publisher: [Read original article]() Published: 2026-03-03T00:00:00Z Content type: opinion Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Kotlin Multiplatform](), [Kotlin](), [compose-multiplatform](), [kotlin-native](), [iOS development](), [ui](), [amazon](), [Library]() Tags: [amazon](), [android](), [compose-multiplatform](), [ios](), [ios-development](), [js](), [kotlin](), [kotlin-multiplatform](), [kotlin-native](), [kotlinconf](), [library](), [talks](), [ui]() ### AI overview A Touchlab commentary selects KotlinConf 2026 talks covering Kotlin/Native integration, Kotlin Multiplatform project organization and compilation times, Compose Multiplatform UI performance and animation, and iOS development with KMP at Amazon. ### Source excerpt The KotlinConf 2026 schedule was recently announced and there are a lot of talks to be excited about. We decided to compile a list of the talks we're excited to see. ## 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. ## KotlinConf 2025 Announcements DevFeed: [KotlinConf 2025 Announcements]() Original publisher: [Read original article]() Published: 2025-06-03T00:00:00Z Content type: article Language: en Sources: [Kt. Academy]() Topics: [Kotlin](), [destructuring](), [exceptions](), [union types](), [syntax](), [Safe-Call Operator]() Tags: [announcements](), [destructuring](), [exceptions](), [kotlin](), [kotlinconf](), [new-features](), [safe-call-operator](), [syntax](), [union-types](), [workshop-learning-programming]() ### AI overview The article summarizes announcements from KotlinConf 2025, including K2 becoming stable, upcoming name-based destructuring, and rich errors with language-level support for result-or-error types and related operators. ### Source excerpt The greatest announcements from KotlinConf 2025. ## KotlinConf 2025 Highlights Backend-Oriented Kotlin Language and Ecosystem Updates DevFeed: [KotlinConf 2025 Highlights Backend-Oriented Kotlin Language and Ecosystem Updates]() Original publisher: [Read original article]() Author: Julien Published: 2025-05-22T14:34:02Z Content type: opinion Language: en Sources: [Thoughts, stories and ideas.]() Topics: [Kotlin](), [jetbrains](), [Back end](), [Programming](), [destructuring](), [Error Handling](), [Null-Safety]() Tags: [2025](), [conference](), [destructuring](), [development](), [error-handling](), [jetbrains](), [jvm](), [kotlin](), [kotlinconf](), [null-safety](), [programming]() ### AI overview A personal assessment of KotlinConf 2025 that focuses on JetBrains' renewed attention to backend developers. The article highlights Kotlin language updates including name-based destructuring and richer error handling, while also discussing the K2 compiler and Kotlin's backend developer experience. ### Source excerpt With their keynote that JetBrains intentionally started putting backend developers in the spotlight again. They made big, impactful announcements, both at an ecosystem and language levels and I can't wait to try out all of the new goodies. ## Introducing Compose-ur-Pres DevFeed: [Introducing Compose-ur-Pres]() Original publisher: [Read original article]() Author: Salomon BRYS Published: 2024-06-25T11:35:42Z Content type: release Language: en Sources: [Kodein Koders - Medium]() Topics: [compose-for-desktop](), [Kotlin](), [multiplatform](), [Open Source](), [Documentation](), [Template](), [wasm]() Tags: [android](), [compose](), [compose-multiplatform](), [desktop](), [documentation](), [kotlin](), [kotlinconf](), [open-source](), [project](), [wasm]() ### AI overview This article introduces Compose-ur-Pres, or CuP, an open-source presentation tool written in Kotlin with Compose for Desktop. It lets developers create and animate presentation slides as composable application screens, with features including slide navigation, transitions, an overview, speaker tools, and experimental web export. ### Source excerpt A tool that allows you to write a presentation slide deck in Kotlin with Compose. https://medium.com/media/92b00e09e5e75db453796863708f60e6/href I've always been frustrated with regular presentation tools, such as Keynote, Powerpoint, or Google Slides. While I do not want to deny their quality, I simply do not believe these tools can implement everything that I have in mind. After all, as an application programmer, creating screens and animations is what I do. I have many ideas of how I want to present and animate my content, and I do not want to be constrained by a WYSIWYG editor. Since I program my screens, why not program my slides? When I first encountered Reveal.js, I thought "OK, that's what I want, but I want it in Kotlin". At that time, Compose multiplatform did not exist, so I wrote my first version with Kotlin-React. Then came Compose multiplatform and more specifically what was then known as Compose Web and is now named Compose HTML. So, of course, I rewrote the entire tool using that. I used it for several presentations (including my presentation at KotlinConf 23). At the same time Compose Desktop became stable and the new Compose Web with Wasm was introduced, my frustration with CSS (especially CSS animations) grew stronger. I wanted to position my content pixel by pixel, and frame by frame, just like Compose allowed me to. So I rewrote this presentation tool a third time, but this time for Compose desktop, and named it "Compose-ur-Pres", or "CuP" for short. A few weeks ago at Android Makers 24, I was thrilled to open source that tool. You can read its documentation, start creating your slides with a template project, and of course access its sources. The pitch of Compose-ur-Pres is very simple: write and animate your slides just like you would your application screens. Focus on your slide content, and CuP will take care of: Creating & managing the application window. Displaying your slides in order and animate transitions between them. Showing an overv ## KotlinConf: The History, Growth, and Appeal of Kotlin's Developer Conference DevFeed: [KotlinConf: The History, Growth, and Appeal of Kotlin's Developer Conference]() Original publisher: [Read original article]() Published: 2024-03-05T00:00:00Z Content type: article Language: en Sources: [Kt. Academy]() Topics: [Kotlin](), [jetbrains](), [Programming](), [Android]() Tags: [conference](), [jetbrains](), [kotlin](), [kotlinconf](), [networking](), [talks](), [tech-conference](), [workshop-learning-programming](), [workshops]() ### AI overview The article traces KotlinConf's origins at JetBrains, beginning with its first edition in San Francisco in 2017. It describes the conference's talks, workshops, networking opportunities, international reach, and growth in speakers, sessions, workshops, and expected attendance through KotlinConf'24. ### Source excerpt Exploring the Biggest Kotlin Conference ## KotlinConf '23 Recap - Touchlab DevFeed: [KotlinConf '23 Recap - Touchlab]() Original publisher: [Read original article]() Published: 2023-04-21T15:28:47Z Content type: article Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Kotlin](), [iOS](), [Mobile](), [Swift](), [Gradle](), [Google](), [jetbrains]() Tags: [announcement](), [community](), [conference](), [google](), [gradle](), [ios](), [jetbrains](), [kotlin](), [kotlinconf](), [mobile](), [recap](), [swift]() ### AI overview A recap of KotlinConf '23 covering Touchlab joining the Kotlin Foundation, the SKIE Swift-Kotlin Interface Enhancer, and Touchlab Pro tools for mobile teams adopting Kotlin Multiplatform. ### Source excerpt Catchy thing ## KotlinConf'23 -- Meta-programming with KSP and Kotlin compiler plugins by Tadeas Kriz DevFeed: [KotlinConf'23 -- Meta-programming with KSP and Kotlin compiler plugins by Tadeas Kriz]() Original publisher: [Read original article]() Author: Matthew Dolan Published: 2023-04-15T01:27:49Z Content type: opinion Language: en Sources: [Stories by Matthew Dolan on Medium]() Topics: [Kotlin](), [Compiler](), [Programming]() Tags: [android](), [android-app-development](), [compilation](), [compiler](), [documentation](), [how-to](), [java](), [kotlin](), [kotlin-compiler](), [kotlinconf](), [ksp]() ### AI overview The article reflects on a KotlinConf'23 talk about metaprogramming with KSP and Kotlin compiler plugins. It compares approaches for generating or altering code during compilation, discusses Kotlin compiler extensions and JVM IR, and recommends using KSP where possible. ### Source excerpt KotlinConf'23 -- Meta-programming with KSP and Kotlin compiler plugins by Tadeas Krizhttps://medium.com/media/5209f3d53633efc6fd3a4ca4879001cc/href I really enjoyed watching the talk on meta-programming by Tadeáš Kříž at KotlinConf'23 where he provided an excellent overview of the two main options for generating and/or altering code during compilation. It was great to see the pros and cons of each option even compared to Java's annotation processing which more developers are familiar with. "there are the things that break your heart 💔" The lack of documentation around writing a Kotlin Compiler Plugin makes getting started hard work. Fortunately the speaker provides plenty of links to resources you can use to help you on your way -- I wish I'd seen this talk before writing my own compiler plugin last week! Perhaps you were aware of the move to JVM IR; for most Kotlin developers the compiler implementation doesn't really matter unless, of course, you are writing a compiler plugin. As such it was interesting to have an overview of both SyntheticResolveExtension and IrGenerationExtension. How do you decide what to use for meta-programming? Prefer KSP where possible. The talk mentions plenty of examples of KSP and Kotlin Compiler Plugins you can check out to help you write your own plugin. Additionally, during the conference I had the opportunity to talk with Tadeas about a Kotlin Compiler Plugin he's been writing, Skie (pronounced sky) which, by the way, looks awesome. We both have our fingers crossed that it can become open source so the Kotlin community has another good example of how to write a compiler plugin. "What do you do next. Hopefully profit." You can find my thoughts on more KotlinConf'23 talks at KotlinConf'23. Please let me know your thoughts. Join medium to read all of my articles or subscribe for e-mail updates. ## KotlinConf'23 DevFeed: [KotlinConf'23]() Original publisher: [Read original article]() Author: Matthew Dolan Published: 2023-04-14T06:29:10Z Content type: article Language: en Sources: [Stories by Matthew Dolan on Medium]() Topics: [Kotlin](), [Kotlin Multiplatform](), [Functional programming](), [Jetpack Compose](), [Swift]() Tags: [android](), [android-app-development](), [functional-programming](), [jetpack](), [kotlin](), [kotlin-multiplatform](), [kotlinconf](), [swift]() ### AI overview Personal notes from KotlinConf'23 in Amsterdam covering talks on Kotlin, functional programming, Kotlin Multiplatform, compiler plugins, Android Jetpack, and a Swift-friendly API generator called SKIE. ### Source excerpt I recently attended KotlinConf'23 Amsterdam; these are some of my thoughts on talks I enjoyed. Kotlin & Functional Programming: pick the best, skip the rest by Urs Peter. Dissecting Kotlin: Unsealing the Sealed, the SAM, and Other Syntax by Huyen Tue Dao Meta-programming with KSP and Kotlin compiler plugins by Tadeáš Kříž Why code autocompletion works faster on weekends by Egor Tolstoy Kotlin Multiplatform 5 years of Multiplatform Settings by Russell Wolf Kotlin Multiplatform Conversions at Android Jetpack Scale by Dustin Lam and James Ward One of the most promising demos I saw was SKIE. The premise of SKIE is a Swift-friendly API Generator for Kotlin Multiplatform. You may already be familiar with MOKO KSwift but SKIE looks incredibly more powerful. NOTE: I will be adding to this as I continue to write up my notes. Join medium to read all of my articles or subscribe for e-mail updates. ## The Power of Types for Errors DevFeed: [The Power of Types for Errors]() Original publisher: [Read original article]() Published: 2020-01-20T00:00:00Z Content type: article Language: en Sources: [SoundCloud Backstage Blog]() Topics: [Code](), [Android](), [App](), [User experience (UX)]() Tags: [android](), [app](), [bugs](), [code](), [compiler](), [engineering](), [kotlin](), [kotlinconf](), [types](), [ux]() ### AI overview The article explains how using custom types, sealed classes, and type hierarchies can model application error states more precisely than independent parameters or enums. This approach makes relationships explicit, improves readability, prevents invalid arguments, and helps the compiler reduce bugs in an Android app's signup tracking flow. ### Source excerpt At KotlinConf 2019, I talked about the power of types. In essence, I discussed limiting the number of primitives we use in our code in favor... ## Live coding a browser in Kotlin DevFeed: [Live coding a browser in Kotlin]() Original publisher: [Read original article]() Published: 2019-12-17T17:25:49Z Content type: tutorial Language: en Sources: [Colin The Shots]() Topics: [browser](), [Kotlin](), [Android](), [Mozilla](), [Open Source](), [coding]() Tags: [android](), [browser](), [coding](), [kotlin](), [kotlinconf](), [learn](), [live](), [mozilla](), [open-source](), [uncategorized]() ### AI overview A video demonstrates live coding an Android web browser in Kotlin using Mozilla's open source Android Components and GeckoView engine. ### Source excerpt I recently live coded an Android web browser on stage at KotlinConf 2019 in Copenhagen. You can check it out and learn all about how to use Mozilla's open source Android Components and our GeckoView ## Touchlab KotlinConf 2019 Recap - Touchlab DevFeed: [Touchlab KotlinConf 2019 Recap - Touchlab]() Original publisher: [Read original article]() Published: 2019-12-10T20:50:19Z Content type: article Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Kotlin Multiplatform](), [Kotlin](), [jetbrains](), [sessions](), [Mobile](), [Android Studio]() Tags: [android](), [android-studio](), [code-sharing](), [community](), [jetbrains](), [kmp](), [kotlin](), [kotlin-multiplatform](), [kotlinconf](), [mobile](), [recap](), [sessions](), [thoughts]() ### AI overview This recap of KotlinConf 2019 in Copenhagen reviews Kotlin Multiplatform sessions, conference announcements, and reactions from Touchlab contributors. It highlights JetBrains' recognition of Touchlab and discusses adoption, tooling, stability, performance, and project setup. ### Source excerpt The Touchlab KotlinConf 2019 recap summarizes Kotlin Multiplatform sessions from Copenhagen. Touchlab was recognized by JetBrains for its KMP expertise. ## Kotlin Multiplatform Sessions Touchlab is Attending at KotlinConf 2019 - Touchlab DevFeed: [Kotlin Multiplatform Sessions Touchlab is Attending at KotlinConf 2019 - Touchlab]() Original publisher: [Read original article]() Published: 2019-12-03T15:59:32Z Content type: article Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Kotlin Multiplatform](), [Kotlin](), [multiplatform](), [Coroutines](), [Mobile](), [Raspberry Pi]() Tags: [code-sharing](), [conference](), [coroutines](), [event](), [iot](), [kmp](), [kotlin](), [kotlin-multiplatform](), [kotlinconf](), [libraries](), [mobile](), [multiplatform](), [native](), [platform](), [press](), [raspberry](), [raspberry-pi](), [sessions](), [thoughts]() ### AI overview Touchlab lists the KotlinConf 2019 sessions it plans to attend, focusing on Kotlin Multiplatform topics for Android, iOS, JavaScript, backend systems, coroutines, Kotlin/Native, Raspberry Pi, and production projects. ### Source excerpt Touchlab will be attending KotlinConf 2019. We anticipate the conference to be a milestone event for Kotlin Multiplatform. A list of sessions we're attending. ## KotlinConf '18 DevFeed: [KotlinConf '18]() Original publisher: [Read original article]() Author: Márton Braun Published: 2018-10-06T21:00:00Z Content type: opinion Language: en Sources: [zsmb.co]() Topics: [Kotlin]() Tags: [android](), [blog](), [community](), [conference](), [design](), [kotlin](), [kotlinconf](), [marton-braun](), [thoughts](), [zsmb](), [zsmb-co](), [zsmb13](), [zsmbco]() ### AI overview A personal account of attending KotlinConf 2018, covering the venue, inclusive facilities, conference design, and community atmosphere. ### Source excerpt Funnily enough, after the previous conference report on this blog, I've got yet another one. I got to visit KotlinConf this year, these are my initial thoughts about it. Spoiler: it was awesome! ## Kotlinconf 2018 slides DevFeed: [Kotlinconf 2018 slides]() Original publisher: [Read original article]() Author: info@jeroenmols.com (Jeroen Mols) Published: 2018-10-05T00:00:00Z Content type: article Language: en Sources: [Jeroen Mols]() Topics: [Kotlin](), [multiplatform](), [coding](), [Development]() Tags: [android](), [blogs](), [conference](), [coroutines](), [functional-programming](), [gradle](), [intellij](), [kotlin](), [kotlin-compiler](), [kotlinconf](), [microservices](), [multiplatform](), [spring-boot]() ### AI overview A roundup of KotlinConf 2018 conference recordings and slides, covering Kotlin development across Android, multiplatform, servers, DSLs, compilers, coroutines, graphics, data science, and related areas. ### Source excerpt Was really great visiting Kotlinconf this year and I wanted to do a quick post to link to all of it's wonderful content. Conference slides # While you will be able to find all recordings here, I often find it useful to be able to quickly scan through the slides. ## Get ready for Kotlin DSL 1.0 DevFeed: [Get ready for Kotlin DSL 1.0]() Original publisher: [Read original article]() Author: Eric Wendelin Published: 2018-08-26T04:00:00Z Content type: release Language: en Sources: [The Gradle Blog]() Topics: [Gradle](), [Kotlin](), [Groovy](), [Documentation](), [ide](), [GitHub]() Tags: [documentation](), [github](), [gradle](), [groovy](), [ide](), [issue-tracker](), [kotlin](), [kotlinconf](), [migration](), [migration-guide](), [release](), [slack]() ### AI overview This release announcement presents the Gradle Kotlin DSL 1.0 release candidate, available in Gradle 4.10. It describes benefits such as type-aware refactoring, content assistance, debuggable build scripts, and documentation access; announces the planned final release with Gradle 5.0; and provides migration resources, samples, and feedback channels. ### Source excerpt Gradle Kotlin DSL 1.0 release candidate is generally available, included in Gradle 4.10. The Kotlin DSL is nearly ready for widespread use. We want you to enjoy a build authoring experience with the benefits provided by Kotlin's static type system: context-aware refactoring, smart content assist, debuggable build scripts, and quick access to documentation. In case you haven't seen it, you can watch Rodrigo B. de Oliveira demonstrate these benefits in this KotlinConf 2017 video. Kotlin DSL 1.0 final will be released with Gradle 5.0, which is the next version of Gradle. After version 1.0, the Kotlin DSL will not introduce any more breaking changes without a deprecation cycle. Please try the Kotlin DSL and submit feedback. Guidance for doing that follows. Trying the Kotlin DSL today The Migrating build logic from Groovy to Kotlin guide is the best place to start: it will cover all the basics and answer most of your questions. You should also consider these resources for use cases not covered by the migration guide: Dozens of Kotlin DSL samples are available through GitHub Some of the guides and nightly Gradle docs have Kotlin DSL samples. (Interested in contributing? Follow these instructions). Feedback wanted Your feedback is crucial for this project to reach this milestone. We want to know your experiences, good and bad, authoring the Kotlin DSL, understanding the logging, with your IDE, and everywhere in between. Please discuss through Kotlin DSL issue tracker or through the #kotlin-dsl channel on Gradle Community Slack (which you can join using this link). We would not be where we are today without you. Special thanks to Jonathan Leitschuh, Jean-Baptiste Nizet, Ilya Chernikov, Stefan M., Mike Kobit, the awesome Kotlin team, and dozens of others who've helped along the way. Onward to Gradle Kotlin DSL 1.0! ## Join Gradle at KotlinConf 2017 DevFeed: [Join Gradle at KotlinConf 2017]() Original publisher: [Read original article]() Author: Eric Wendelin Published: 2017-10-10T04:00:00Z Content type: article Language: en Sources: [The Gradle Blog]() Topics: [Gradle](), [Kotlin](), [GitHub]() Tags: [2017](), [3](), [conference](), [github](), [gradle](), [guide](), [kotlin](), [kotlinconf]() ### AI overview Gradle invites the Kotlin community to suggest topics for new Kotlin-with-Gradle guides for a chance to win one of two standard tickets to KotlinConf 2017. The post also highlights Gradle's conference participation and ways to contribute to the Gradle guides repository. ### Source excerpt Kotlin is the #1 rising Gradle "related topic" according to Google Trends. We want to improve user experience developing Kotlin applications with Gradle, and that requires great guides -- but we need your help! Tell us which unwritten Kotlin Gradle guide you think would be most useful, and you'll have a chance to get a free ticket to KotlinConf! See instructions below. We are proud to be a silver partner for KotlinConf, which is just 3 weeks away! Hans Dockter will be presenting Building Kotlin Applications at Scale and some of the Gradle Kotlin DSL team will be on-site to talk Kotlin with you. About the KotlinConf 2017 ticket raffle We are giving away 2 standard tickets to the conference. You'll be responsible for getting to the conference, so please don't accept a ticket if you cannot attend. All you need to do is file an issue on the gradle/guides GitHub repo with a unique and useful suggestion for a Gradle guide around building Kotlin with Gradle. For inspiration, you can check out the proposal for the Building Kotlin JVM Libraries guide, which was published recently. We'd be happy to get lots of good ideas from you, but we'll enter your name once. Winners will be chosen at random on Monday, October 16th. We'll contact you if you've been selected, and you'll have 3 days to confirm you can attend. UPDATE: Thank you everyone! The contest is now closed. If you're interested in contributing to the Kotlin/Gradle community, just adding 👍 s on ideas you think would be good is helpful, but even more so submitting a PR with a sample or typo fix is most welcome. Remember the goal: make Kotlin development awesome for everyone! Good luck! We hope to see you at KotlinConf!