Draw on a QR code, and the health bars will accurately display how close the QR code is to being unscannable. How few errors does it take to break a QR code? How many errors can a QR code handle? Counters at the bottom track your record minimum and maximum damage. (Can you figure out how to break a QR code with 0.0% damage to the actual data region?)
Also, click on the magnifying glass button to toggle between "draw mode" and "inspect mode". I encourage you to use your phone's camera to scan the code as you draw and undo/redo to verify that the code really does break when the app says it does.
I wrote the underlying decoder in C++, and it's compiled to WebAssembly for the website.
I hope you find it interesting.
flysand7•10mo ago
It seems to be missing some explanations regarding how the code is structured and how it performs error correction. I feel like there's little point in interacting with a system you don't understand or not trying to understand. And I also think there are cool ways to make those things interactive as well. Pick an image, then explain what the little squares in the corners are for and provide little interactivity to see how they affect the decoding. Then move on to the error correction. This step-by-step style of interactivity may be better, I'd think about that.
As for what is there, the first thing I don't like here is icons. The four icons in the lower-right corner (result data, format info, ..) are hard to distinguish, and are hard to correlate with the "history" tab. I'd probably either make them slightly different color, or actually simplifying these icons further might be a better option, just because they're so small.
But yeah it is pretty hard to tell what I'm interacting with, unfortunately. I don't know pretty much nothing about QR codes, and I don't know what the different kinds of errors are, what "EC" stands for etc.
UI should probably be rethought as well, because before I was writing the comment I had no idea I could switch a brush. Hell, I had no idea I was changing colors (the cursor covered half the space of the pixels, so I couldn't tell)
The idea's cool though, good work
Xiione•10mo ago
Ultimately I'm glad that I was able to get the main point across. That is, that QR codes can take a lot more abuse than one might assume. Thanks for checking my work out!
boomskats•10mo ago
You don't know what EC stands for but you have an opinion on when the error correction should be demoed? And the first thing you don't like are the icons?
OP, if I were you I would ignore this critique entirely. This is a fantastic demo. The usability was spot on (I learned a lot in a very short amount of time) and your /repos readme is _exactly_ what I wanted to read. It is perfectly executed.
I'm gonna dig into your code a bit more tomorrow, but you should be very proud of this. You have a bright future ahead of you.
Xiione•10mo ago