Kotzilla Platform Update – Improving How Android Devs Investigate Performance Issues

This Kotzilla Platform update improves how you investigate Android performance issues by making existing data easier to interpret and navigate.

It includes updates to the Kotzilla Console (3.17.0), fixes and improvements in the Kotzilla SDK (1.4.2), and the introduction of the Kotzilla Sandbox, which lets you explore real performance data before configuring the SDK.

With this release, we’ve focused on adding clearer time-based context, simplifying access to relevant sessions, reducing visual noise in the timeline view, and improving data correctness for Compose applications.

Kotzilla Console 3.17.0

Issue duration: minimum and maximum execution time

Issues displayed in the Kotzilla Dashboard and Issues views now include minimum and maximum execution duration values, expressed in milliseconds. These values are shown alongside the number of impacted user sessions and apply to both critical and non-critical issues.

This additional time-based context helps you better understand the nature of an issue.

A high maximum duration may indicate freezes or ANR-like behavior, even when the issue affects a relatively small number of sessions. By exposing duration directly in issue lists, this update supports more informed prioritization during performance investigations.

Direct access to the last impacted session

The Console now provides direct access to the most recent session impacted by an issue. From both the Dashboard and Issues views, you can open the timeline of the last impacted session without navigating through the Issue Details view or manually filtering sessions.

This change reflects common debugging workflows, where the most recent occurrence of a problem is often a good starting point for analysis.

Reducing the number of steps required to reach session context helps shorten the time between issue detection and investigation.

Timeline view redesign

We've redesigned the Timeline view to reduce visual density and improve focus during analysis.

As applications grow in complexity, timelines can accumulate a lot of data, making it harder to identify what's relevant. We've decided to emphasize clearer structure and navigation but still preserving access to the detailed execution data you need.

Explicit event categories in the timeline slider

We’ve updated the timeline slider to clearly differentiate between performance issues and crashes, and screen-related events such as Activities and Compose navigation.

These categories are interactive, letting you navigate directly to specific moments within a session timeline.

This separation reflects how you'd typically reason about performance problems: the UI structure provides contextual framing, and performance events highlight execution bottlenecks or failures.

Memory and threading views with reduced noise

We’ve also updated the Components Memory Usage and Events Per Thread views to highlight selected event types, such as dependency-resolution and manual-tracing events.

Components Memory Usage

Events Per Thread

We've grouped less relevant activities under a neutral category to reduce visual clutter.

We hope that by reducing background noise, these views make it easier to follow execution paths, identify thread contention, and correlate memory behavior with specific events during a session.

Interactions between these views and other timeline components remain synchronized during navigation to preserve context.

The Kotzilla Sandbox is Here

We’ve introduced a Sandbox environment that allows you to explore the Kotzilla Console using pre-collected data, without integrating the SDK.

It's based on a sample Android application that includes multiple versions, demonstrating how crashes and performance issues are introduced and resolved over time.

Sessions are captured from both phones and tablets, illustrating how runtime behavior can vary across device categories. The dataset is derived from materials used in recent DroidCon workshops and provides realistic investigation scenarios.

Check it out and tell us what you think.

Kotzilla SDK 1.4.2

We’ve also released Kotzilla SDK version 1.4.2 with several fixes and improvements focused on Compose-based projects.

Generated resources are now resolved correctly when multiple resource folders are present in CMP applications. We’ve fixed a race condition that could previously cause duplicate event batches to be sent to the platform.

We’ve also addressed cases where stale application version values could be reported in Compose applications. App version metadata is now resolved and automatically applied to Compose-based projects, improving reporting consistency while reducing the need for manual configuration.

Thank you to everyone using the Kotzilla Platform and sharing feedback along the way. It helps us keep improving the tool.

If you have thoughts on this update, we’d love to hear them.

And last but definitely not least, we wish you a great start to the new year and a smooth 2026.