Cardboom. From discovery to a collecting workflow.

The product challenge

Collectors need to identify what they have, understand the available information, and find the next relevant action. A marketplace also needs to distinguish browsing, managing a collection, and buying or selling.

Those are different jobs. The product experience should connect them without making the user repeatedly enter the same information or lose their place in the catalogue.

The visible product scope

Cardboom’s portfolio screens show a multi-game catalogue, collection and marketplace interfaces, and scanning workflows. The app preview displays a 109k-card catalogue. That is a catalogue figure shown in the interface, not a claim about active sellers or transaction volume.

The product proposition also includes auctions, buy-now listings, portfolio tracking, and grading submissions. Availability should be checked in the current beta when evaluating a specific workflow.

• Card discovery and catalogue browsing
• Scanning and listing workflows
• Collection and portfolio views
• Marketplace and grading journeys

The infrastructure questions behind a marketplace

A marketplace brief must connect the interface to catalogue data, account permissions, listing state, and transaction events. Buyers should ask how duplicate requests, failed payments, and changing availability are handled.

These are the questions we bring to an infrastructure discussion. The public screens demonstrate the product experience; a detailed implementation proposal needs its own architecture review, system boundaries, and test plan.

What this means for a client project

Start with one complete journey, such as identifying an item and preparing a listing. Define the data and integrations needed at each step. We can then assess the web, mobile, and backend work required to make that journey usable.