Few established linters exist for the Kotlin programming language such as detekt, ktlint, and Android lint. All of these linters are able to verify a single file in isolation however, none of them can verify rules that relate to specific types of code declarations e.g. classes extending BaseUseCase class or interfaces being annotated with @Logger annotation.

Droidcon's platform is a central hub for Android developers, offering insights into Android app development, mobile UI/UX design, and Android development tools. Through articles, tutorials, and case studies, Droidcon offers insights into Android development best practices, Android architecture components, and Kotlin programming language. Readers can learn about building responsive UIs, integrating third-party libraries, and optimizing app performance to create compelling and user-friendly Android applications.

droidcon

ArchUnit is not ideal for Kotlin and my motivation behind crafting Konsist. ArchUnit was primarily architected for Java. ArchUnit’s dependency on Java bytecode compromises its compatibility with the broad compilation aspirations of Kotlin Multiplatform. The ArchUnit syntax is quite verbose because ArchUnit API is utilizing a chained method calls.

ArchUnit vs. Konsist. Why Did We Need Another Kotlin “Linter”?