Posted by alentodorov 12/21/2025
This is a very interesting sentence.
I interpret this sentence as saying that manually entering a barcode is less error prone than letting AI do it, that AI would have an unacceptable margin of error (and this is probably an accurate assessment).
But you don't need AI to find or read barcodes. Finding and reading barcodes is a reasonably mature technology that has existed long before AI.
Barcodes exist as a fast, machine readable data transfer format meant to avoid data entry errors by avoiding manual data entry, and yet you've implemented manual entry in order to avoid errors?
Now, if one of the constraints you've put on your implementation is that it work only in the browser and you don't want to have to download a large barcode scanning library to the browser, then it makes sense to implement manual entry. But that has nothing to do with AI.
That being said, there are some barcode reading apps that can be used to prompt for a scan from a web page, and you get the barcode payload back. I've used an app called "bineye" on Android (source on GitHub) that works like this. This helps avoid error prone manual entry and gets the full barcode payload (many barcodes store/encode more information than the human readable text printed next to them).
https://serratus.github.io/quaggaJS/ seems browser friendly?
Generally I agree with your point on AI fuzziness here not being useful.
I have to scan bar codes every once in a while with an app on my iPhone, which definitely doesn't use AI. It will instantly recognize a bar code before I've had a chance to line up the camera properly, and the error rate is zero.
edit: oh, I guess you can't, because Apple Wallet doesn't support it.
[1] https://developer.apple.com/documentation/walletpasses/pass/...
https://developer.apple.com/documentation/walletpasses/showi...,
{
...
"locations" : [
{"latitude" : 37.3229, "longitude" : -122.0323},
{"latitude" : 37.3286, "longitude" : -122.0143},
{
"altitude" : 10.0,
"latitude" : 37.331,
"longitude" : -122.029,
"relevantText" : "Store nearby on 3rd and Main."
}
],
"relevantDate" : "2014-12-05T09:00-08:00"
}The privacy concern about sending pass data to the server is valid though. Since .pkpass files need to be cryptographically signed with Apple's certificate, there's no way to generate them purely client-side.
Potential solution: open source the signing code and let users run it locally with their own Apple Developer account ($99/year). Power users would do this, casual users can use your hosted version.
Also works with Google Wallet apparently, which is great for Android users.
SuperCards is very very similar, and in my opinion more useful than putting everything in Apple Wallet. You get to store a pictures, and everything is in one place. Apple Wallet is already cluttered with tons of creditcards, tickets, etc
To be honest though, a micro loans company engaging in this behaviour doesn’t surprise me at all.
> The Service Provider will retain User Provided data for as long as you use the Application and for a reasonable time thereafter. If you'd like them to delete User Provided Data that you have provided via the Application, please contact them at blub@blob.com and they will respond in a reasonable time.
That looks like a placeholder address to me? Not exactly confidence inspiring if so…
> please contact them at support@supercardsapp.com and they will respond in a reasonable time.
Technically you could use blind signing, no?
Didn't know it was this simple to just provide a download for prepared file. Is it open source?
(Not sure whether the current licensing offerings are worth it, though. I’ve got grandfathered in from before it had AI support.)
One obvious concern here is data privacy, since the pass details are sent to the server. Any chance it would be possible to run everything in the browser, without sending data back to the server?
Why can't the browser send the hash to the server for signing?
Because I don't see the.... utility if it?
Unless this achieves something specific I don't know.
So yeah, in Google Wallet you can just add the loyalty card like that (scan the qr/bat ode or type the number), and then have it synchronised to your account (to have it available on your other phone for example).
Sure, not every kind of the pass can be added like this (not movie tickets or boarding passes), but all that matters.
Anything to do with Google Wallet passes just forwards me to a Google login page.
Google's format also has a download option but that format doesn't work well for desktop users, so Google prefers to import via the web.
One annoyance I've faced is that Apple Wallet will not accept a downloaded file, or a file transferred from another app. You must click a link in Safari or it will refuse to load the damn pass.
I'm surprised how terrible all of these major wallet apps are at handling the slightest of edge cases.
Turns out it uses a format called Codebar which is from 1972 and not supported by Apple wallet passes. This tool and most of the other linked ones in this thread did not work. (And also tried to charge me a recurring subscription to use once, but that’s another issue)
I found this one which generates many other barcode formats and generates them as images as a workaround. That seems to work.