Built a Windows app with Claude

Started by Drastic, November 17, 2026, 02:30:11 PM

Previous topic - Next topic

Drastic

I've not really had much time to play with AI for personal usage, and working on a new pc build, I gave it a shot, and have to admit I'm pretty amazed.

I decide to get an AIO for a pc with a 9800X3D which causes air cooler fans to ramp up and down noisily. It came with a simple lcd screen. However, the app was bloated and clunky.

I asked claude for a replacement app and was instructed to download a USB stream capture software. (Didn't know this was a thing.) I performed 3 operations sending commands to the lcd/aio, capturing the usb input on the device each time separately, and gave that to claude.

Claude rewrote the app in python so I needed to install python and dependencies for building the executable. This was the most time consuming bit of the whole thing, mucking with the correct install and dependencies. But once that was sorted, I ran the batch file claude gave me to build the exe.

Fired it up and it work great. But it was a CLI, so I asked for a GUI. Next build, had a simple right-click on systray icon, gui.

I saw the new app was still consuming up to .5% cpu time, while much better, wasn't satisfactory. Claude taught me that the cooler had no onboard storage so the app has to stream each frame. So, claude decided to tweak the app with different fps options on the gif, to find a happy balance between frames delivered and cpu time. (I didn't yet think to ask for this.)

So, now I have a lightweight app with every functionality of the oem app, with new options to control frame rate. The whole process took me right at an hour, and most of that time was spent on the python setup. Pretty amazing and thinking of what I'll build next.

We've been doing some cool stuff at the office with ai. Mst recently, we pay for oneup at the office for social media management over multiple accounts with scheduling, etc. for $300/mo. One of our guys just built a replacement with claude so we're now canceling that.

There is a ton of opportunity right now with AI. At some point all this compute is going to cost end-users a lot more and I feel that a lot of the strength we have currently will eventually be gated-off from the general public and maybe everyone without some kind of clearance. It's kind of like the 90s web, right now.

rcjordan

>USB stream capture software

Wait! What??

>python

Yeah, Gem wanted to build a python script to scan 3dprinting .3mf folders (similar to zip folders). I put it on the to-do list because I don't want to tackle a python install.

Drastic

https://desowin.org/usbpcap/
So, you load this and figure out which pcap is the target by unplugging/replugging the device in question. I don't know how to read the captures though, AI chewed right through it.

Python setup was actually super easy, you just have to tick the necessary boxes on install.


ergophobe

Quote from: Drastic on November 17, 2026, 02:30:11 PMClaude rewrote the app in python

I have a website that is 15 years old. I built it in a weekend to solve a simple pain point: the NOAA website wasn't mobile friendly and I wanted forecasts for precise altitudes.

I have basically not touched it since, which means it is on a horribly insecure version of Drupal and it's been a niggle for years, but with all the hacking and such, I just had to get rid of it.

I put this prompt into Google AI Studio

QuoteI have a website that pulls a forecast from NOAA and uses XSLT to output the forecast in a mobile-friendly format. The site currently uses Drupal but I want it to be just a static site except of course for the forecast data which updates dynamically. You can see an example forecast page at https://stuff.tld

It spit out an entire site flawlessly. It got rid of all server-side dependencies - not only drupal, but no PHP or anything. It's a React site (which I would normally hate but since I do not have to do anything all with the code, what difference does it make). And it added a bunch of features that are nice to haves that I never bothered with.

The only issues I had were that my software was out of date and so the build program (Node and npm) had be to updated. Once they were, I ran the build, moved the files to web root and it runs.

I can now not only remove the old Drupal, I can remove PHP and MySQL from that site and pare it down to something extremely difficult to exploit.

If not for my outdated build software, this would have been 10 minutes total.

Drastic

Sweet!! Can we get the url? I'm about to ditch android and the noaa app isn't there.

ergophobe

#5
https://yosemiteforecast.com/

That is completely untouched - exactly as generated first go.

There are some glitches.  If I enter a page URL other than root it won't render. Bizarre. Haven't looked into it yet.


Note that the design is completely different from the site it was based off of. The hourly forecast and several other features are completely new, just added in the fly by the AI

I really like the bottom nav which it lifted from the weather.com app I think, but adapted for my site.

My original version was just a mobile friendly forecast and navigation. In some ways I prefer that - very simple and readable.

But I'm still super impressed. The last time I tried something similar it took a few hours of tweaking prompts and asking for refinements and so forth. It felt more like coding but fast. This was more like magic.

ergophobe

#6
Here's what it looked like from 2014 to today (you'll have to copy and paste because of how archive.orf formats the url

https://web.archive.org/web/20250223210537/https://yosemiteforecast.com/

rcjordan

### Missing Parameters & Source Gaps

* **Compiled Bundle Not Provided:** Only the root `index.html` shell is included; the application logic resides in `/assets/index-CLs76O-s.js` and styles in `/assets/index-CQAJy3Vt.css`.
* **Source & Legacy Template Absent:** The underlying source files (such as React/TypeScript components or location config) and the friend's original Drupal/PHP implementation are not present in this snippet.

---

### What This Code Shows

