HN Explorer

20 comments

[ 3.7 ms ] story [ 49.3 ms ] thread
jakozaur
Good direction.

I wonder how it compares to using OpenCV other on top of much nicer API and doing everything yourself.

Benjamin_Dobell
Wait... what? Why is this part of the Google APIs framework (closed source) and not part of the Android Open Source Project?

Here we go, folks.

btian
Because this is higher level in terms of functionality than OS. Android API lets you access hardware, e.g., get a photo from camera, establish a network connection.

Processing data from hardware is higher level.

Benjamin_Dobell
I didn't say make it part of the OS, I said part of the Android Open Source Project. The platform SDK (applications, services, UI, media playback, notifications etc. etc.) and the support library are both extremely high level and part of AOSP.
abalos
There are many applications of this stuff outside of Android though. I agree that it's a little weird for it not to be incorporated in AOSP, but it could be used on Chrome OS. Heck, maybe even iOS? I think Google is just trying to keep the door open for developers on different platforms.
natch
Because that way Google gets to decide what uses you put its AI to. Recognizing faces and barcodes? Sure. Want to ask for the AI's help in recognizing business opportunities in click data? Sorry, that functionality is reserved for Google.
[deleted]
(comment deleted)
ocdtrekkie
Because ZXing Barcode Scanner works anywhere, so Google had to fix it so barcodes can only be scanned on proprietary Google phones.
memorion
because the developers would be stuck with the version the manufacturer ships with the device, this way all users are on the same version. they could still open source it though
kllrnohj
Probably because they didn't want to open source it?

There's still a lot of secret sauce in this general domain.

lnanek2
Would be nice if they provided more information about their implementation. I currently pay for a barcode API that doesn't have the dumb binary off/on pixel logic of the free version of zxing almost everyone else uses. It's just better UX for users if their bar codes can be recognized even with out of focus images, for example. There's nothing on this site about if the Google library is better or worse than popular open source offerings, however.
chkuendig
which api are you using? im currently looking into the same topic...
nly
Last I looked, Clef, who rely on barcode scanning as the basis for their entire product, were using ZBar[0] on Android. It's a C library. I think it's unmaintained these days though. No commits on sourceforge for 3 years.

[0] http://zbar.sourceforge.net/index.html

vladtaltos
any information about licensing the API ? cost-wise ? I couldn't find it in the site
lorenzhs
I'm pretty sure processing happens on the device, it's not a web API. No cost.
habosa
Totally free, you can use it on any device that has Google Play Services.
cpcat
i think this only works on snapdragon processors with fastcv. i tested this on snapdragon dev kits 2 years ago.
waynenilsen
I wish this could be used in a broader context without involving Android.
dangerboysteve
What is the performance of the barcode scanning? The commercial Scandit crossplatform lib is amazing (see videos) www.scandit.com