← sources

Six months building a Windows desktop app with Claude Code, as a graphic designer who can't code

source: reddit (reddit:ClaudeCode)published 2026-10-24 08:59ingested 2026-10-24 11:00

retained text

[Every day since April 16. The darker part of each thread is fixes and reverts.](https://preview.redd.it/8gyif3ahqdxh1.png?width=1600&format=png&auto=webp&s=5152f3d86ed2932fd4a60e4a53c2baee58a13644)



I've been a graphic designer in Italy for twenty years. Print, editorial, video, some 3D. I don't know how to code.

On April 16, around 7 pm, I opened a Claude Code session and described something I'd been missing for years: one place where each job's programs, folders and files wait for me exactly as I left them, so when a client calls about a correction I can jump straight into their project instead of reopening everything. At 9:46 pm the first version ran. That evening it was Opus 4.7; the same project has since gone through Opus 4.8, Fable 5, Opus 5 and now Opus 5.5.

Six months later it's called Warpstead and it's in free beta on the Microsoft Store. The repo has 1,614 commits, and 544 of them are fixes or reverts.

I didn't expect the 544. I went in half believing the demo version, where you describe the app and the agent hands it back finished. For something this size it doesn't work like that, at least not for me. I decide what a thing should do and how it should feel, Claude writes it, I try it on my own PC, and most of the time I come back with what's wrong: a window that flickers when you zoom, a drag that lands two pixels off. After twenty years of layouts you notice the two pixels.

The hard part was getting ordinary Windows programs to run live on the canvas. Some attempts took days and went in the bin. Giving each app its own virtual desktop held up for a while and then fell apart. A virtual display driver lasted three days before we reverted it. DWM thumbnails (the API behind the taskbar previews) looked perfect until YouTube came out as a black rectangle. Claude could always explain why something had failed, but dropping it and trying another way was my call every time. In June we also threw away the first foundation, Tauri and WebView2, and moved to our own host on CEF.



[Programs, folders and files on one canvas. Chrome and the terminal are running live.](https://preview.redd.it/ulnyp3ahqdxh1.png?width=1920&format=png&auto=webp&s=4213dfceb4f7ef1bd0a6cf0b26781dda4cd490f6)



The first time I had Word, Chrome playing a YouTube video, Affinity and a terminal with Claude Code all running live side by side, and could take any of them full screen with one gesture, I was thrilled.

How Claude Code is set up, since that's what people here usually ask. The repo has a [CLAUDE.md](http://CLAUDE.md) with the build checks and the commit style. There are five subagents with narrow jobs: a cheap one that only searches the code, one that runs the builds and reports just the errors, one for Rust and Win32, one for the React interface, and a reviewer that reads every diff before a commit. Then there's a memory folder, over 440 files by now, where every mistake and every decision gets written down with the reason, so we don't pay for the same one twice. Before any change Claude also says how much process the job deserves (straight fix, measure first, or delegate with one review), because early on a fifteen-line fix took three hours of agents and reviews.

Claude Code writes the code; the design, the decisions and the testing are mine. Most of the bugs only show up on a real PC, so that last part is most of my week.

If you want to see what came out, the preview runs in a browser with nothing to install, and the beta is free on the Store: [https://warpstead.com](https://warpstead.com)

document fetched 2026-10-25 00:35 · canonical https://reddit.com/r/ClaudeCode/comments/1xe3r56/six_months_building_a_windows_desktop_app_with