A loading state should answer two questions for the user: whether the application is still working and what can happen next. Show the destination layout promptly, reserve space for content that has not arrived, and replace placeholders without shifting the page unexpectedly. Use a determinate progress indicator when completion can be estimated; otherwise use a restrained activity indicator and a specific status message. Keep navigation and cancellation available when the underlying operation permits them. For recurring workflows, caching and prefetching are usually more valuable than elaborate loading animation because they reduce the wait itself.