ACQUIRED

Why I made it

We save photographs by the thousands, but the context around a physical object is much easier to lose: where it came from, who owned it, how it was acquired, and why anyone cared enough to keep it. Acquired is where that context gets to survive.

What I built

Acquired treats everyday objects like museum holdings. Each object receives a permanent accession number and a structured record, like title, date, maker, classification, materials, place, acquisition history, and provenance, alongside its personal significance. Photographs document each piece, and every record can stay private or be made public individually.

The product logic

The system starts with accessioning rather than organizing. A collection code, year, and sequence number give every object a stable identity; the collection view makes those records searchable; and the individual object page keeps the full history behind the thumbnail. The structure is meant to remain useful as a collection grows instead of depending on folders, filenames, or memory.

Design direction

The product itself borrows from museum collection catalogs rather than social feeds: accession numbers, structured records, restrained typography, and object-focused layouts. The portfolio page stays within the same visual system as the rest of my work so the project feels like part of one body of experiments rather than a separate microsite.

Built to keep growing

Supabase handles authentication, structured object records, and image storage. The app also supports image cropping and browser-based background removal, so object photography can stay visually consistent without changing the underlying record. This isn't about owning more. It's about remembering why any of it mattered.