Loading is the pause before the punchline, and errors are the plot twists we never wanted. (true developers feelings, cough cough) Jokes aside… You already know that handling loading states and errors is key. You've learned how to handle errors the right way in whole course, so even if something goes wrong, your app won’t crash completely. Instead, the part that’s broken will show a (hopefully helpful) error message. Once everything is set up, it’s pretty easy. But is that the only way?