Upgrade Android Studio experience by building your own plugins
summary
Build plugins with the Gradle plugin (recommended), the older DevKit, or a GitHub template; register UI and actions in plugin.xml manifest; match the IntelliJ base version to the Android Studio build and set the runIde task to point to Android Studio or the plugin won’t load. Use actions, extensions, listeners (about 200 base listeners), editors, persistence state component and Password Safe for secrets. Distribute by handing jars or using the publishPlugin gradle task (initial review ~2 days). Small teams (2–5) avoid heavy plugin work; 10–30 maintain a few; 100+ build internal frameworks.
AI-written summary · about
chapters (15)
- 0:00Introduction to plugins
- 1:12What plugins can do
- 2:38Options for plugin development
- 3:20Plugin project setup
- 4:25Plugin project structure
- 5:10Building Android Studio plugins
- 7:17Creating actions in plugins
- 9:23Running and testing plugins
- 10:27Using extensions for UI
- 11:53Building dialogs in plugins
- 13:18Using listeners for monitoring
- 14:46Working with editors
- 15:29Storing plugin settings
- 16:13Distributing plugins
- 16:56Strategizing pluginization
related talks
21mSupercharge Android Studio: Developing Your First Plugin
42mWrite your own Android Studio Plugin and automate everything
28mFrom Idea to IDE: Developing Plugins for Android Studio
39mFantastic Plugins and Where They Live
40mMake The Android Gradle Plugin Work For You- 39mFantastic Plugins and Where to Find Them
01h 13mService Plugin
38mLevel up your Android build