Hardware integration, done in production
The vendor tutorial got you to hello world. Production is where it stopped.
Production-grade UHF RFID integration guidance for Android and .NET — written by someone with the actual devices, who has shipped it 12 times, covering what the vendor tutorials explicitly say they don't cover.
Zebra — "Hello RFID" tutorial, official docs
"This app is intended for tutorial purposes only and should not be used in production environments."
Chainway SDK — inline comment, sample repo
@Deprecated // kept for backward compatibility only
> what happens after that sentence is what we do.
What we work on
Device SDK
Chainway, Zebra, and Sunmi SDKs — what the sample code doesn't tell you.
Printers & Encoding
ZPL, ZD621R, and label encoding that survives a production run.
Protocols & Standards
EPC Gen2, ISO 18000-6C, and the standards vendors gloss over.
Platform Integration
Odoo, .NET, and getting scan data into systems that matter.
The No-Brand Wedge
Cross-device patterns that outlast any single vendor's SDK.
Latest guides
All guides →Chainway C5 · Android · Updated Jul 18, 2026
Chainway C5 RFID Android SDK: Inventory to CSV
The Chainway C5 shares its UHF SDK family with the C72 — same UART-based reader class, same trigger-key pattern. Turning a raw inventory sweep into a usable stocktake means dedupli…
Chainway C72 · Android · Updated Jul 18, 2026
Chainway C72 Android SDK Integration in Kotlin
Chainway's C72 sample code targets RFIDWithUHF, a class the SDK itself marks obsolete. Production integrations must use RFIDWithUHFUART, handle the trigger key event directly, and…
Chainway (SDK family-wide) · Android · Updated Jul 18, 2026
Chainway's Obsolete SDK API: Migration Notes
Chainway's sample repositories across its UHF handheld line still demonstrate RFIDWithUHF, a class the SDK's own build marks deprecated in favor of RFIDWithUHFUART. This guide maps…
Generic Android scanner · Android · Updated Jul 18, 2026
Keyboard Wedge vs. SDK Scanning on Android
Keyboard-wedge input is sufficient when a scan only needs to land in a single focused text field with no metadata — it fails once an app needs RSSI, multi-tag reads, background sca…
12+
Hardware integrations shipped
★5.0
Across contracts
Every device
On the desk, not in a PDF
How it works
01
Feasibility read, in 24 hours
Send the device model, the SDK, and what's failing. You get a written read on whether it's solvable, what it takes, and what it doesn't — before any money moves.
02
Fixed-scope build
A scoped, fixed-fee build against the actual hardware — not a demo app, not a proof of concept that dies in the field.
03
Handover with docs
Working code, the reasoning behind it, and documentation your next engineer can actually use — no tribal knowledge locked in one person's head.