# Starting point: FE engineer, Cache API after IndexedDB

Learner is a frontend engineer with completed SSE, Web Workers, and IndexedDB missions in this repo. Goal (issue #2) is practical judgment for offline support, asset caching, and resource management via the Cache Storage API — not shipping one PWA checklist. Cache API was already the “HTTP assets / app shell” contrast on the IndexedDB storage spectrum; do not re-teach that spectrum from zero. First ZPD lesson: place Cache Storage firmly as Request/Response storage (code-driven, usually SW-paired), separate it from IndexedDB and from pure HTTP cache, and practice choose/reject decisions.
