StudioPlugins bundles prebuilt Android Studio plugins for one IDE version

A list of plugins with the binaries attached

StudioPlugins is not a plugin and not a framework. It is a curated collection of Android Studio plugins, and the repository description makes the selection criterion explicit: the point is not quantity but quality, not many but few.

The repository layout shows how thin it is. There is a README, a picture directory holding the screenshots, and a plugins directory holding the downloadable plugin archives. There is no source code for the plugins themselves, because the plugins are other people's projects.

Each entry in the list follows the same pattern. It names the plugin, links to its JetBrains Marketplace page, links to its upstream GitHub repository, and gives a download address that points into the plugins directory of this repository. So the collection is two things at once: a recommendation list and a mirror of prebuilt plugin archives that you can install without going through the marketplace.

The audience is Android developers working in Chinese, since the README is written in Chinese and the blog links point at a Chinese writing platform. The selected plugins cover translation, image preview, build speed, code smell detection, AI completion, adb tooling, dependency lookup, code location, Parcelable and Bean generation, and a small macOS convenience.

The licence recorded for the repository is Apache-2.0, with a LICENSE file at the root. That covers the collection itself, not necessarily the third-party plugins whose binaries it hosts, which is the distinction the last section returns to.

Everything is pinned to Android Studio Quail 3

The first note in the README is a compatibility statement, and it is the constraint that decides whether the collection is useful to you.

The README says all plugins were tested without problems on Android Studio Quail 3 | 2026.1.3, and recommends using that version. Download links are provided for the Quail 3 release for Windows, macOS on x86, macOS on arm, and Linux.

That pin explains a lot about the repository. A plugin built against one IntelliJ platform build will refuse to load in another, and the archives in the plugins directory were fetched for a specific platform version. The release history makes the pattern visible: the tags are named after the IDE release they target, with 2026.1.3.7 for Android Studio Quail 3, 2022.3.1.18 for Android Studio Giraffe, and 2021.1.1.20-2 for Android Studio Bumblebee 2.

The README also offers a workaround, and it is the most practically useful line in the document for anyone on a different build. If the plugin will not install and your Studio is not the tested version, copy the plugin name and search for it in the online plugin search inside Studio, and Studio will pick the version that matches your installation.

In other words, the collection's value is highest for people on the recommended version and degrades to a link directory for everybody else.

Installing from disk takes three clicks in Settings

The installation path is short, and the README states it in one line: download the plugin, then in Studio go to Settings, then Plugins, then Install Plugin from Disk.

* 下载好插件，选择 `Settings` -> `Plugins`  -> `Install Plugin from Disk` 进行安装

The archives are ordinary plugin packages in the plugins directory, referenced from each entry's download line, for example plugins/TranslationPlugin-3.9.1.zip and plugins/GsonFormat-1.5.0-fix.jar.

The version suffix in those filenames is worth noting, because it shows what the collection does and does not control. Some entries point at a zip pinned to an exact version, such as TranslationPlugin-3.9.1.zip or JsonToKotlinClass-3.7.7.zip, while others point at an upstream release page, such as the jugg plugin pointing at the Tencent Music releases and the CodeLocator plugin pointing at the ByteDance releases. In the first case the archive is a frozen copy; in the second the collection is only a pointer.

The screenshots in the picture directory are not decoration either. Each plugin entry is accompanied by a short description of what it does and a usage note, usually a few steps naming the menu or the right-click action, so the README doubles as the manual for the tools it collects.

What is actually in the list

The navigation section lists sixteen categories, and the entries below it explain what each tool does and which IDE version it was tested against.

For reading and writing code, the Translation plugin translates the selected word or sentence in place and can translate API documentation, with a choice of Google, Youdao or Baidu as the engine. The Android Drawable Preview plugin shows thumbnails for images and for XML resources in the drawable and mipmap folders. SonarQube for IDE warns when code does not meet the configured rules. GitHub Copilot provides completion suggestions in the editor, accepted with the TAB key after signing in with a GitHub account.

For build and device work, Jugg is the incremental build tool the collection highlights for large Android projects, described as a seconds-level incremental build approach from the Tencent Music team aimed at projects where a small edit can otherwise cost minutes of compilation. Two adb plugins sit next to it: Adb Input sends text from the IDE to a device, and ADB Idea wraps adb commands such as uninstalling an app, killing it, clearing data or revoking permissions.

