Hey Kotlin folks! :wave: I just released Konture,...

# android-architecture

[Bao Le]

Hey Kotlin folks! 👋

I just released Konture, a Kotlin architecture testing library/plugin for Android, KMP, and JVM backend projects.

It lets you write architecture guardrails directly in your test suite, using a fluent DSL to catch things like forbidden module dependencies, layer leaks, package boundary violations, and naming/interface convention issues.

GitHub: github.com/baole/konture
Article: medium.com/@leducbao/kotlin-architecture-tests-what-they-are-and-why-they-matter…

Would love feedback from the Kotlin community, especially around real-world architecture rules you’d want to enforce in multi-module projects.

[tevjef]

How does this compare to konsist?

[Bao Le Duc]

@tevjef yep, Konsist is probably the closest neighbor, but Konture’s main difference is the Gradle/Maven plugin. Konture captures the real project model Gradle builds: actual modules, source sets, production source dirs, and declared project dependencies.
That matters for Android, KMP, and backend projects because architectural boundaries often live in the build graph, not only in package names or folder conventions. Konsist is great for Kotlin source-structure checks; Konture is aimed at guardrails that need the real module graph plus Kotlin source analysis in one test surface.

[tevjef]

Awesome work!

[aherbel]

hi, does your tool use Konsist for doing the checks internally? Because Konsist is no longer maintained

[Bao Le]

No, Konture is developed from ground up