Build a collection tracker app for records, cards, books or anything you hoard
Generic catalogue apps fail collectors because every hobby counts different things: a record has a pressing and a matrix number, a trading card has a set number and a grade, a book has an edition and a printing. Anticode can build a collection tracker app around your own fields, saved in your browser on one device. Here's how to design the data before you describe it.
Start with the item, not the screens
Write down three real items from your shelves and everything you'd want to know about each. The fields that appear on all three are your core; the rest are optional or belong to one kind of item. A few examples by hobby:
| Collection | Identity | Condition and value | Extras |
|---|---|---|---|
| Vinyl | Artist, title, label, catalogue number, year, pressing country | Sleeve and media grade on the usual Mint to Poor scale | Matrix runout, colour variant, signed |
| Trading cards | Set, card number, name, rarity | Raw condition or a grading company and grade | Quantity owned, foil or parallel |
| Books | Author, title, publisher, edition and printing, ISBN | Condition, dust jacket present | Signed, first edition points, where bought |
| Board games | Title, publisher, edition | Complete or missing parts | Expansions owned, last played |
Two fields matter across every hobby: status (owned, wanted, ordered, sold, lent out) and quantity. Status lets one list hold your collection and your wishlist, and quantity handles duplicates without separate entries.
Screens a collector will open
- Shelf view
- A dense grid or table you can sort by any field and filter by status. Collectors scan, so favour density over big cards.
- Item detail
- Every field, with notes and an edit button. Show the item's history: when added, price paid, when sold.
- Quick add
- The few core fields only, so adding a find at a record fair takes seconds. Fill the rest in later.
- Set progress
- For cards, stamps or a series of books: "37 of 120 in this set", with the missing numbers listed. This is often the screen that keeps a tracker in use.
- Wishlist
- Wanted items with a maximum price, to check against at a fair or shop.
Describing it to Anticode
Give the model the fields, the grading scale and how you browse. For example: "A vinyl collection app. Fields: artist, title, label, catalogue number, year, country, sleeve grade and media grade (Mint, Near Mint, VG+, VG, G+, Poor), price paid, status (owned, wanted, sold) and notes. Table view sortable by any column, a search box, a quick-add form, and a wishlist with a max price. Dark, dense, like a record shop's back office. Fill it with 20 sample records labelled as sample data that I can clear."
Then use it with real items and ask for changes as the gaps show: "add a field for colour variant", "let me filter by grade". If you collect two different things, ask for item types with their own fields rather than one form that tries to cover both.
Photos, storage and backups
Anticode's apps run in a sandbox with no network and no camera access, and they save to your own browser's local storage, which holds a few megabytes. That's plenty for thousands of text records. Photos are where it gets tight.
- A full-size phone photo can be bigger than the whole storage allowance. If you want pictures, ask for a picker that takes a photo already on the device and shrinks it to a small thumbnail, then test how many fit before you depend on it.
- For a large collection, keep photos in your phone's own albums and store a short reference in the tracker ("album: Records 2026, photo 14").
- Ask for export and import of your catalogue as a file. Clearing browser data, a private window or a new phone otherwise means starting again. Test the round trip once.
What it can't look up
Collectors often expect a scan or a search to fill in the details. Inside this sandbox that isn't possible:
- No barcode scanning. The app has no camera access.
- No online databases. It can't look up a release, a card set or an ISBN from a catalogue site; you type the details or paste them.
- No market prices. Values are what you enter. Live price guides need network access.
- No sharing or trading. Others can't browse your shelves or offer swaps; there's no shared data between visitors.
If what you want is a public showcase of your collection that you update yourself, a published site with CMS collections, which visitors read but don't edit, is closer to that than a private tracker. Stock for a shop is a different job again, covered under inventory tracking. For tracking many people's collections with accounts, the Next.js export of an app build is a starting point for a developer.
Questions people ask
Can a collection tracker app handle more than one hobby?
Yes. Ask for item types, each with its own fields, sharing status, quantity and notes.
Can I import my existing spreadsheet?
Ask for a CSV paste or file import with column matching, and test it with a few rows first. Everything imported stays in that browser.
Is my collection data private?
It's saved in your browser and not sent anywhere. Publishing the app doesn't publish your items; each visitor starts with an empty tracker.
Can it value my collection?
It can total the prices you enter, but it can't fetch market values.