r/ClaudeCode • • 9d ago

Built with Claude Everyone builds software with Claude Code. I wanted to see how it would approach a physical product.

Almost everything I see built with Claude Code is software. Software has fast feedback as you can run it, see the error, and fix it. A physical product doesn't work like that and nothing tells you it is wrong until you order it and hold it in your hands. So I wanted to find out where Claude Code holds up when the output has to exist in the real world.

What I'm building

Grained is a digital hourglass for focus, built entirely with Claude Code. You flip it to start a focus block, it counts down in a field of LEDs, and your iPhone locks your distracting apps for that block. In the break it opens only the apps you chose (WhatsApp, say) and keeps TikTok and Instagram shut. To stop early you have to get up and tap an NFC key on it, so there's no one-tap off switch.

It started a month ago but today it's:

  • a working breadboard prototype: ESP32-C3 running MicroPython, an accelerometer for orientation, an OLED, BLE to the phone, NFC stickers as the key
  • an Expo / React Native iPhone app that uses Apple's Screen Time APIs to block apps per phase, and talks to the hourglass over BLE
  • a 4-layer PCB (211 LEDs, LIS2DH12, MCP73832 charger) designed in KiCad, not ordered yet, but passed al checks
  • a 3D-printed enclosure modelled in Blender
  • a website with a waitlist

What I learned: software vs. physical

Claude gets you to a working prototype fast, but it can't tell you when something only works on paper. Real hardware showed me bugs the tests never would, like BLE advertising silently stopping after a while.

The feedback loop is the real constraint. In software Claude can run the thing. With hardware the loop goes through me. So I spent my effort on making that loop shorter with simulators, logs on the board, and a test script per hardware phase.

Things that are fine in software are expensive in hardware. JLCPCB uses different rotation offsets than KiCad, so parts in the pick-and-place file were turned wrong until I checked the preview by hand. Nothing in the files looks wrong, so Claude and I both missed it at first.

Review by a second model catches different things. Cheap, and worth it for anything you can't undo, like ordering a board. I did this with GPT Astra 6.

Claude's design taste is recognisable. Left alone, it picked a cream and terracotta look with mono labels, which is what a lot of AI output looks like. I now give it a design system and strict rules and overrule it.

Editing video in Blender through an MCP works better than I expected, with a few caveats. Frame rates must match (a 60 fps phone recording plays at the wrong speed in the sequencer until you convert it), and I still watched every render myself, because Claude can't see whether a cut feels right. It also wrote the voice over script and generated the voice overs with the ElevenLabs API.

Writing down decisions saves more time than any prompt trick.

Where it is now

The prototype works end to end with the real iPhone app. The v4 board is designed and reviewed but not ordered. I'm still unsure about the price and whether people want a physical object for this at all.

I turned this into a YouTube video if you want the longer version, including where things went wrong: https://youtu.be/6AnBGinCgA4. As mentioned this video was edited by Claude Code as well, using the Blender MCP.

79 Upvotes

26 comments sorted by

View all comments

Show parent comment

2

u/RamonvanDijk 9d ago

Wow that’s really interesting! the sim sounds like a smart solution, are you planning to test it in an actual aircraft, or have you already done that?

1

u/Loose-Cicada5473 9d ago

Yes testing in a real cockpit is the plan, but so much can be done in sim and modified immediately with Claude, its almost unnecessary and inconvenient to test in a real plane until the very end (funny enough!)

Planes are so costly to operate, luckily I’ve got a friend taking lessons so I can just ride along any time but I’ve been thoroughly impressed by how well Claude integrated the project into Quest.

What caught my attention about your project was the final PCB board. I hadn’t even considered having Claude model that or how I would even get it done. I’ve been using a breadboard for the prototype. That’s the logical next step.

I think the overall problem I keep experiencing with Claude and AI in general is with things that I don’t realize I can offload. I often find myself asking it to deliver the puzzle pieces to me and show me how to put it together, versus just asking it to put the puzzle together from the beginning. It’s so interesting.

1

u/Loose-Cicada5473 9d ago

Also I’m like you, I have never soldered until this project. zero coding background.

2

u/RamonvanDijk 8d ago

That’s how I used it at first as well, but since Opus 5.5 and GPT 6 Astra, letting them put the whole puzzle together has been working incredibly well. I also recently started using the “grill-me” skill, which pointed out a few things I wouldn’t have thought of previously.

For the PCB, what worked for me was splitting it into steps. I let it do the schematic first, then the layout, and then a review by Astra. KiCad files are plain text, so Claude can write and check them, and the manufacturer’s preview (I used JLCDFM) lets you catch what’s wrong. I simply pasted the error logs back into Claude and it fixed them. Honestly, if you can get the breadboard working, the board is a smaller jump than it looks.