I've made a Playstation DualSense controller tester with #Claude #code using #Tauri and #Rust. After some initial hiccups that I was sure we'd have, because Claude did report it couldn't 100% determine what bits in the datastream corresponded to what piece of information; however, it's now working well. It's also #accessible to screen reader users.

You get connection status, battery status, data values for the sticks, triggers, touch pad and buttons, and three haptic tests. There are tones that pan for X axis movement and change pitch for Y axis movement across both sticks. They are distinct enough to be able to tell which stick is being moved. There are also tones for the triggers, each of which is panned in the appropriate direction. Similarly, the touchpad makes a sound when moved. I'm testing the battery reporting. It reads 10% as of now, and does report charging status. I'm curious if it will actually report accurately.

I had previously given up on getting Ai to write Rust code that actually compiles, because until now, I'd had no success with it. This not only works, it works reasonably well. With me having a grant total of zero Rust knowledge, I can't really audit the code, but I am curious if it's actually good or not. #blind #programming #vibecoding #accessibility #gaming