Gradle Plugins · Maven Central

Plugables

Opinionated code-generation plugins for Android & Kotlin projects. Eliminate boilerplate, generate from source or schema, and ship faster.

Group: com.rohittp.plugables 2 plugins JVM 21

Getting Started

Apply a plugin

All plugins are published to Maven Central. Add Maven Central to your plugin repositories in settings.gradle.kts, then apply the plugin in your module:

settings.gradle.kts

pluginManagement {
    repositories {
        mavenCentral()
        gradlePluginPortal()
    }
}

build.gradle.kts

plugins {
    id("com.rohittp.plugables.viewmodel-stub") version "1.0.0"
    // or
    id("com.rohittp.plugables.typed-events") version "1.0.0"
}

No authentication required

Maven Central is a public repository — no credentials or account needed to consume these plugins.

Available Plugins

Choose a plugin

Each plugin is fully self-contained with its own versioning and DSL block.

viewmodel-stub ↗

Scans your Kotlin source for classes annotated with @ViewModelStub and generates a matching interface and a no-op stub implementation — ready for use in unit tests and Compose previews.

v1.0.0 Android Kotlin

typed-events ↗

Reads an analytics event schema from a YAML file and generates typed top-level Kotlin functions, one per event. Register a single handler at startup to connect any analytics backend — no inheritance required.

v1.0.0 Android Kotlin

Design Philosophy

Conventions over configuration

Plugables plugins are opinionated by design. Each plugin does one thing, has sensible defaults, and requires minimal configuration. The generated code is plain, readable Kotlin — no runtime dependencies, no reflection, no surprises.

Source-driven

Generate from what you already write — annotations or YAML schemas.

Zero runtime

Generated files are just Kotlin. No runtime library to add.

Config-cache safe

All tasks use Provider APIs throughout for Gradle compatibility.

AGP integrated

Output is automatically wired into the Android main source set.