understanding-hot-reload-limits

Explain Compose HotSwan hot-reload boundaries and rebuild-forcing changes.

472|16|Updated Apr 29, 2026

Search Tags:#workflow #kotlin #compose #hot-reload #hot-swan #android-performance

Ready to run

npx skills add https://github.com/skydoves/compose-performance-skills --skill understanding-hot-reload-limits

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: understanding-hot-reload-limits
Source: https://github.com/skydoves/compose-performance-skills/tree/main/hot-reload/understanding-hot-reload-limits
Command: npx skills add https://github.com/skydoves/compose-performance-skills --skill understanding-hot-reload-limits

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It educates developers on the rules that govern hot-reload in Compose HotSwan and when ART schema immutability forces a rebuild, preventing silent failures and wasted iterations.

Core Features & Use Cases

Boundary tables distinguish hot-reloadable changes from rebuild-forcing changes.
Practical workflow to diagnose and batch risky changes during iterative refactors.
Real-world scenarios and patterns (inline functions, new resource IDs, data-class properties) to guide change strategy.

Quick Start

Explain HotSwan hot-reload boundaries for my Kotlin/Compose refactor and show when a rebuild is expected.

Frequently Asked Questions about understanding-hot-reload-limits

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What changes force a full rebuild instead of a hot-reload in Compose?▼

Hot-reload boundaries in Compose HotSwan distinguish body-only composable edits from schema changes. Altering function signatures, adding new resource IDs, or changing data-class properties forces a full rebuild due to ART schema immutability.

How do I diagnose unnecessary rebuilds during Kotlin or Compose refactoring?▼

Diagnose unnecessary rebuilds during Kotlin refactoring by applying a diff-then-batch workflow. Use boundary tables to separate hot-reloadable composable body edits from rebuild-forcing schema changes, batching risky modifications to avoid silent failures.

Can I hot-reload inline functions and new resource IDs in Kotlin Compose?▼

You cannot hot-reload new resource IDs or inline function signature changes in Kotlin Compose. These modifications alter the ART schema, requiring a complete rebuild rather than applying a hot-reload update.

Why does my hot-reload silently fail when modifying data-class properties?▼

Modifying data-class properties causes hot-reload to fail silently because these changes violate ART schema immutability. Compose HotSwan cannot dynamically patch structural modifications, which forces an expected full project rebuild.

Does Compose HotSwan support hot-reload for Android performance tuning tasks?▼

Compose HotSwan supports hot-reload for Android performance tuning by enabling rapid iteration on composable bodies. It distinguishes safe body edits from schema changes to prevent wasted rebuilds during optimization tasks.