Equipment · Bill of materials

Tools

Everything the revival actually took, and what you can swap for what. If you're bringing your own Naked mirror back to life, think of this as the shopping list. The series walks the whole chain end to end: the iOS app, the mirror and its firmware, and the local server that stands in for the dead cloud.

Server

MacBook. The always-on local server. It runs the HTTP listener and the stand-in cloud the mirror uploads scans to, now that Naked's api.nakedfit.net is gone.

SubstituteAny always-on machine on the same network works: a Linux box, a mini PC, a Raspberry Pi. It only needs real horsepower if you also run the scan-processing step locally.

Device

Naked Labs mirror and scale. The hardware being revived. The mirror carries the three depth cameras and the BLE server; the scale doubles as the turntable that rotates you through the scan. Both are required for a scan.

SubstituteNone. This is the one part you can't swap, and it has to be one you own.

Pair programmer

Claude Code. Used throughout as a pair-programming partner: decompiling the APK, mapping the BLE protocol, building the diagnostic and production apps, and standing up the mock cloud.

SubstituteAny capable coding assistant, or just time and patience. It mostly saved iteration cycles.

Network

Firewalla. Used to reroute the mirror's cloud traffic to the local server instead of the dead Naked cloud.

SubstituteIt doesn't have to be a Firewalla. Anything that can override DNS or redirect traffic works: an /etc/hosts entry on the mirror itself, a Pi-hole, a router with custom DNS, or a small local DNS server.