One thing to remember
Every API call has three visible states: loading, success, and failure. If you only design success, your app will feel broken during normal network delays.
A reviewer on mobile data should know what is happening, what went wrong, and what they can try next.
Why this matters
In a hackathon demo, your API may be slow because the free server is waking up, the college Wi-Fi is crowded, or the reviewer is on a hotspot.
A loading message stops people from clicking again and again. A failure message shows that you handled real-world use, not just the happy path.