understanding-hot-reload-limits

Changes to fields, constructors, interfaces, and inline functions in Jetpack Compose cause a full rebuild instead of a hot reload due to Android Runtime class schema limitations. Method body modifications and new resource IDs generally support hot reload.

To optimize your workflow within Compose hot reload limits, structure iterative development steps to prioritize method body changes over structural modifications. This approach keeps the majority of coding iterations within the hot reload threshold, avoiding full rebuilds.

Adding a new constructor parameter triggers a full app rebuild because it alters the class schema, which Android Runtime cannot hot reload. Hot reload in Jetpack Compose is primarily constrained to method body changes without altering the underlying class structure.

Android Runtime limitations restrict Kotlin hot reload to method body modifications and new resource IDs. Structural code changes involving fields, constructors, interfaces, and inline functions exceed these limits, forcing the system to fall back to a full rebuild.

No, you cannot hot reload changes to inline functions in Jetpack Compose. Modifying inline functions alters the class schema and requires a full rebuild, as Android Runtime hot reload support is limited to method bodies and new resource IDs.