For dependencies and navigation, GoogleLibraryVersionQuerier suggests dependency coordinates as you type a repository name in Gradle and can query historical versions of a dependency. CodeLocator, from ByteDance, combines an Android SDK with an IDE plugin for locating code and correcting UI on a real device.

For code generation, the Android Parcelable code generator writes the Parcelable implementation for a Bean, the README explaining that Serializable is simpler but slower while Parcelable is faster but tedious to write by hand. GsonFormat turns a JSON response into Java Bean fields, and JSON To Kotlin Class does the same for Kotlin. The last entries cover a macOS convenience, CopyToFinder, and the navigation also lists rainbow brackets, a JSON helper and a findViewById plugin.

Where a plugin collection is the wrong tool

The honest limitation is that this is a mirror of binaries, not a maintained dependency set.

Each plugin is someone else's project with its own repository, its own release cadence and its own maintainers. The entries link to those upstreams, which is the right place to report a bug. When this collection says a plugin was tested on Quail 3, that statement is true on the day it was written and decays after every IDE update, and nothing in the repository enforces or rechecks it.

The supply chain angle deserves a mention. Installing a plugin from disk bypasses the marketplace, which means you are running a binary whose provenance is a link in a README rather than a listing in the JetBrains registry. Some of the archives are named with a fix suffix, GsonFormat-1.5.0-fix.jar and AndroidParcelableCodeGenerator-0.7.0-fix.jar, which tells you these are locally patched builds rather than pristine upstream releases.

The second limitation is scope. There is no plugin manager here, no version resolution, no automated update check and no build step. The collection assumes a specific IDE version and a manual install, so it does not scale to a team that wants a reproducible plugin set across dozens of machines, where the IDE's own plugin repository or a build configuration would be the mechanism.

Third, the selection is opinionated and narrow. Sixteen categories is a small slice of what the JetBrains Marketplace offers, and the criteria for inclusion are not written down anywhere in the README. If your project needs something outside the list, the list is not an argument against installing it from the marketplace.

Apache-2.0 for the list, and separate terms for every plugin

The licence of the repository itself is Apache-2.0, which is a permissive grant and covers the README, the screenshots and the arrangement of the collection.

It does not automatically cover the plugin archives. Each plugin keeps the terms of its own project, and the README is explicit about who owns what by linking every entry to its upstream repository. For the entries where the collection ships a modified archive, the modified build is a derivative work of someone else's plugin, and the terms of that plugin apply to it. A team using these plugins in a commercial product should check the upstream licence for each plugin it actually installs.

On maintenance, the numbers are worth reading carefully. The repository is not archived and the last push was on 2026-09-09, so the collection is still being refreshed. The newest release, 2026.1.3.7 for Android Studio Quail 3, is dated 2026-09-07, two days before that push. The two releases before it, 2022.3.1.18 for Giraffe and 2021.1.1.20-2 for Bumblebee 2, are both dated 2023-08-20, which tells you the collection follows the IDE release cycle rather than a fixed schedule of its own.

So the practical expectation is a refresh shortly after each Android Studio release, with older IDE versions supported by older tags. That is a sensible cadence for a plugin list, and it is also the reason the fallback tip about searching the marketplace by plugin name matters: it is the escape hatch for anyone whose IDE release is newer than the latest tag.

Editorial conclusion

Android developers who want a known-good set of plugins for one specific Android Studio release should use this collection, because the archives are tested together against Quail 3 2026.1.3 and the README explains how to fall back to the marketplace when a version does not fit. It is the wrong tool if you want plugins you can build from source or track upstream, since the repository holds prebuilt archives and links rather than code, and it is the wrong tool if you are on a different IDE release, where the bundled builds may not load at all. Before installing, check that your Studio version matches the tested one, read the licence of each upstream plugin you actually take, and prefer the upstream project when a plugin is actively maintained.

Frequently asked questions

Official sources

1. getActivity/StudioPlugins on GitHub
2. Issues
3. License: Apache-2.0
4. README
5. Releases