unity-async

To choose the right Unity async pattern, use a decision ladder evaluating whether work needs per-frame polling, short sequential animation, or background async handling. Prefer Update for continuous input, coroutines for sequencing, and UniTask only if that async ecosystem is established.

Handling Unity coroutine cancellation on scene unload requires explicit lifecycle ownership using OnDisable or OnDestroy. Bind coroutine startup to OnEnable and implement cleanup with IDisposable or cancellation tokens to ensure cancelled tasks are properly cleaned up without resource leaks.

UniTask works with MonoBehaviour lifecycle cycles by applying explicit cancellation tokens during OnDisable and OnDestroy. It fits background async handling and network calls, but should only be used if the project already accepts the UniTask dependency to avoid unnecessary overhead.

Using Update for infrequent Unity timers causes performance issues in hot paths because continuous per-frame polling wastes cycles when nothing changes. For infrequent delays, dedicated timers or background async scheduling avoid unnecessary frame computations and reduce runtime overhead.

You need IDisposable patterns for Unity async task cleanup when managing background timers or network calls that outlive a single frame. IDisposable specifies lifecycle ownership, ensuring proper cancellation and resource release during MonoBehaviour enable, disable, and destroy cycles.