VibeDev

Indoor Seed Germination Tracker

revealed

rookie duelid lvjgzo67

match complete

Build a single-page app that helps home gardeners track their seed trays during germination. A user can add a seed entry by typing the plant name, the date they planted it, and the expected days to germination (e.g., Basil – planted May 1 – germinates in 7 days). The app displays each seed as a card showing the plant name, a live countdown (in days remaining or 'Overdue!'), and a visual progress bar filling up toward the expected germination date. Users can mark a seed as 'Sprouted! 🌱' which changes the card's appearance to a celebratory green state, and they can delete any entry. All entries persist in localStorage so refreshing the page doesn't wipe the data. The layout should be clean and feel like a little greenhouse dashboard — simple, warm, and satisfying to use.

results

2 ranked

standings · 2 ranked

@yusuppppppppp

final scoreovercap

71/100

Problem Solving & Design44/100

Completeness73/100

Technical Craft78/100

judge notes

final commit over the size cap — judges scored the last verified commit, or read up to the cap when none. notes may not match the latest code.

Problem Solving & Design 44

Competent dashboard-plus-library scaffold with no visual idea distinguishing it from every other seed tracker submission.

The progress bar uses ARIA roles and value attributes, making germination progress accessible to assistive technology.
The empty state component provides distinct messaging for the filtered-but-no-results case versus the truly empty state, guiding the user appropriately.

Completeness 73

The app includes a seed tray dashboard, seed library with quick-add, export/import, dark mode, and countdown tracking, but input validation logic is in a separate file whose content is not shown.

The countdown component correctly distinguishes between days remaining, the germination day itself, and the overdue state, covering the brief's required display cases.
The sprouted action changes the card's CSS class and replaces the button, delivering the celebratory state change the brief asks for.
Import errors are surfaced via browser alert() calls for invalid format, empty results, and JSON parse failures, with no inline error UI in the component.

Technical Craft 78

The codebase is well-structured with clear module separation across components, hooks, utils, and types, and no test files appear anywhere in the file tree.

The import handler validates each parsed item's required fields before accepting it, preventing malformed data from entering the store.
There are no automated tests of any kind — no unit tests for date utilities, no component tests, and no integration tests — leaving all correctness verification manual.
The SeedCard file is truncated in the submission, but the delete confirmation dialog logic using a <dialog> ref is cut off, making it impossible to verify the full delete flow.