Modules your application can drive
| Module | What your application gets |
|---|---|
| 2D scan engine | Decode results from Newland, Honeywell N3680 or Zebra 4710 engines, including continuous scan behaviour and the symbologies your workflow uses |
| Fingerprint capture | Image and template records from FAP10 capacitive or FAP20 and FAP30 optical sensors; the capture profile decides the image dimensions and the record format |
| Identity cards | Structured data from the second-generation Chinese ID card reader, offline, and from the online version where the workflow depends on a central service |
| NFC and RFID | Tag reads over NFC ST21NFC at 13.56 MHz (ISO/IEC 14443 Type A/B, ISO/IEC 15693) and over LF 125K / 134.2K, HF 13.56 MHz or UHF RFID depending on the platform |
Formats are confirmed against your application before the order is placed, rather than discovered during integration. That is the difference between a two-week integration and a two-month one.
What we put on the image
Pre-installed applications
Your APK is installed as part of the build, so devices arrive configured rather than needing a roll-out on site.
- Your application(s) and any dependencies
- Default language and locale for the deployment
- Supporting tools your team expects on the device
Device behaviour
Behaviour requirements belong to the software scope, not to a manual handed to the installer.
- Launcher behaviour and kiosk lock-down where operators should see one application
- Boot logo and start-up animation carrying your brand
- Policies your IT team requires before deployment
Send the APK and integration requirements at the feasibility stage so they can be validated on the sample. Changing the image after units are built costs time on every device in the batch.
How software requirements move through a project
| Stage | What is settled |
|---|---|
| Requirements and feasibility | Application list, module set, whether the platform can support the software you need, and any privilege questions |
| Written proposal | The agreed specification, documentation set and SDK coverage, confirmed in writing |
| Engineering sample | Your team integrates against real hardware and confirms output formats on a device instead of a datasheet |
| Verification and certification | The image is frozen and checked against acceptance criteria before mass production |
| Mass production and support | Units ship on that image; configuration changes for later batches are raised as a revision |
The full project sequence is described on the Custom Solutions page.
Software customization questions
What SDK support is included?
Which output formats are supported?
Can our own application be pre-installed?
What happens if our software depends on privileged access?
Send the software scope
The more of the following you send now, the more accurate the proposal and the fewer surprises at sample stage:
- Your application, or the integration requirements it depends on
- The modules it must drive and the output formats it expects
- Default language, launcher behaviour and whether kiosk mode is required
- Whether it needs elevated permissions, and for what
- The platform or model you intend to start from
- Quantity, destination market and target date
Request a quotation Chat on WhatsApp
Shenzhen Xinhong Smart Technology Co., Ltd. · WhatsApp and phone +86 185 9427 9341 · [email protected] · Mon–Sat, 9:00–18:30 (GMT+8). Back to the OEM and ODM centre · hardware customization · industrial design · Android OS customization · certification support.