Building an Evidence Pack Before Piloting Industrial Android Terminals

A terminal that runs a demo app may still be unsuitable for a production fleet, since procurement, developers, and operations often hold incomplete and disconnected information. The article recommends compiling a small evidence pack that links requirements to a reproducible device configuration, including board revision, hardware modules, OS build, firmware, and SDK details. Each requirement should have a named evidence owner, and untested items should be recorded as unverified rather than passed. Broad claims such as scanning or serial support should be converted into specific, testable conditions with expected outcomes defined in advance. The guidance also stresses tracking Android version, security patch level, and firmware, and treating vendor security and update assurances with caution until they are documented and dated.