91–100 of 262 posts
Number of steps to scan grocery by phone: 1. Find your phone 2. Unlock 3. Swipe left to home page three or maybe four 4. Visually scan for the AmazonFresh icon and tap 5. Wait for loading 6. Start scanning action 7. Confirm and pay Number of steps to scan grocery by Dash: 1. Get device from drawer or pantry 2. Press one button and scan 3. Confirm and pay For the target demo (30+, married, households with children), o…
"Number of steps to scan grocery by phone"
Most people just use pencil + paper, or notepad/note app on phone. Never have I seen people actually use technology while shopping unless it's a typed out list.
Number of steps to scan grocery by phone: 1. Find your phone 2. Unlock 3. Swipe left to home page three or maybe four 4. Visually scan for the AmazonFresh icon and tap 5. Wait for loading 6. Start scanning action 7. Confirm and pay Number of steps to scan grocery by Dash: 1. Get device from drawer or pantry 2. Press one button and scan 3. Confirm and pay For the target demo (30+, married, households with children), o…
Not to be a pedant but you're neglecting steps in your Dash algorithm that you implemented in the phone version (possibly creating a visual bias). Number of steps to scan grocery by Dash: 1.) Find scanner 2.) Turn on scanner 3.) Start scanning action 4.) Find laptop (or mobile phone) 5.) Navigate to browser 6.) Sign in to Amazon Fresh Account 7.) Confirm and pay I don't honestly think the Dash would provide a discern…
Also, if something like this gets baked into iOS or Android the steps change to "Swipe from home screen. Select 'Scan'."
Though I trust Amazon here and assume their hardware works in more situations than a phone's camera
Number of steps to scan grocery by phone: 1. Find your phone 2. Unlock 3. Swipe left to home page three or maybe four 4. Visually scan for the AmazonFresh icon and tap 5. Wait for loading 6. Start scanning action 7. Confirm and pay Number of steps to scan grocery by Dash: 1. Get device from drawer or pantry 2. Press one button and scan 3. Confirm and pay For the target demo (30+, married, households with children), o…
Option A
1. Ask your phone to buy {name of item}
2. Screen turns on, tap to confirm your purchase
Option B
1. Find the Dash device
2. Scan the item (if you haven't already discarded or recycled it, and haven't ruined the barcode in the process of opening it)
3. Confirm and pay
To me, Dash feels like a (possibly unnecessary) stopgap on Amazon's part. I understand they have the means to try things like this, but selling a device seems superfluous given the developing capability and direction of phones. As an Amazon customer, I hope Option A is their endgame.
Break out your phone, load up your barcode scanning app (there's 20 seconds right there even if the phone is in your pocket). Now try to actually scan something with it. You'll spend another 30 seconds lining up the little on-screen window with the code, rotating things, waiting for the camera to focus, and even having to move to another location if you're not in bright lighting. It's a terrible experience and that's why you don't see stores checking people out using the camera of an iPad.
A barcode scanner, on the other hand, just works. You point it in the general vicinity of the barcode, press the button, and it's scanned. You don't have to perfectly align anything, be in specific lighting, or wait for a camera and an app. I'm sure you've seen cashiers run multiple things over a scanner in under a second.
Amazon Dash isn't just a subset of your phone's functionality. It's a dedicated barcode scanner, which is hardware you don't have on your phone.
Earlier quoted context omitted.
Probably because nobody wants to use mobile apps with bar code scanners. Related: http://picturesofpeoplescanningqrcodes.tumblr.com/
Which is the conventional wisdom (no one scans anything) but its not actually correct. I've done some QR tests which have picked up hits (not huge mind you but non-zero). There was also the story of the guy[1], on Sharktank, where one of his props was a QR code and he picked up customers who scanned it (from their TV) while watching the show. It isn't common, that is for sure. And the bar code folks don't make it eas…
HN'ers asking why this isn't a cell phone app take note - this exemplifies why we (geeks) don't make good use cases for consumer tech and we should always be careful looking to our own habits and values when in a Product Development role. We're rarely the target customer and rarely behave like "average Joe". We're naturally resistant to superfluous redundancy ("My phone can already snap a barcode, I don't need a sepa…
Opening an app is, thankfully, something the tech industry has managed to train the average consumer to do. I'd argue though remembering where you put this thing, or "oh hey the wifi password got changed why isn't the food scanner working?" adds lots more complexity than hitting an app icon. The app route also enables you to have multiple scanners - since the target audience of such a product is probably already heav…
2) If you're cooking and your hands are occupied/covered, you're going to have a hard time using a phone with your hands. Phones aren't typically waterproof, and touchscreens don't typically work well with water on them.
3) If you use a screen lock on your phone, any app is immediately inconvenient given #2
This device seems to be designed specifically for the job, and has a low per-use setup cost.