All projects
web
A weather dashboard that handles failure
Consume a public API and deal with the parts tutorials skip: errors, loading and empty states.
Why it matters
Most beginner projects show the happy path only. Handling a failed request, a slow one, and a city that does not exist is what makes this look like production code.
What you build
- Live data from a public API
- Loading, error and empty states that all exist
- Search with debouncing
- Sensible behaviour when the API is down
If you want more
- Cache recent searches
- Add a 5-day forecast view
Build it
- Turn the network off and confirm it degrades gracefully
Material for the whole build
Shows you write for the unhappy path, which is the difference between a tutorial and an application.
Get a plan built around projects like this