# Notes

## Learner profile
- Frontend engineer; sibling tracks: SSE (complete), Web Workers (complete)
- **Motivation:** general FE toolkit depth — design-review judgment for browser platform APIs
- **Prior knowledge:** none assumed on IndexedDB depth; knows localStorage/cookies exist; understands workers can use IDB-class APIs (from Workers dealbreakers)
- **Depth:** system-design decisions + interactive practice; light hands-on later if useful
- **Why this topic:** top recommendation after SSE + Workers — fills durable client storage / offline data gap

## Teaching preferences
- Decision frameworks, tradeoffs, deal-breakers
- Browser APIs and integration difficulty from an FE perspective
- Short interactive lessons (same shape as SSE / Workers)
- Cite high-trust sources; don’t invent API behavior

## Session log
- 2026-07-14: Mission established; resources seeded; lesson 1 (when IndexedDB fits — storage spectrum)
- 2026-07-14: Lesson 1 passed; primary web.dev storage read; MDN basic terminology deferred → lesson 2 (open/stores/keys) uses it as primary
- 2026-07-17: Lesson 2 passed (open/stores/keys); next lesson 3 (transactions & CRUD)
- 2026-07-17: Lesson 3 passed (transactions & CRUD); primary MDN Using IndexedDB **not** read → lesson 4 (indexes/cursors) uses it as primary and can lightly backfill
- 2026-07-17: Lesson 4 passed (indexes/cursors); external primaries still unread (MDN Using IDB / terminology / web.dev idb); lesson 5 deal-breakers next