Decompose: Break down #1 into implementable work units #9

New issue

Closed

opened 2026-05-27 01:03:38 +00:00 by Mark · 1 comment

Mark commented

2026-05-27 01:03:38 +00:00

Owner

Assessment

Issue #1 requests a backend/API layer for price data and alerts — currently all front-end mockups.

Proposed Phases

P1: Data model & persistence

Define schemas for markets, products, prices, and alerts. Set up SQLite or Postgres with migrations.

P2: REST API — price data endpoints

CRUD endpoints for market listings and price entries. Expose recent prices, history, and trends.

P3: REST API — alert system

Endpoints for creating/managing price alerts (threshold-based). Background check for alert triggers.

P4: Authentication & user scoping

Add user accounts tied to alerts/views. Simple JWT or session-based auth so each user sees their own alerts.

P5: Frontend integration

Wire frontend mockups to real API endpoints. Replace hardcoded price data with API calls.

## Assessment Issue #1 requests a backend/API layer for price data and alerts — currently all front-end mockups. ## Proposed Phases ### P1: Data model & persistence Define schemas for markets, products, prices, and alerts. Set up SQLite or Postgres with migrations. ### P2: REST API — price data endpoints CRUD endpoints for market listings and price entries. Expose recent prices, history, and trends. ### P3: REST API — alert system Endpoints for creating/managing price alerts (threshold-based). Background check for alert triggers. ### P4: Authentication & user scoping Add user accounts tied to alerts/views. Simple JWT or session-based auth so each user sees their own alerts. ### P5: Frontend integration Wire frontend mockups to real API endpoints. Replace hardcoded price data with API calls.