
This problem covers sending every request of a library app through one API client, so each page gets its data, its loading state and a clear error message from one place instead of handling them itself.
This problem covers translating a library's loans API into the app's own models, so every screen shows the same due date and fine instead of converting the raw data itself.
This problem covers giving every book and loan in a library app its own address, so a shared link opens the right page with its data already loaded instead of landing on the home page.
This problem covers building the data layer behind a library's loans desk, so check-outs and loan extensions load and save in the API's shape and a failed save never loses what the librarian typed.
Learn frontend system design by building one growing app: API layers, component architecture, state, caching, rendering, performance, real-time UI, auth, accessibility and observability.
2 modules: API Integration & Data Layer and UI Component Architecture.
8 exercises, all easy.
Challenges run on Node.js 24.
No. Every challenge runs in a browser-based IDE with everything already set up, and your code is graded automatically against a test suite.