Mobile Barcodes NeoReader on the iPhone vs Nokia N95 Barcode Scanner
Last week a release went out that NeoMedia had released the NeoReaderfor the iPhone. I decided to check it out. Because I also have a Nokia N95; with the Nokia Barcode Scanner on it I decided to do a face-off between both the products.
How?
Well, I chose the same sets of barcodes and I took a picture or scanned them using the two services.
But before I start the comparison I need to mention that the solutions from the iPhone NeoReader is a classic picture solution. You see a mobile barcode you take a picture and then it directs you to the content online. But with the Nokia solution it is a scanner. This means that you hold the device as near to the barcode as possible and it scans it for you.
I have to be honest, I have used this Nokia solution couple of times now and the best thing about it is the barcode scan noise and click sound that accompanies the scan when the barcode is read. Also there are two red lines with the Nokia Scanner which makes it easy to see where the phone needs to be placed.
With the NeoReader you can take the image and you have an option to change it take it again or go with the original.
On conducting these tests I tried to take several types of image with the NeoReader (near and from afar). So basically in some cases you could only see the barcode but in others you could see the barcode and physical objects. To demonstrate this I have taken some video (http://www.flixwagon.com/bena) or side panel to the right of this article – but unfortunately it didn’t come out.
So, I took pictures of the following codes. I found them all via a Google Image search of Mobile Barcodes. I took the pictures of the online versions and in this test I only used the online versions.
Results
What I found was that both the Nokia device and the NeoReaderreturned results for the 2D barcode successfully. I found the taking the picture of the barcode very easy to navigate. The scanner was fast for the 2D code –but there is a little knack to holding it right first time to get it correct –because the image looks larger via the phone that it does on the PC.
So, I do realise that the Nokia scanner is a 2D mobile barcode scanner. So, I didn’t expect any results for any other codes. But I tried anyway. What I didn’t like, was that if the scanner didn’t recognise the code it just gave up and went into standby mode. There was no clarification and no comment.
At one point I was scanning the 1D barcode with the Nokia device for about a minute (verge of hand ache) when it just shut down. This was a bit tiresome. Yes, to be expected but a “we don’t get that code” or “scan not possible” or images of the types of codes that the Nokia devices does scan in the terms or help section would be appreciated.
The NeoReader managed to scan three of these mobile barcode vs the Nokia one type only. When I took pictures of the code that it didn’t scan with the NeoReader; as with the Nokia– there was also a lonely silence. If the code is not recognisable nothing seemed to happen. So then I tried typing the number into NeoReader for the 1D code. It recognised it was a 1D code and also told me that this particular one didn’t exist. (Nice).
Both the readers didn’t get the shotcode or the Scanlife code. I think I must have been imagining it as I thought that some Scanlife codes had numbers on them. The ones that I found and used, were all codes that looked half empty. (I am going to come back to this in another article).
So then I moved to Kaywa. I went to Feed2mobile and typed in GoMo News and got the barcode. This was the best user experience and quality ever. It took me less than 3 seconds with the iPhone NeoReader and about 5.5 seconds with the Nokia N95 to get the best looking RSS version of GoMo on the site (see picture).
So what we think?
Well, I think that the scanner is a great idea from Nokia. But it might be a bit early. Holding the device to the barcode is a bit cumbersome and on one occasion I was left waiting for a minute before the phone switched to standby. This either means that I never got the scan in the right position (it worked with the NeoReader) or it just gave up.
Also, the NeoReader saved every picture that I read and catalogued it for future use. This wasn’t an option with the scanner.
Even when the picture quality of the NeoReader wasn’t at its best, results were delivered (not for Scanlife or Shotcode).
So, with this particular test, the NeoReader performed better because taking a picture was instant and results were delivered quickly in 2 clicks (or 3 seconds) . Even though I could listen to the sound of scanning a mobile barcode on the Nokia N95 all day – I think that some work still needs to be done.
1. Education. Nokia needs to educate users on what a 2D code and what will work.
2. It needs to do more than just hope consumers realise they need to scan the code within the two red lines.
3. It must start to interact with users and say if the code can or can’t be read. This is because holding the scanner over a code is tiresome and frustrating.
On the other hand the NeoReader can also improve
1. By responding to images that are not readable with a health warning.
Capturing images at this point in time for mobile barcodes was a lot easier than scanning.
Actions for the future
1. You know what – The NeoReader with the new black and orange design and the icon on the iPhone looks great. I am sure that a scanner can be put on the NeoReader moving forward and a marriage of the Nokia and NeoReader solution would be the best remedy.
2. But, if that takes time to occur:
a. Both readers need to have a stronger communication side with consumers stating what can or can’t be read.
b. There are more 1D codes than 2D codes and reading both codes is essential.
3. I would like to see a recommendation service coming out after this barcode reader. I realise that the NeoMedia relationship with Mobotended –but a visual mobile search company could add a lot of weight to this – recommended additional codes if ones that were read didn’t do the job. A sort of “did you mean” or “similar barcodes” would add real flavour to this.
I now have several readers on 3 different devices and expect more comparisons such as this one. I want to do a 1D barcode scanner session too.
Related News:
Perhaps I can add a couple of points of interest to this. First let me say that I fully expected the IPHONE to be slightly faster in returning results, since the workings of the two phone models vary so greatly
On the issue of scanning versus taking a picture, I am glad you brought that issue up. Based on what I have been able to learn, any JAVA based application requires you first take a picture or snapshot, before any type of action can be performed. Scanning type application gives immediate results if the code is recognizable.
For that reason some of the more popular bar code reading application developers, suich as Quickmark, have decided not to adopt their reader to the Java platform, as they see this requiremnt to take an action first as a hindrance to the end user down the road. Here is a response I received from Quikmark, when I inquired about this issue.
“However, we currently do not support the Java platform because we feel that
the Java platform has certain constraints that may not provide the best overall
user experience.
For instance, Java requires the user to perform a “snapshot” before each
recognition whereas we prefer to offer a zero-click experience. ”
On the shotcode and scanlife code issue, if my knowledge is correct, the only readers that will read those codes, are the company who developed the codes reader. They are not open standard data matric or QR codes, and were independently developed by the respective companies. So for instance, if you have Scanbuys reader on your phone, you are supposed to be able to read all standard datamatrix codes and QR codes, and in addition can read their own code they developed, which is a variation of the open standard data matrix code.
A universal reader that will read open standard Data Matrix and QR codes, will not read variants of those codes developed by another company. The Neoreader will not read them at this time, and as far as I am aware no other reader will read them either, except the code developers own reader.
To go back to the first issue for a second, I understand developers concerns that a user must first take a picture of a code before they receive any type of action. The camera function of most mobile phones is a very power consuming action. Most users would not go around taking pictures of codes, if they know its going to drain their batteries rapidly out in the field. That would slow down the mass adoption of the technology. A work around for java type platforms needs to be developed, so the user can just scan over the code, and see a pop up showing them the link or content of the code, before they decide if they want to click on it or not, or before they active their browser to go directly to the content, which is another concern as it too uses more power, as well as data time for those who do not have unlimited data packages with their service provider.
Brewskih
On the JAVA aspect, the camera API is available under J2ME (JAVA) so I don’t think QIK is correct. Although I have run dev teams developing mobile apps I have ever used the camera api in JAVA so I will ask around and find out.
cheers
Rob
Thanks Rob,
I would be very interested in what you find out.
Quickmark, being praised as one of the best readers on the market, in all the reviews I have read, would seem to have some very smart engineers on their team, so I put a lot of trust in what their response was on this issue.
I forgot to add - that I used an EDGE Nokia N95 and an EDGE iPhone - to be fair.
Are you saying that you compared the different readers on 2 DIFFERENT cell phones?
What is the point? Thats comparing apples and oranges.
I appreciate the review and your comparisons, but they are don’t tell me anything unless you are using the same cell phone.
Different phones have different memory and processor speeds.
Please rerun your test using different barcode reader on the SAME cellphone.
Brewskih
Ok, I did a root around the net. Although the camera is available through JAVA it is not a real time solution. You do have to press a button to initiate taking a picture/snapshot whatever you want to call it. The Mobile Media API (JSR 135) allows the operation under JAVA. More details can be found here: http://tiny.cc/QGWuz
Under Symbian C++ the camera is constanly available and once a barcode is recognised the software then can initiate a call to action.
So, under JAVA a button has to be pressed, under Symbian its in real time and does not.
I wouldn’t exactly call this taken a snapshot first as it can be done inside a JAVA barcode application, so to the end user its all part of the process, personally I don’t think having to push a button is a major problem!! especially as a large percentage of the population are used to the notion of point and click but what do I know eh
Anyway I found a couple of video’s of a JAVA barcode application and a symbian version both from the same developers - which I think is interesting.
http://tiny.cc/yeawv
best
Rob
Scanning is not possible under J2ME, but that extra click is no problem IMHO.
Zero Click - Automatic Scanning on the iPhone using the NeoReader
http://i30.tinypic.com/i1cvgh.png
Screenshot captured using the iPhone’s screen capture program.
Just tried Neoreader on my iPhone, it is not zero-click. Requires taking picture and a lot of waiting. Success rate is also low. So far all the iPhone barcode readers are like this.
I amnot sure what you mean by zero-click.
I just watched video of how the Scanbuy application Scanlife will work on the Iphone at
http://www.youtube.com/watch?v=qMFucpGn55E
Is this zero-click, or is it 1-click?
How many clicks does Neomedia’s iphone application need?
GoMo News is a fun and happy business blog with nice replies if one wants to be provocative or get into arguments or just post low IQ responses please go elsewhere.
I have to completely disagree with most of the posters here.
If we are ever going to see mass adoption of this technology, one click is not an option. I’ve been part of demos and pilots with CIOs and “average Joe’s” and the difference between zero and one click is formidable.
I’ve gone over this with some UX people, and they noted how important the difference was.
There is also a major “wow factor” of just swiping the viewfinder over the barcode and being redirected. I was doing a video of a code scan and I had to do it in two shots, as I couldn’t explain the process it happened so quickly.
Zero clicks or bust!
except of course the clicks needed to launch the application in the fist place..so zero clicks doesn’t actually exist!
[...] are back with more 2D barcode info. In “Mobile Barcodes NeoReader on the iPhone vs Nokia N95 Barcode Scanner” we are treated to a comparison of the two readers. Bena Roberts of GoMo News does a good job of [...]
Zero clicks to me means that the user does not need to press a button to “take a photo” in order to decode a barcode. It is possible that the end user take several photos and not get any decode result.
heard through the grapevine that scanbuy’s app got rejected. anyone hear the same? thanks.
rejected for what? It is a proprietary app. Not sure what you are talking about.
Bena
Hi Bena
Hows the holiday going
I think Dan is saying there is a rumor Scanbuy app was rejected for I-Phone app store. JMHO
[...] Hat schon einmal jemand gestestet, ob der Neoreader zufriedenstellend auf dem iPhone läuft? Bena von GoMoNews hatte erst vor ein paar Tagen im Selbstversuch den Neoreader auf dem iPhone gegen den [...]
Scanbuy’s iPhone app is out: link. But only recognizes their own code.