# jetbrains Published articles for jetbrains. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Building a RAG Pipeline for Semantic Code Search: A Developer Diary and Field Notes DevFeed: [Building a RAG Pipeline for Semantic Code Search: A Developer Diary and Field Notes]() Original publisher: [Read original article]() Author: Adam Malek Published: 2026-09-17T12:39:40Z Content type: article Language: en Sources: [The JetBrains Blog]() Topics: [Retrieval Augmented Generation (RAG)](), [code search](), [Parsing](), [jetbrains](), [Large Language Model]() Tags: [agentic-ai](), [ai](), [code-search](), [jetbrains](), [llm](), [llm-agents](), [parsing](), [rag](), [search](), [semantic]() ### AI overview Part 1 of a developer diary explains how JetBrains built a RAG pipeline for semantic code search, covering parsing, chunking, and vectorization. The pipeline is intended to give LLM agents precise, citable evidence from real repositories and retrieve code by meaning rather than exact keywords. ### Source excerpt Part 1: Parsing, chunking, and vectorization Some time ago, we set out to build the best semantic code search platform we could: a RAG pipeline that gives LLM agents precise, citable evidence from real repositories instead of whatever grep happens to surface. The eventual solution was JetBrains Context. We got it working, we got it [...] ## Rider and ReSharper 2026.2.2 Are Out! DevFeed: [Rider and ReSharper 2026.2.2 Are Out!]() Original publisher: [Read original article]() Author: Alexander Kurakin Published: 2026-09-16T14:12:44Z Content type: release Language: en Sources: [The JetBrains Blog]() Topics: [rider](), [resharper](), [AI-assisted coding](), [test-coverage]() Tags: [2026](), [ai-agent-hooks](), [ai-agents](), [code-coverage](), [coverage](), [hooks](), [jetbrains](), [macos](), [mcp](), [net](), [net-tools](), [releases](), [resharper](), [rider](), [update]() ### AI overview JetBrains releases Rider, ReSharper, and .NET tools 2026.2.2, adding an AI Agent Setup widget in Rider, more targeted hook feedback for coding agents, TUnit coverage support, and fixes including a macOS freezing issue. ### Source excerpt We've released version 2026.2.2 of ReSharper, Rider, and .NET tools. You can install this update from inside the tools themselves, through the Toolbox App, or on our website. Here's what's new in this update. Rider 2026.2.2 AI Agent Setup widget We've recently added a wide range of features to help you work with coding agents [...] ## Behind the Scenes: How the OpenTelemetry Plugin Maps Your Microservices in Real-Time DevFeed: [Behind the Scenes: How the OpenTelemetry Plugin Maps Your Microservices in Real-Time]() Original publisher: [Read original article]() Author: Egor Klimov Published: 2026-09-16T12:34:47Z Content type: article Language: en Sources: [The JetBrains Blog]() Topics: [OpenTelemetry](), [Microservices](), [observability](), [telemetry](), [Traces](), [ide]() Tags: [all-things-web](), [backstage](), [environment-variables](), [goland](), [ide](), [idea](), [intellij-idea](), [intellij-platform](), [jetbrains](), [microservices](), [observability](), [opentelemetry](), [performance-optimization](), [plugin-development](), [plugin-highlights](), [plugins](), [pycharm](), [research](), [rider](), [telemetry](), [traces](), [webstorm]() ### AI overview This article explains how the JetBrains OpenTelemetry Plugin generates a service map from runtime telemetry. It describes using logs, metrics, and especially standardized trace spans to visualize how microservices communicate, along with the plugin's lightweight local OpenTelemetry backend. ### Source excerpt We've all been there: you join a new project, and the first thing you ask for is the architecture diagram. You're handed a diagram that looks great, but after a week of debugging, you realize it's six months out of date. Service A hasn't talked to Service B since the spring, and there's a new [...] ## Build Setup: Targets, Source Sets and buildSrc for tvOS in a Compose Multiplatform Fork DevFeed: [Build Setup: Targets, Source Sets and buildSrc for tvOS in a Compose Multiplatform Fork]() Original publisher: [Read original article]() Author: Sajid Ali Published: 2026-09-14T04:24:43Z Content type: tutorial Language: en Sources: [ProAndroidDev - Medium]() Topics: [compose-multiplatform](), [tvOS](), [Kotlin Multiplatform](), [Gradle]() Tags: [apple](), [build](), [compiler](), [compose-multiplatform](), [gradle](), [gradle-plugin](), [ios](), [jetbrains](), [multiplatform](), [source]() ### AI overview This tutorial explains the build setup for adding tvOS support to a Compose Multiplatform fork. It covers Kotlin Multiplatform targets, source-set organization shared between iOS and tvOS, and the build-layer work used to identify missing modules and dependencies. ### Source excerpt Compose Multiplatform on tvOS This series: Compose Multiplatform on tvOS My Journey Making Compose Multiplatform Work on tvOS, and What I Learned Build Setup: Targets, Source Sets and buildSrc for tvOS in a Compose Multiplatform Fork (this post) Rendering (coming soon) Siri Remote input (coming soon) Siri Remote trackpad (coming soon) Screen density and text input (coming soon) Porting tv-material (coming soon) The Gradle plugin and third-party libraries (coming soon) Maintaining the fork (coming soon) Building a real app on it (coming soon) Part 1 was why this fork exists. This one is the build layer, and it comes before any Compose code, because in Kotlin Multiplatform a target is not a flag you flip at the end. It decides which source sets compile, which dependencies resolve, which klibs get published, which linker flags get passed. Until the build knows about tvosArm64, nothing tells you what is missing. So the first commits were build files. Once the targets were on, the compiler listed what was missing, module by module, and I worked through that list. Source set layout on the tvos branch I started on a branch called tvos, based on upstream. Back then JetBrains called iOS "uikit" in this repository and the source set was uikitMain. Because tvOS is also UIKit underneath, it made sense to have a common source parent for both iOS and tvOS. But iOS was already being called uikit, so I chose uiKitCommonMain as the source set name and moved all the UIKit files there, keeping only the iOS specific files in uikitMain and putting the tvOS specific files in a new source set, tvosMain. The problem with this approach was how to keep up with upstream. I tried a symlink to the uikit source set, and then overriding the tvOS files in a separate target. The override worked but complicated the process. At that time my goal was to make it runnable on tvOS however possible, so we would have a proof of concept. So I did a lot of hacks in the tvos branch to make it runnable, and af ## What to expect at the Zephyr Project Meetup (September 15, 2026) - Amsterdam, Netherlands DevFeed: [What to expect at the Zephyr Project Meetup (September 15, 2026) - Amsterdam, Netherlands]() Original publisher: [Read original article]() Author: Susan Remmert Published: 2026-09-09T05:00:04Z Content type: news Language: en Sources: [Zephyr Project]() Topics: [Zephyr RTOS](), [Embedded Systems](), [Fuzzing/Fuzz testing](), [Open Source]() Tags: [2026](), [blog](), [c](), [c-plus-plus](), [crashes](), [developer-tooling](), [embedded](), [embedded-systems](), [event](), [events](), [firmware](), [fuzzing](), [harness](), [jetbrains](), [meetup](), [memory-corruption](), [open-source](), [simulator](), [zephyr]() ### AI overview The Zephyr Project Meetup in Amsterdam on September 15, 2026, will bring together embedded developers, contributors, students, and engineers to share practical knowledge about Zephyr RTOS. The agenda includes talks on JetBrains' work with Zephyr, fuzzing Zephyr with AFL and Renode, and making hardware development easier with Schematik. ### Source excerpt What are developers in the Netherlands building with Zephyr? On September 15, the embedded community will meet in Amsterdam to exchange practical knowledge, discuss current work, and learn more about the Zephyr RTOS. The event is open to experienced contributors, first-time users, students, engineers, and anyone curious about open source embedded development. ## 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. ## 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?!? ## Investigating a Suspected Memory Leak in JetBrains Jewel with JVM Heap Analysis DevFeed: [Investigating a Suspected Memory Leak in JetBrains Jewel with JVM Heap Analysis]() Original publisher: [Read original article]() Published: 2026-07-28T18:00:00Z Content type: article Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Memory Leaks](), [Compose](), [compose-multiplatform](), [jetbrains](), [ide]() Tags: [compose](), [compose-multiplatform](), [dump](), [eclipse](), [heap](), [jetbrains](), [kotlin-multiplatform](), [memory-leak]() ### AI overview The article investigates a suspected memory leak in the JetBrains Jewel project, a Compose Multiplatform library targeting desktop applications. It explains using JVM-specific tools, including heap dumps and Eclipse Memory Analyzer Tool, to examine retained heap and identify possible memory-retention issues. ### Source excerpt A kinda-brief tale about a memory leak, a heap dump, and a one-line fix. ## Adding a Koog AI assistant (with structured output) to the FantasyPremierLeague CMP sample DevFeed: [Adding a Koog AI assistant (with structured output) to the FantasyPremierLeague CMP sample]() Original publisher: [Read original article]() Published: 2026-07-27T23:00:00Z Content type: tutorial Language: en Sources: [John O'Reilly]() Topics: [Artificial Intelligence](), [compose-multiplatform](), [Kotlin](), [jetbrains](), [Framework](), [App]() Tags: [agents](), [ai](), [ai-agents](), [compose](), [compose-multiplatform](), [framework](), [jetbrains](), [kotlin](), [llm](), [multiplatform]() ### AI overview This tutorial adds a Koog-powered AI assistant to a FantasyPremierLeague Compose Multiplatform sample. It uses structured output to return typed player and fixture IDs, allowing the app to render cards and resolve references against its existing data. ### Source excerpt Koog is JetBrains' Kotlin framework for building AI agents. In this article we're going to use it to add an in-app "FPL Assistant" to the FantasyPremierLeague Compose Multiplatform sample. This is a chat screen where you can ask about players, fixtures and mini-league standings. The answers render as player and fixture cards rather than just as text. ## Moxy - My new programming font DevFeed: [Moxy - My new programming font]() Original publisher: [Read original article]() Author: Kaushik Gopal Published: 2026-06-16T07:00:00Z Content type: opinion Language: en Sources: [Kaushik Gopal's Site]() Topics: [Font](), [Programming]() Tags: [download](), [files](), [fonts](), [jetbrains](), [ligatures](), [mono](), [plex](), [programming](), [programming-font]() ### AI overview The article introduces Moxy, a programming font built on Recursive with opinionated character choices and fixes, incorporating some glyph ideas from Lilex. It explains the font's customizable character choices and provides installation instructions for the v1 release. ### Source excerpt Every time I switch or try out a new font, I track it in my my-new-programming-font series. Some of the popular ones: IBM Plex Mono, Recursive, Commit Mono, Berkeley Mono. This time's a little different. It's one I've "made" myself, and I'm calling it Moxy. Built on strong bones ## Moxy is built on top of Recursive. It's a stretch to call it a new font -- it's Recursive with a set of opinionated character choices and a few fixes to the original. There's two things I love about Recursive: it's one of the most legible and clear fonts out there it's got flair1 Recursive was also a pioneer in pushing what variable type fonts can do. Another font I've been testing and playing with is Lilex. It's popular again because editors like Zed use it as the default. Lilex is really just IBM Plex Mono with a set of special characters and ligature choices. It's an excellent font in many ways, and one I often find myself switching to. Lilex has a few ligatures I absolutely love for programming. So, with the power of AI coding, I thought to myself: what if I had Recursive but with some of the glyphs of Lilex? Thus was born Moxy. What's different: ## The font ships with my specific Recursive character choices baked in. But you can swap them in and out depending on your preference. Install it ## Download the v1 release, unzip it, and install the .ttf files like any other font. Alternatively, use brew: brew install --cask kaushikgopal/tools/font-moxy People understandably love and swear by JetBrains Mono. They keep asking why I don't cite or bring it up. I love that JetBrains Mono exists, but I find it a "drab" font -- and that's not always a bad thing. When you look at Recursive, it makes a statement. ↩︎ ## Why Decision-Makers Adopt Kotlin Multiplatform DevFeed: [Why Decision-Makers Adopt Kotlin Multiplatform]() Original publisher: [Read original article]() Published: 2026-04-29T18:00:00Z Content type: article Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Kotlin Multiplatform](), [multiplatform](), [Kotlin](), [Maintainability](), [Developer experience](), [jetbrains]() Tags: [adoption](), [business-value](), [developer](), [jetbrains](), [kmp](), [kotlin](), [kotlin-multiplatform](), [maintainability]() ### AI overview The article explains that Kotlin Multiplatform adoption depends on decision-makers seeing measurable business value, not only on developer enthusiasm. It highlights reduced duplicated work across iOS and Android, native UI and workflows, potentially less code, faster release cycles, and improved maintainability. ### Source excerpt KMP adoption is not driven by developer enthusiasm alone. It moves forward when leaders see a clear case for measurable business value. ## Building Shellporter: From Idea to Production in a Week DevFeed: [Building Shellporter: From Idea to Production in a Week]() Original publisher: [Read original article]() Author: Marco Gomiero Published: 2026-02-14T00:00:00Z Content type: article Language: en Sources: [Posts on Marco Gomiero]() Topics: [macOS](), [Terminal](), [ide]() Tags: [app](), [ide](), [jetbrains](), [macos](), [terminal]() ### AI overview The author describes building Shellporter, a macOS menu bar utility that opens a terminal in the project directory of the active IDE. It uses window information, macOS Accessibility API attributes, IDE-specific resolution strategies, metadata files, and a cache, with support for several IDEs and terminal applications. ### Source excerpt I work with multiple projects at the same time. My typical macOS setup is one Desktop/Workspace per project, with my IDE and a terminal window. I prefer using a standalone terminal over the one built into the IDE because TUIs, especially those from AI agents, tend to perform better there: no scrolling jank, no weird jumps, and a generally smoother experience. And also I prefer to have a full big window dedicated to the terminal with more stuff to read rather than a small window in the IDE. ## Rust Questions Answered in a JetBrains Livestream with Herbert Wolverson DevFeed: [Rust Questions Answered in a JetBrains Livestream with Herbert Wolverson]() Original publisher: [Read original article]() Published: 2026-01-07T00:00:00Z Content type: article Language: en Sources: [William Kennedy]() Topics: [Rust](), [Code]() Tags: [ardan-labs](), [blog](), [developers](), [go](), [go-programming](), [golang](), [jetbrains](), [livestream](), [programming](), [repo](), [rust](), [talk]() ### AI overview This article summarizes 23 questions discussed in a JetBrains livestream with Herbert Wolverson about Rust. Topics include his new book, Rust's memory model, the language's learning curve, and whether beginners should learn C first. ### Source excerpt In a recent livestream with JetBrains, Vitaly Bragilevsky sat down with Herbert Wolverson, our Lead Rust Consultant and Instructor here at Ardan Labs, to talk about everything Rust developers - beginners and pros alike - are curious about. Watch the full livestream replay on the Ardan Labs Channel and check out the GitHub repo with Herbert's prepared answers and code samples. Below is a short summary of the 23 questions that were covered during the livestream. ## Start building with Gemini 3 DevFeed: [Start building with Gemini 3]() Original publisher: [Read original article]() Author: Logan Kilpatrick Published: 2025-11-18T17:49:13Z Content type: release Language: en Sources: [Google DeepMind News]() Topics: [Google AI](), [agentic-coding](), [Development](), [Command-line interface](), [ide](), [Benchmark]() Tags: [agentic-coding](), [agentic-development](), [antigravity](), [benchmark](), [cli](), [gemini](), [google](), [google-antigravity](), [jetbrains](), [linux](), [macos](), [none](), [preview](), [windows]() ### AI overview Google introduces Gemini 3, highlighting Gemini 3 Pro's reasoning, coding, agentic workflow, and benchmark performance. The model is available in preview through the Gemini API, Google AI Studio, and Vertex AI, with integration across developer tools. ### Source excerpt Gemini 3 is introducing advanced agentic coding capabilities, plus Google Antigravity, a new agentic development platform. ## ACP Brings JetBrains on Board DevFeed: [ACP Brings JetBrains on Board]() Original publisher: [Read original article]() Author: Franciska Dethlefsen Published: 2025-10-06T00:00:00Z Content type: release Language: en Sources: [Zed Industries - Blog]() Topics: [Protocol (disambiguation)](), [ide](), [IntelliJ IDEA](), [junie](), [PyCharm](), [webstorm](), [codex]() Tags: [codex](), [gemini](), [integration](), [integrations](), [intellij](), [intellij-idea](), [jetbrains](), [junie](), [protocol](), [pycharm](), [vendor-lock-in]() ### AI overview JetBrains will co-develop the Agent Client Protocol with Zed and plans to add ACP support across its IDE ecosystem, including IntelliJ IDEA, PyCharm, and WebStorm. The article presents ACP as an open standard intended to let agents work across compatible editors. ### Source excerpt The Agent Client Protocol reaches a major milestone: JetBrains is committing to bringing ACP support to their entire ecosystem. ## Live Templates in Android Studio DevFeed: [Live Templates in Android Studio]() Original publisher: [Read original article]() Author: Segun Famisa Published: 2025-07-17T06:00:00Z Content type: tutorial Language: en Sources: [Segun Famisa]() Topics: [Android Studio](), [Kotlin](), [ide](), [IntelliJ IDEA](), [Code]() Tags: [android](), [android-studio](), [code](), [ide](), [intellij](), [jetbrains](), [keyboard](), [kotlin](), [shortcuts](), [tests](), [workflow]() ### AI overview This tutorial explains IntelliJ-based IDE live templates, with a focus on creating a custom Android Studio template for Kotlin test functions that use backticks. It describes the template settings, applicable context, abbreviation, description, and template variables. ### Source excerpt If you are already familiar with live templates, feel free to skip to the live template for kotlin tests If you use IntelliJ-based IDEs like Android Studio, WebStorm, etc., chances are that you have seen some kinds of "shortcuts" (pictured below) show up when you press some key combinations. These are called live templates. For example, if you type sout in a Java/Kotlin file, you see a pop-up like the one above. When you press tab, it autocompletes into System.out.println (in Java) or println in Kotlin. Live templates allow you to generate common code constructs by typing keywords that trigger the template. This feature is not new, and I definitely remember seeing it in the Netbeans IDE when I developed J2ME applications. If, like me, you write a lot of Android code in Android Studio, you may also know that if you type comp in a Kotlin file and press the tab key, a composable function is generated. I have personally found these templates extremely useful for developing faster, and I use them all the time. I even have a few of my own templates, and one of them is the main reason I am writing this article. -- Live Template for Kotlin tests One of the things I do almost every day when I write code is write tests. If you use Kotlin, you might know that backticks are allowed in test function names. I like to optimise my workflow, and I realised this was an opportunity to save myself a few keystrokes for every test I write. I ended up writing a live template to automatically create a test function with backticks (does anyone else find the backtick key awkwardly placed on the keyboard?). To set this up, I follow the instructions on JetBrains' website. You can do the same: CMD + , to open settings Navigate to Editor > Live Templates Select Kotlin group (the templates are usually grouped, but you can also create your own group if you so please) Click on the little + button or CMD + N , and select 1 or Live Template Now we can begin to set the details for the live template. Th ## 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. ## My experience using Junie for the past few months DevFeed: [My experience using Junie for the past few months]() Original publisher: [Read original article]() Author: Julien Published: 2025-05-11T11:38:55Z Content type: opinion Language: en Sources: [Thoughts, stories and ideas.]() Topics: [junie](), [Artificial Intelligence](), [IntelliJ IDEA](), [coding]() Tags: [agent](), [ai](), [coding](), [development](), [experience](), [intellij](), [jetbrains](), [junie](), [kotlin]() ### AI overview A personal review of using JetBrains Junie over several months. The author describes Junie's Code and Ask modes, IntelliJ-based IDE integration, terminal command option, pricing, and distinctions from other JetBrains AI products. They value its IntelliJ integration, Kotlin support, and test-first focus, but criticize its slowness and limited ability to accept only part of a proposed solution. ### Source excerpt Junie is one of the best coding agent I've been trying out so far. Very well integrated with IntelliJ, great for Kotlin, and the test first focus makes it quite good at coming out with good results. However, I do miss the capability to only accept part of a solution and it can be very slowwwwww. ## Gradle Best Practices - A Path to Build Happiness DevFeed: [Gradle Best Practices - A Path to Build Happiness]() Original publisher: [Read original article]() Author: Laura Kassovic Published: 2025-05-01T04:00:00Z Content type: article Language: en Sources: [The Gradle Blog]() Topics: [Gradle](), [Google](), [Tooling]() Tags: [best-practices](), [build-system](), [developer](), [gradle](), [jetbrains]() ### AI overview Gradle, Google, and JetBrains formed a working group to define best practices for structuring and configuring Gradle builds. The initiative responds to developer difficulties caused by Gradle's flexibility, including build instability, suboptimal solutions, and maintenance challenges. ### Source excerpt Gradle Build Tool, also known as Gradle, is a highly flexible and extensible build system. It supports multiple ways to structure and configure builds, making it incredibly powerful--but also somewhat daunting, especially for teams just getting started. Even experienced developers and tooling providers sometimes struggle with Gradle's complexity. We've heard this loud and clear from the community and also in our recent Developer Survey. Whether it's setting up a build from scratch, improving performance, or avoiding pitfalls, teams often find themselves searching for clear guidance on the best way to do things. That's why we partnered with JetBrains and Google to create the Gradle Best Practices guide--an essential resource to help teams build with confidence and settle debates over the proper way to use Gradle. How This Initiative Started This effort began during a Gradle, Google, and JetBrains Summit in Fall 2024, where teams from each company meet annually to align on product roadmaps and discuss the future of the ecosystem. These summits have been pivotal in shaping major initiatives--Declarative Gradle emerged from one of these discussions, and Kotlin itself has been deeply influenced by them. At the 2024 Summit, a key question emerged: Beyond new features, how can we improve the Gradle experience today? The answer was clear: we need to establish best practices. While it's easy to focus on exciting new Gradle features, existing build setups often lack clear guidance. The Gradle teams at Google, JetBrains, and Gradle recognized that developers frequently struggle with too many ways to do the same thing--leading to suboptimal solutions, build instability, and maintenance headaches. This realization led to the formation of a dedicated working group, with representatives from all three companies. Over the past months, we've been meeting weekly to define best practices that provide firm foundations and help teams avoid future problems. Why Best Practices Matter Gradle's ## HarmonyOS App Development 101 DevFeed: [HarmonyOS App Development 101]() Original publisher: [Read original article]() Author: Jasper Morgan Published: 2025-01-18T23:23:13Z Content type: tutorial Language: en Sources: [Snapp Mobile - Medium]() Topics: [App](), [Development](), [ide](), [huawei](), [SDK](), [Tooling](), [jetbrains](), [Package Management](), [Testing](), [Open Source]() Tags: [android](), [app](), [app-development](), [apps](), [code-completion](), [debug](), [deployment](), [development](), [harmony-os](), [huawei](), [ide](), [jetbrains](), [open-source](), [package-management](), [programming-languages](), [refactoring](), [sdk](), [testing](), [tools](), [ui](), [ui-framework]() ### AI overview An overview of HarmonyOS Next app development, covering the Huawei-based DevEco Studio IDE, project configuration, SDK versions, modules, and common development features. The article also outlines programming languages, UI frameworks, build tools, package management, execution, debugging, testing, and profiling. ### Source excerpt Huawei have taken a big step in moving away from the Android platform with the launch of new devices running HarmonyOS Next. This is a brand new operating system that had been design specifically for devices. This means it is lightweight, supports a range of device types, is modular and extensible. In this article we aim to give you an overview of what is available to developers wishing to build apps on this new platform. To that end, we will be looking at the following topics: The IDE Programming Languages UI Framework Build Tools Package Management Running code (devices/emulators) Debugging Testing Profiling Other cool stuff If you are curious about the Harmony platform, its Open Source foundations (OpenHarmony) and its global reach (Oniro), we have written about it here. The IDE The development environment for Harmony apps is currently a Huawei-based IDE which is based on the JetBrains IDE platform. The good news is that JetBrains offers a world-class IDE platform and it makes for a very solid development experience for Harmony apps. For those, wanting to keep to the Open Source side of Harmony (OpenHarmony and Oniro), you are out of luck right now. DevEco Studio is proprietary, albeit free to use software. Let's look at a couple of IDE features -- these should not surprise you but hopefully demonstrates that the platform is already in a good place (as far as IDEs go). Project Creation Creating a project will look familiar already for many. There are a few project templates to choose from to bootstrap your project. New Project Templates You will also then need to configure a couple of options -- a couple of notes on these (which could probably be expanded into a separate article). Firstly, the bundle name is used for app signing and identity. Secondly, an app supports a single SDK version. (The latest SDK version is 13, however version 11 is still widely used.) Thirdly we can specify the module name. The default ('entry') isn't very descriptive. If you have a singl ## The pursuit of fast feedback loops DevFeed: [The pursuit of fast feedback loops]() Original publisher: [Read original article]() Author: Saket Narayan Published: 2024-11-27T17:46:56Z Content type: opinion Language: en Sources: [Saket Narayan]() Topics: [Mobile](), [Compose](), [ui](), [unit tests](), [jetbrains]() Tags: [android](), [compose](), [hot-reloading](), [incremental](), [jetbrains](), [layout](), [mobile](), [screenshot](), [tests]() ### AI overview This opinion argues that fast feedback loops for validating software changes matter more than hot reloading itself. It discusses the reliability history of hot-reload tools and describes using screenshot tests and unit tests to shorten UI and presentation/backend iteration cycles. ### Source excerpt Sebastian Sellmair from JetBrains recently showed off a prototype of hot-reloading Compose UI code for deploying changes without rebuilding the project. It looks exciting and I want it to succeed. At the same time, I've learned to be cautiously optimistic about hot-reload solutions. Google has tried this multiple times: their first attempt (Instant Run) was [...] The post The pursuit of fast feedback loops appeared first on Saket Narayan. ## Flash cards for Coroutines - KotlinFlashKards DevFeed: [Flash cards for Coroutines - KotlinFlashKards]() Original publisher: [Read original article]() Published: 2024-09-18T17:50:02Z Content type: tutorial Language: en Sources: [maiatoday]() Topics: [Coroutines](), [Kotlin](), [kotlin-coroutines](), [ide](), [Deadlock](), [Error Handling](), [Testing]() Tags: [code](), [coroutines](), [error-handling](), [flash-cards](), [ide](), [jetbrains](), [kotlin](), [kotlinflashkards](), [structured-concurrency](), [testing]() ### AI overview An in-IDE flash-card course called KotlinFlashKards helps learners practise Kotlin coroutines through questions, hints, code snippets, and tests. It covers basics, structured concurrency, error handling, and testing, and runs through the JetBrains Academy plugin. ### Source excerpt I made something. I made a set of flash cards to practise and learn Kotlin coroutines. I call them KotlinFlashKards (with a K of course). This is the first of a series covering different topics. Why create flash cards? Does this happen to you? You are writing some code, you know something is possible but you can't remember exactly how to do it. By the time you have asked an AI or researched you have forgotten what it was you wanted to do in the first place. There is a way to fix this. Learn and remember the key concepts you use often. One way to do this is to use flash cards. I learnt this from the book The Programmers Brain by Felienne Hermans How does it work? The deck doesn't replace the docs or a good book. It is an in IDE course in the form of a question, a hint that hides the answer and a code snippet with a test to explain the concept. It has four sections Basics - 18 cards Structured Concurrency - 12 cards Error handling - 7 cards Testing - 6 cards You can explore the sections in order or dip in and try tasks at random. Strategies to get the best out of the course? Repeat at regular intervals - Memories are built up if you repeat the flash cards at regular intervals. It is better to do a few lessons more often than to do many lessons in one sitting. You can do the course many times or choose which areas to practise. Recall the answer before peeking - It is important to try to recall the syntax first before looking at the hints or letting the IDE help you. This means you practise your recall of the memory. Think about the solution - For each question and answer you will remember it better too if you think of a practical place where you could use similar code. How do I get it? You need: a JetBrains IDE like Android Studio or Intellij Community edition the JetBrains Acadamy plugin installed Then do the following: Before opening a project click on the Learn menu item on the left Click on New course In the Marketplace search for KotlinFlashKards and start the cou ## 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 ## Resource Sharing in Compose Multiplatform - Anonymous DevFeed: [Resource Sharing in Compose Multiplatform - Anonymous]() Original publisher: [Read original article]() Published: 2023-12-14T15:38:42Z Content type: article Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [compose-multiplatform](), [API](), [jetbrains](), [Kotlin Multiplatform](), [Tooling]() Tags: [api](), [compose](), [compose-multiplatform](), [core](), [development](), [feature](), [implement](), [jetbrains](), [multiplatform](), [platform](), [platforms](), [ui]() ### AI overview The article discusses JetBrains' 2024 Kotlin roadmap, highlighting planned Compose Multiplatform support for a common API that would allow resources to be shared across targets. The roadmap does not specify which resources will be shareable or provide an official timeline. ### Source excerpt JetBrains just shared a development roadmap for 2024 detailing their focus for 2024. One item stands out above the rest: a common API for resources. [Next page]()