Our latest update introduces a handful of simple but impactful improvements across the platform — from config checks in the Koin IDE Plugin to more intelligent issue prioritization in the Console.
Here’s a quick breakdown of what’s new.
If you’re using the plugin day to day, this release brings some refinements that make working with larger or more modular Koin projects feel a bit more solid.
Qualified Koin declarations are now supported
Static analysis now picks up named bindings and qualifiers — helpful if you're working across modules or using more structured DI patterns.
More accurate config checks
Based on community feedback, we’ve resolved a number of false positives and added better support for binding declarations. These changes make the plugin’s warnings feel more reliable.
If you haven’t connected your project to the Kotzilla Platform yet, the new SDK Wizard can now handle the setup for Android projects. You’ll find it in the SDK tab of the plugin’s Koin Insights view.
The wizard takes care of:
Adding the Kotzilla Gradle plugin
Updating your app-level build.gradle
Generating your kotzilla.json with the correct API key
Inserting the analytics() call in your Application class to start the SDK
Just drop in your app name and package ID, sync, and run — session capture starts automatically.
📌 Manual setup guides are still available for KMP and library projects in the same tab.
This update brings some long-requested improvements to help you sort through issues faster and make more informed decisions.
New issue categories
Issues are now grouped by type:
Crashes (unhandled exceptions)
Performance (slow startups, blocked threads, resolution delays)
Architecture (dependency graph complexity)
Severity levels
Each issue is now tagged Critical, High, Medium, or Low, using an Apdex-style system that scores how far it deviates from expected performance. It’s a simple way to surface high-impact problems first.
Version comparison
You can now compare two app versions to assess regressions or improvements. This includes:
Total sessions
Number of issues
Affected devices
Average session duration
Just select the builds — the Console handles the rest.
Two updated views make it easier to investigate recurring problems:
All Issues View — now includes severity visualization alongside issue type. Issues can be filtered by severity and type. You can also filter by date, app version, impacted class, and even use full-text search.
Issues by Class View — a new perspective that groups issues by impacted class (like a specific ViewModel, repository, or background worker).
This helps surface which parts of your app are repeatedly involved in issues — and might need a closer look.
Issue Detail View: now shows key info up front, including resolution times for performance issues.
Timeline View: includes a side drawer that summarizes session issues at a glance.
Saved filters: your filters now persist across views, so you don’t lose your context while navigating.
Using Gradle Version Catalog?
We’ve published a a setup guide specifically for that workflow — one of the most requested pieces of documentation. Thanks to everyone who asked for it!
The feedback and ideas you sent us shaped most of these updates. Thanks for that, and please keep it coming.
You can find full details in the docs, or reach out in our Slack community if you want to chat directly.