Build a free network scanner app for Mac and Windows without writing code

A network engineer who cannot write Swift or Rust had Claude Code build ARPradar, a subnet scanner with device naming and UniFi maps, as a SwiftUI Mac app and a Tauri Windows port.

Done withClaude CodeinGitHub· Nov 9, 2026

What they did

Reddit user u/Lone_Wolf_555, a network engineer, wanted a scanner that lists every device on a subnet with IP, MAC, maker, a real name and device type. Claude Code wrote nearly all of it: a SwiftUI app for Mac and a Tauri port with a Rust scan engine for Windows. The app names devices from DHCP, UPnP, SNMP, web page titles and Ubiquiti discovery, guesses device types, saves scans per customer or site, draws a network map from a UniFi controller and exports to Excel. The poster's part was knowing what a good scan looks like and saying when something was wrong. Claude ran the tests, watched the GitHub Actions builds and tried the UI in a browser against demo data before handing it over, and showed mockups before building screens.

How it went

The app shipped free at arpradar.com. When the Windows builds kept failing, Claude worked out that GitHub's download servers were timing out, stopped re-running builds that burned minutes, and waited until downloads had stayed up for several checks before starting one. One commenter said it found every device on their LAN quickly. Apple signing was still a couple of weeks away when posted.

Worth knowing

Claude could not see the real network from its sandbox, so anything about live scanning was tested by the poster, who also entered API keys by hand. Commenters noted that ARP only works inside one broadcast domain, so remote VLANs give IPs and ports but no MAC addresses, and that a closed-source scanner from an unknown developer is a hard sell; the poster said they may open source it.

Try it

With Claude Code· 4 parts to fill in

Build me a desktop app for [Mac and/or Windows] that [what the tool should do, e.g. scans a subnet and lists every device]. I know the domain but do not write code, so ask me what a correct result looks like before you start. Show me a mockup of each screen before building it. Write tests and run them, and test the UI against demo data before asking me to try anything. Use [GitHub Actions or my CI] for builds; if a build fails for an infrastructure reason, find the cause before re-running it. Tell me when you need something only I can do, such as testing on my real [network or hardware] or entering keys.

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

Related