The problem
A single product price tells you what something costs now, but not whether that price is actually interesting. Historical context changes the decision.
The outcome
The project explores price history as a useful signal instead of treating price as a static field.
The approach
The project explores a backend-first workflow for product data, price history and comparison, exposed through APIs to a responsive frontend.
Product discovery
↓
Price capture
↓
Historical data
↓
Comparison
↓
Useful insight
What I built
Product records
Price history
Comparison workflow
REST API design
PostgreSQL persistence
Responsive frontend
Engineering decisions
The core idea is to treat price as a time-series signal rather than a static field. That creates room for future alerts, trend views and smarter purchasing decisions.