* **Static SPA Shell:** Uses standard HTML5 metadata, Google Fonts (`DM Sans`, `JetBrains Mono`, `Outfit`), a `<div id="root">` mount point, and hashed `/assets/index-*.js` and `/assets/index-*.css` files characteristic of a Vite static build rather than server-rendered Drupal or PHP.
* **Cloudflare Injection:** Contains a Cloudflare browser challenge/telemetry script (`__CF$cv$params` / `/cdn-cgi/challenge-platform/...`) and Cloudflare Web Analytics (`beacon.min.js`).

---

### Modifiability for Other NOAA Locations

* **Yes — Coordinate-Driven:** The National Weather Service API (`api.weather.gov`) resolves forecasts by latitude and longitude rather than park-specific endpoints, so any point or route with coordinates can query NOAA data once the location coordinates and labels in the app code are updated and rebuilt.
* **Practical Constraint:** Editing a minified production bundle directly is brittle; modifying the original source project (or rebuilding a clean replacement from the location list) is the reliable path.

ergophobe

What is that output from?

>  Only the root `index.html` shell is included;

When I told it that I couldn't access pages directly, it added the endpoints. I need to rerun the build script though, which I haven't done yet

> Google Fonts

Decisions like that make it slower than the original for sure.

You can see the lag when you go to a new page too.

rcjordan

I'm not interested in copying it but Drastic made me wonder.

I just copied the source, told Gem that it was a remake by Claude of a friend's Drupal/PHP site (I did not mention React), and asked what could it tell me about it & could it be replicated for other locations.

A good bit of the assets I had already figured out, but it was interesting to see Gem break it down.

Drastic

#10
Very cool! Thanks

It's pick up some nice mentions:
https://www.google.com/search?q=-site%253Ayosemiteforecast.com+%22yosemiteforecast.com%22

forum sw is break the url, here's the paste:
-site:yosemiteforecast.com "yosemiteforecast.com"

ergophobe

That reminds me... When I first got the idea (see below), I noticed that NOAA had an XML feed and I had one of those Aha! moments where I realized that if they were pumping out the raw data, I was not wedded to their crappy interface.

So I grabbed the feed, fed it through an XSLT template to format it the way I liked.

I expected the AI to do roughly the same, but when I asked AI Studio to rebuild it without the Drupal dependency, it came back with

QuoteInstead of server-side XML/XSLT processing, the browser fetches live GeoJSON directly from NOAA's CORS-enabled api.weather.gov endpoints (12-hour 7-day forecast periods, 24-hour hourly forecasts, and active NWS alerts) with a 5-minute sessionStorage cache and manual Refresh NOAA trigger.

So it really started over, not even pulling from the same data source. And it understood the underlying architecture of the original just from the HTML output, without seeing the code at all.

It is ridiculous how capable these systems are.

I was at my nephew's last week. He's a senior software engineer for a small company, formerly worked at Palantir and before that Cisco. He said for real work on hard problems the frontier models are worth it and that it has gone from being like having a junior engineer working for you a year ago to now being like having a peer on chat.

He is quick to point out that your peer on chat is not an all-knowing oracle. Your peer makes mistakes. Your peer has ideas she hasn't thought through. But it's still hugely helpful to have someone of your same ability with a different perspective. That's where he sees AI now. Generally speaking, if a senior engineer can do it quickly and easily, so can the AI. If it's genuine novel work, the AI is a useful collaborator.

He said the models released about six weeks ago are enough better that, "If anyone starts talking to you about using an AI for coding and they haven't used a frontier model seriously in the last six weeks, just pay no attention to everything else that comes out of their mouth."

He also pointed out that for almost his entire working career, most collaboration has not be in person, but via Slack, Skype, IRC. Using a chat window to converse with colleagues is default behavior. I think it can be for us older people too, but he has never known a collaborative environment that did not have instant messaging.

So that means that for engineers of his generation and younger, the AI doesn't feel weird or foreign. It feels like any other colleague, just super fast, very smart and always available.



> It's pick up some nice mentions:

Interesting. I've never paid attention. This was literally just to solve an annoyance for myself.

I live at 5600 feet. Four miles in one direction it is 2000 feet. Four in the other it is over 8000. Precise forecast locations make a big difference. Right now it is raining at my house and snowing half a mile away. So I wanted ready access to the forecasts that matter to me for recreation without having to be on my own machine with my own bookmarks.

And the NOAA forecasts were unreadable on mobile at the time.

Thus the site. My wife used it at work and people saw it and from there it got a bit of a local following. That fell off when NOAA forecasts got mobile-friendly (even though the home page still isn't and there is no iPhone app).

It also changed park practice. One person who started using it also compiled the Daily Report, sent to all park employees and members of the public who want it every morning at 9. They used to just have the mostly useless Zone Forecast. So Jeffrey changed the Daily Report to have half a dozen point forecast locations as links.

I've never paid attention to whether other people were using it or mentioning it on the web. It's a pretty niche thing. I don't think many people have that much forecast variation within a few miles of their home.

rcjordan

> I don't think many people have that much forecast variation within a few miles of their home.

Yeah, elevation doesn't vary much here. And if it is low, it is full of water. But a local area's close proximity to big bodies of water does change air temps by a couple of degrees F.