Enough with scripts, let's create an Android Studio plugin?
summary
A concrete workflow for replacing fragile external scripts with an Android Studio plugin that edits source files to insert view binding code. It uses the IntelliJ/Android Studio Platform and PSI to parse Kotlin and find setContentView calls, generates binding classes, programmatically edits documents, builds and signs a Gradle plugin, publishes it to the JetBrains Marketplace, runs the plugin in a test IDE, and performs project-wide migration of hundreds to thousands of screens to save days of manual work.
AI-written summary · about
chapters (10)
- 0:00Android Studio plugins
- 1:52Plugin vs script
- 5:00Dev environment setup
- 6:44Register plugin action
- 10:17ViewBinding plugin
- 16:19Java file manipulation
- 17:24Other plugin types
- 17:45Deploying plugin
- 20:57Plugins vs scripts
- 21:19Q&A
related talks
33mMake your Android Studio Plugin
42mWrite your own Android Studio Plugin and automate everything
28mFrom Idea to IDE: Developing Plugins for Android Studio
31mBuilding an IDE plugin for clean code generation
21mSupercharge Android Studio: Developing Your First Plugin
01h 13mService Plugin
43mPlug and Play: Power Up DevX with Android Studio Plugins
39mFantastic Plugins and Where to Find Them