14

I've been developing an Android app for a specific model of a handheld barcode scanner (almost 3 months) for our customers.. We are finally going live with this application so my boss ordered a new batch of devices. Bought the newer, fancier model instead of our test/dev model...

*Fatal error galore, different storage type, different barcode reader, deprecated functions,..*

Oooh the joys..
(Needs to be finished by tomorrow)

Comments
  • 1
    Someone did this with me once. I always build device recognition into my work, so trying to make it work with anything that my application isn't designed for is hopeless. This way you don't get any unexpected behaviour.

    I'd do this, and when it doesn't work, quote extra for the re-work time. That way you get time to breathe, do it right, and make some extra money.
  • 0
    @monr0e I do exactly the same. I know it sounds very limited, but honestly its the way to go to avoid multiple headaches
  • 0
    Building an Android app for a specific handheld barcode scanner sounds like one of those projects where the hardware details matter just as much as the code itself. I’d pay particular attention to scan response times, connection stability, and how the app handles repeated scans, since small issues can quickly become frustrating in daily use. If you’re still evaluating hardware or planning future compatibility, Elvotec are distributors of Hikrobot barcode readers, and their catalog is a useful reference when comparing options for a particular workflow. Here’s the resource I’d check: https://elvotec.eu/en/catalog/.... Getting the scanner integration right early can save a lot of debugging once the app is being used in a real working environment.
Add Comment