All originals
CommunityShipped 20235-week sprint
BoardGame Group Library
One shelf, shared by the whole table.
Scroll for the technical layer
Layer 01 — The world
A dark shelf of boxed worlds seen edge-on, one spine catching cold blue light.
A shared collection for game groups: who owns what, what is in the box, and what nobody has played yet.
Interface01
Motion02
System03
Layer 02 — The build
X-ray the interface. See the engineering.
The challenge
Every game group has a spreadsheet, and every spreadsheet has four versions. Nobody knows who owns the expansion, and the shelf at the host's house is the only real inventory.
Architecture decisions
- 01Group-scoped library with a single canonical ownership record per copy.
- 02Barcode and photo ingest to add a game in under ten seconds.
- 03Offline shelf view so the inventory works in a basement with no signal.
Build process
Week 1Audited four groups' spreadsheets, found 38 duplicates.
Week 2Prototype: scan, confirm, on the shelf.
Week 3Ownership model and group invites.
Week 4Offline shelf and cover matching.
Week 5Ship to twelve groups, watch them add.
Stack
- Client
- React Native · Expo
- Data
- Group-scoped library
- Ingest
- Barcode + cover match
- Sync
- Offline-first, conflict-free
From the codebase
// One canonical copy per owner, many views
addCopy({ gameId, ownerId }) // shelf, list and group view stay in syncMeasured results
9s
to add a game
38
duplicate records eliminated
94%
libraries with 20+ games in week one
Principles in play
The technical layer holds the challenge, the architecture decisions, the week-by-week build and the numbers. Open it when you want to judge the engineering, not the screenshots.
Next originalTrip Synced
Build the next one