# jetbrains-toolbox Published articles for jetbrains-toolbox. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Toolbox App 3.8: Improves IDE Update Handling on macOS and Fixes Keyboard Navigation DevFeed: [Toolbox App 3.8: Improves IDE Update Handling on macOS and Fixes Keyboard Navigation]() Original publisher: [Read original article]() Author: Ivan Kuzmin Published: 2026-09-14T16:05:56Z Content type: release Language: en Sources: [The JetBrains Blog]() Topics: [App](), [ide](), [macOS]() Tags: [cleanup](), [ide](), [jetbrains-toolbox](), [macos](), [navigation](), [shortcuts](), [toolbox-app](), [update]() ### AI overview Toolbox App 3.8 improves IDE update handling on macOS, restores keyboard navigation in project and tool lists, and adds progress reporting and safeguards for cleanup of leftover IDE directories. ### Source excerpt Version 3.8 of the Toolbox App restores keyboard navigation in project and tool lists. On macOS, manual IDE updates stay available even when the system reports the installation directory as protected. IDE updates remain available on macOS macOS was sometimes incorrectly reporting an IDE installation directory as non-writable, causing the Toolbox App to needlessly disable [...] ## iOS development with JetBrains Fleet DevFeed: [iOS development with JetBrains Fleet]() Original publisher: [Read original article]() Author: Romain Boisselle Published: 2023-11-26T19:17:05Z Content type: tutorial Language: en Sources: [Kodein Koders - Medium]() Topics: [jetbrains](), [ide](), [SwiftUI](), [iOS development](), [User interface design]() Tags: [appcode](), [how-to](), [ide](), [ios](), [ios-app-development](), [ios-development](), [jetbrains](), [jetbrains-toolbox](), [swift](), [swiftui](), [xcode]() ### AI overview A tutorial on using JetBrains Fleet for iOS development with SwiftUI. It explains how Fleet supports code navigation, refactoring, collaboration, and running iOS applications, while noting that Xcode remains necessary for tasks such as project configuration, signing, and dependency management. ### Source excerpt Farewell, AppCode; we've found a worthy replacement. This article is intended to demonstrate how to use JetBrains Fleet for the development of Swift/UI applications, including SwiftUI previews. For those who may not know about JetBrains, it is an amazing company that builds tools for developers, such as IntelliJ IDEA or Kotlin. To me, JetBrains has always provided tools that exceeded my developer expectations, even when those tools are considered "not stable." A year ago, JetBrains announced Fleet, a brand new distributed and polyglot IDE. While many people saw it as just another VSCode IDE, I knew it would become more than that. Bringing collaborative work for remote developers and providing multiple language support out-of-the-box is a real game-changer. And if you've already tried a JetBrains IDE, you know that they are serious about developer productivity! In the meantime, a year ago, they discontinued AppCode, an underrated IDE for working within the Apple ecosystem. AppCode was particularly helpful for developers who found it challenging to adjust to alternative IDE workflows, such as XCode. With Fleet, you will experience easy code navigation, refactoring, collaboration, and support for a wide range of languages and project types, including SwiftUI applications. Let's be honest, you won't completely escape from Xcode -- there are still essential tasks like project configuration, signing, and package dependency management that require its user interface. However, for the majority of your coding sessions, you'll find that you won't need it anymore. Edit and run your iOS app from Fleet Let's start by installing Fleet using the JetBrains Toolbox. This is the easiest way to manage and upgrade your JetBrains IDEs in one place. JetBrains Toolbox -- IDE version management Once Fleet installed, you can either use your own SwiftUI project or clone the following GitHub project created for this article's purpose. https://github.com/KodeinKoders/playground-fleet-swiftui Jet ## Scripting file templates for Android Studio DevFeed: [Scripting file templates for Android Studio]() Original publisher: [Read original article]() Published: 2020-03-10T09:31:04Z Content type: tutorial Language: en Sources: [Posts on Adam Bennett]() Topics: [Android Studio](), [Boilerplate](), [Scripting, bash](), [Bash](), [jetbrains-toolbox](), [GitHub]() Tags: [algorithms](), [android](), [android-studio](), [architecture](), [automated](), [bash](), [blog](), [career](), [compose](), [developers](), [development](), [engineering](), [files](), [finance](), [formatting](), [functional](), [github](), [growth](), [install](), [java](), [jetbrains-toolbox](), [jetpack](), [kotlin](), [money](), [onboarding](), [opinions](), [productivity](), [script](), [scripting](), [software](), [startups](), [team](), [thoughts](), [training](), [tutorial]() ### AI overview This tutorial explains how Cuvva automated installing Android Studio file templates for team members across standard and JetBrains Toolbox installations. It also describes combining the setup with scripts that configure ktlint formatting, code style, and pre-commit hooks to streamline developer onboarding. ### Source excerpt As we've started locking down our architecture at Cuvva we reached a point where every new feature required very similar boilerplate, and building all of this by hand was getting tedious. The obvious solution here was to create file templates using Android Studio. I won't go into much detail as to how these are made (there's some good resources available for this already), but I wanted to quickly share how we automated setting these up for team members.