The brief calls for "that same hinge feel, but in plastic"

A design lead asks for a hinge that opens with the same resistance as a product from a teardown three projects ago, and answering that well depends on whether the teardown photo — and the notes about why that mechanism worked — is actually findable, rather than sitting in a folder named after a project that shipped and was archived a year back.

Where a working designer's reference actually accumulates

It is rarely one library. Competitor products bought and photographed for a teardown, material swatches shot under studio light for a finish comparison, trade show photos of things that caught your eye for reasons you meant to write down later, sketches and CMF boards handed over by a colleague on a project you joined mid-way. Each folder made sense on the day a project needed it. Almost none of it is named for the question that actually comes up later — "what did that hinge feel like" — which is exactly the reference a new brief needs first.

A mechanism or a finish, found across every project at once

Registering a project drive's existing folders as one workspace does not require reorganising anything a studio already has in place. in:Teardowns scopes a search to disassembly photos only, while tag:any:brushed-aluminium reaches every matching material photo across Teardowns, Materials and Competitor-Products at once, regardless of which project first needed it.

type:image tag:any:soft-touch-tpe rating:>=4     rated finish studies
in:Teardowns tag:any:snap-fit                     scoped mechanism reference
added:>2026-01 -tag:archived                      this quarter's active set

A term the parser does not recognise renders as free text rather than an error, so a half-remembered material name from a review still returns something to narrow down from.

Rating what actually held up in a prototype

Not every teardown or material sample survives contact with an actual prototype, and the difference rarely shows in the filename. Rating a photo once a mechanism or a finish has been tested — four stars for a hinge feel that made it into tooling, one star for a material sample that photographed well and felt wrong in hand — turns rating:>=4 into the shortlist worth reaching for on the next brief that calls for something similar, rather than a re-scroll through every sample ever photographed.

Keeping a materials vocabulary that survives a change of project

A studio's material and mechanism reference tends to outlive any single product, and a folder structure built entirely around one project's part numbers does not travel to the next one. Tagging by material and behaviour — brushed aluminium, soft-touch TPE, snap-fit — rather than filing only by project name means a later brief can reuse a finish study gathered years earlier, found by tag:any:brushed-aluminium regardless of which product it was first collected for.

A shortlist boarded for a design review

A design review wants to see the reasoning behind a mechanism choice, not just the rendered concept, and rebuilding that reasoning into a slide deck for every review is its own small project each time. Arranging the relevant teardown photos, material swatches and prototype shots onto a canvas and presenting straight from it skips that step. The file stays in the project folder afterward, so the next designer working a similar mechanism finds both the decision and the reasoning in the same place.

What happens to a supplier's or a colleague's photos

Not all material and mechanism reference originates inside your own camera roll — a supplier's sample photos sent by email, a colleague's teardown from a project you joined partway through, a trade show photo someone else took and forwarded. None of it needs special handling beyond dropping it into the registered workspace; the watcher picks it up on its own, ready to tag alongside anything gathered first-hand.

Comparing this to a library tool that copies files into itself

Eagle is a capable option for the same job and copies whatever is imported into its own managed library, which suits some studios because everything then lives under one app's control. Coii Ref indexes a studio's existing project folders exactly where they sit instead, so a teardown photo an engineer already filed by part number never needs duplicating into a second, app-managed copy that could drift out of sync with the original. The round-up of Eagle alternatives covers the wider field if a tool that takes ownership of the files is the actual preference.

Working across a studio machine and a personal reference archive

Designers who freelance or contract across studios often keep a personal archive of material studies and teardown photos built up over years, separate from whatever a current studio's project drive holds. Register the personal archive on a personal Mac and, separately, a studio's shared drive on the studio machine — each builds its own local index, with nothing to sync and no account tying the two together. Licensing covers three Macs on one purchase, which in practice covers a personal machine, a laptop and a studio seat without paying twice.

What it costs and what it runs on

$19 once, three Macs, updates included, nothing that renews. The trial runs 30 days with every feature enabled, no card and no account required. It needs macOS 11 Big Sur or later, on Apple Silicon or Intel, as two native builds.

