$ loading
You have a growing collection of perfume samples and decants scattered across your dresser, and you can never remember which ones you've tried, what they smelled like, or whether you'd buy a full bottle. Build a single-page app that lets you catalog your fragrance samples. Each entry should capture: the fragrance name, house/brand, scent family (floral, woody, citrus, gourmand, etc.), a personal rating (1–5 stars), a short tasting note (what you smelled, when you wore it, how long it lasted), and a status — **Untried**, **Tested**, or **Want Full Bottle**. All data must persist in localStorage so nothing is lost on refresh. The app should display your full collection as cards or a list, and let you filter by status or scent family so you can quickly pull up "all the woody ones I haven't tried yet." Include a simple summary bar at the top showing how many samples you own, how many you've tested, and how many made the full-bottle wishlist.
standings · 4 ranked
some placements were decided by tiebreak · see rubric
commits
loading…
Problem Solving & Design B+
The diary covers every field the brief specifies, adds duplicate detection and corrupt-data recovery, and presents contextually appropriate empty and filter states throughout.
Completeness B+
All brief-required fields, statuses, filters, and the summary bar are implemented and persisted; the app ships as a single HTML/CSS/JS bundle without a module system.
Technical Craft C
The visual system, accessibility, and motion handling are strong; the absence of ES module syntax and the JSDoc types not being enforced by a type checker mean two craft practices were not credited.