The story behind Collectify

Collectify was inspired by a simple problem: collectors often build meaningful collections over time, but they end up managing them across different apps, spreadsheets, notes, or marketplace platforms. A vinyl collector may use one platform to track records, a trading card collector may use another, and anime merchandise or figurines may not have a clean home at all. That creates a fragmented experience where it becomes difficult to view everything in one place, understand the value of a collection, or simply organize personal items in a way that feels polished and intentional.

This project was designed as a unified collection portfolio that brings different collectible categories into one premium dashboard. Instead of treating every hobby separately, Collectify presents collections as part of a single personal archive where users can organize items, monitor estimated value, and explore their portfolio through a clean visual interface. The goal behind the project is not just storage, but creating a more thoughtful and modern experience for collectors who care about both organization and presentation.

SG

Shlok Goud

Developer

Responsible for UI design and implementation across every page of Collectify, from the theme system and component library to the charts, forms, and interactive user experience.

How Collectify sees your collections

Every user owns many collections. Every collection holds many items. Each item can track its own price history over time.

Collectify Logical Data Model Four entities connected by one-to-many relationships: User to Collections, Collection to Items, Item to PriceHistory. User PK user_id UUID name VARCHAR email VARCHAR password_hash TEXT created_at TIMESTAMP Collection PK collection_id UUID FK user_id UUID name VARCHAR category ENUM created_at TIMESTAMP Item PK item_id UUID FK collection_id UUID name VARCHAR purchase_price DECIMAL estimated_value DECIMAL PriceHistory PK price_id UUID FK item_id UUID recorded_at TIMESTAMP value DECIMAL source VARCHAR 1 : M 1 : M 1 : M PK · Primary Key FK · Foreign Key Relationships shown as 1 : M (one-to-many)

User Collections

One user can curate many collections, each grouped by theme or category.

Collection Items

Each collection holds many individual items like cards, vinyl and figurines, along with purchase and valuation data.

Item PriceHistory

Every item tracks its valuation over time, enabling trend analysis and portfolio insights.