The app's entire outbound network activity is a licence check on Activate and a launch-time read of a server's Date header only, so a wound-back clock cannot extend a trial. No in-app updater means no update check, and there is no analytics or crash reporting.

Past day thirty of an unpaid trial, one category of action stops: growing the library, meaning registering a new folder, running the importer, or starting an index by hand. Search, tags, ratings, notes and the folder watcher all keep working permanently on what is already indexed, so a review does not stall because a trial ran out mid-project.

Why a materials archive is worth more the longer a studio has kept one

A studio's material and mechanism archive compounds the longer it runs, because a new brief rarely starts its reference from zero — it starts by reusing whatever the studio already tested on a similar part. A decade of teardowns and finish studies across a dozen shipped and cancelled products, searchable by material and mechanism rather than by which product gathered them, is exactly the asset a folder structure alone stops being able to deliver once it gets that large.

What a cancelled project's reference is still worth

A product that never made it past prototyping does not have to take its material studies and teardowns down with it, provided they were tagged by what they show rather than only by the project that gathered them. A snap-fit study photographed for a cancelled product is exactly as useful the next time a similar mechanism comes up on an unrelated brief, found by tag:any:snap-fit regardless of which product it was first gathered for.

What a benchmarking session actually needs on hand

Benchmarking a category — every competitor kettle, every rival's charging dock — usually means buying several products, photographing each one from the same angles, and then trying to compare them side by side later from whatever folder they landed in. Tagging each competitor photo by the category and the specific attribute being benchmarked, rather than only by brand name, means a later question like "how did rivals handle this vent" can be answered with one search across every teardown ever done for that category, not just the one from the most recent session.

What changes when a supplier updates a material sample

A supplier occasionally sends an updated sample of a material already in use — a new batch of the same soft-touch coating, a revised aluminium finish — and the old sample photo does not stop being useful just because a newer one exists. Tagging both by the material and adding a date or a batch note rather than overwriting the old photo with the new one keeps a record of how a finish has actually changed over time, which matters the next time a part fails and the question is whether the material itself moved.

Comparing this to keeping reference only inside a CAD project

Reference kept only as attachments inside a CAD file or a PDM system tends to be hard to search across projects and disappears from easy reach the moment a project is archived. Coii Ref works the other way: material and mechanism photos live as ordinary files in an ordinary folder, searchable by tag and rating long after the CAD project that first needed them has shipped or been shelved, with no PDM login required to go looking for last year's hinge study.

What a photography rig for products actually needs to produce

Photographing a competitor product or a material sample consistently enough for later comparison usually means a plain background, repeatable lighting and a few fixed angles, done the same way every time a new sample arrives. Tagging by that consistency — studio-lit for photos taken under the controlled rig, versus a quick phone photo taken on a trade show floor — lets a later comparison scope itself to tag:any:studio-lit when the question depends on colour or finish being judged accurately, while still keeping the quick, less controlled shots in the same searchable library for everything else.

What a design review's decision record is worth a year later

A review where a mechanism or a finish was chosen over the alternatives it was compared against is easy to forget the reasoning behind once the product ships and the team moves to the next brief. Keeping the shortlist board from that review as a file in the project folder, rather than a slide deck exported once and never opened again, means the reasoning is still there the day a similar question comes up on an unrelated product — found by opening the same canvas rather than trying to reconstruct a decision nobody quite remembers making.

Who this actually suits

A designer or a small studio whose material and mechanism reference is genuinely spread across more projects and more folders than any one person can hold in their head, who needs a finish or a hinge feel found by property rather than by remembering which product it came from. A related job built around building precedent rather than materials and mechanisms sits at the architect page, and a colour and scheme-matching habit from a very different craft is at the miniature painter page. The general digital asset manager round-up covers the wider field of tools for a solo studio managing its own archive.

Thirty days, every feature, no card and no account: download it and point it at whatever project drive has the deepest teardown history already on it. Tag the mechanisms that actually made it into tooling first — that is the search that answers "that same hinge feel" before the review runs long.