I did. It’s mentioned in the article. (I updated the article for even more clarity though.) The system is good for single-player video games, where if the person cheats then they’re only cheating themselves. It’s not for securing bank information.
…but what is nice, if you’re creating a webview app from a Hype project, there isn’t an easy way to view the source from an iOS device. (If there is, I don’t know it. How do you view web page source on iOS?) So, this method is pretty good for creating a video game passcode system across multiple mobile platforms. (Sure, someone could just copy the app to the desktop, look at the code and figure it out, but again… just a deterrent.)
Another way to explain it is this… it’s like the Mike Tyson’s Punchout code. It’s not really a secret to experienced players. Lots of kids from the 80s probably have it memorized. But when you saw that code on the screen for the first time, you probably wrote it down.
For securing information, no… it’s terrible. That’s the point of the system. The codes are ultimately meant to be shared, but not right away. There has to be a perceived value. It’s like when a girl is undressing in an old movie. She will be nearby and say to the guy… no peaking… but then they totally have sex later in the movie. The “no peaking” is part of the foreplay.
Video game cheat codes are meant to be shared. Normally, you don’t post replies about my templates. Today, you did. You got to reverse engineer the system and tell others about it. This creates buzz. Imagine if people didn’t know the famous Konami 30 lives cheat code, would their games be as popular?