Software for the workflow
Keep your existing POS, ERP or kiosk application, use a qualified third-party platform or scope a focused Android application with UnitWeave. We connect the named workflow to the selected SUNMI device and peripherals, then document the integration, acceptance and support responsibilities before rollout.
Discuss your projectIntegration surfaces
The right interface depends on the model, variant, firmware, application build and accessory path. We document the exact setup under review instead of treating a catalog capability as a universal compatibility result.
Review receipt and label output for a built-in or external printer path, including the behavior an operator sees when a print cannot complete.
Map scan triggers and decoded data into the existing application without losing events during rapid entry or reconnects.
Review the exact base, accessory wiring, power path and application commands for counter peripherals.
Check the application where device-specific screen, lifecycle, permission, orientation and background behavior can change the workflow.
Prepare a repeatable path from signed package to preloaded, named and managed devices when the project includes a fleet rollout.
Separate the device workflow from acquirer, certification, tax, import and country obligations that require their own confirmation.
How a review moves
A useful integration review turns an open-ended compatibility question into a named setup with an acceptance record and a clear owner for the remaining risks.
Describe the transaction, task or handoff that must work in the field, along with the application and destination.
Output: application brief, target configuration and open questions.Review or test the exact model, Android version, firmware, application build, interface, accessories and network assumptions.
Output: compatibility notes, evidence state and known limitations.Coordinate the sample, acceptance steps, preload, naming, MDM, accessory pairing, staging and handover responsibilities.
Output: deployment profile, acceptance record and project-specific terms.Bring these facts
The more precise the initial brief, the less likely a device capability or generic Android assumption will be mistaken for a tested integration.
Application name, package or build and software owner
Target SUNMI model, variant, Android and firmware assumptions
Printer, scanner, cash drawer, customer display or payment path
Country, quantity, timeline, network and offline requirements
Acceptance criteria, credentials, signing, ownership and maintenance boundary
Scope and responsibility
Manufacturer-supported facts, a UnitWeave test, a customer validation and a project promise are different records. We keep those states separate so the acceptance decision stays traceable.
Before you send the brief
It can be assessed when the application build, target model, Android and firmware assumptions, permissions, screen behavior and peripheral interface are available. The result is specific to the named setup.
Software follows the workflow. Keep your existing POS, ERP or field application, use a qualified third-party platform or scope a focused Android application with UnitWeave; we name the business-logic owner, agree the device and integration surface, and document acceptance and support responsibilities before work starts.
Public examples must be original or cleared for redistribution. We can publish implementation notes and link to approved vendor references; a project sample or dedicated validation is scoped against the exact device setup.
Preload, device naming, policy, MDM enrollment, accessory pairing, staging and handover can be scoped as deployment engineering. Signing keys, credentials, ownership, updates and recovery responsibilities are agreed separately.
No automatic promise is made. Acquirer integration, certification, import, tax, warranty, repair and local support depend on the country, provider and written project terms.
Ready to name the setup?
Tell us what the application must do, which SUNMI configuration you are considering, where it will be deployed and how many devices are involved.
