Skip to content
Blog

Android Kiosk Hardware: How to Match the System to Your App

By YJCEN Engineering Team
YJCEN angled touchscreen kiosk beside a three-step selection flow: application requirements, hardware configuration and workflow testing.

Choose Android kiosk hardware by the application it must run, its connected devices and how it will be maintained. An Android version or processor name alone cannot establish compatibility. YJCEN’s Interactive Kiosk offers Android or Windows configurations, with customizable memory and storage, so the practical decision is which configuration completes your application’s workflow reliably.

Does the application need Android, Windows or a browser?

If your supplier provides an Android APK, evaluate an Android configuration. If the existing application requires Windows or a Windows-only peripheral driver, start with Windows rather than budgeting for an unplanned software conversion.

A browser application can leave either option open, but its requirements extend beyond opening a URL. Test the supported browser or WebView, login, downloads, printing and any camera or scanner access used by the actual workflow.

The current YJCEN kiosk specifications list Android / Windows as selectable, RK3568 / RK3576 for Android, and customizable RAM and storage. Some earlier datasheets describe Android 11 with 2 GB RAM and 32 GB eMMC; that is a documented configuration, not the limit of the current product range.

Why is “Android compatible” not enough?

Requirement Decision it changes Evidence to use
Minimum Android version Whether the application can install and use its required APIs Application minimum API level and supported OS versions
Native libraries Whether processor architecture and the installed OS image are compatible The application’s supported ABIs and the device image’s supported ABIs
Browser or Google services Whether login, maps, notifications and web content work Required browser/WebView versions and any Google Play services dependency
Peripheral interface Whether the application can operate the exact printer, scanner or payment device Device model, connection, driver or SDK and a complete transaction test
Device management How the kiosk starts, restricts access and receives updates The selected management method tested on the proposed image

Android’s minimum SDK documentation distinguishes the minimum API level needed to run an app from its target SDK. A target version alone is not an installation requirement or a compatibility verdict.

For applications containing native code, Android’s ABI documentation explains the architecture-specific interface. Check the application package against the supported ABIs of the actual OS image; a processor’s 64-bit capability alone does not establish what that image supports.

How much memory and storage should you specify?

Size memory around the heaviest screen and the processes running alongside it. A static directory, a browser showing a large interactive map, and an ordering application with a device-management agent impose different workloads; screen diagonal is not a useful RAM requirement.

Installed RAM is shared with the operating system and background services. Likewise, nominal storage is not free application space: account for the OS, application, offline content, logs and temporary space used during updates.

On the proposed configuration, repeat the busiest workflow with realistic content and the management software active. If the app reloads, stalls or runs out of update space, adjust memory, storage or the workload before approving the configuration; do not approve it merely because the installer completed.

Will the peripherals and kiosk mode work together?

Count occupied connections, not just sockets on a specification sheet. YJCEN’s listed two USB connections and one RJ45 connection provide a starting point, but an integrated device can already use a connection; the complete peripheral arrangement must fit the selected configuration.

A scanner may deliver keyboard-like input or require an SDK. A printer needs the correct driver or application integration, and a payment terminal needs the selected provider’s supported connection; a matching USB plug does not settle those software requirements.

Kiosk mode is also part of the software deployment. Android’s lock task mode guidance distinguishes managed access restrictions from screen pinning, which a user can exit. Test the intended restriction and update method on the selected image; an Android label does not establish a particular management or Google-services configuration.

What should the sample test prove?

Four stages of kiosk sample testing: startup, normal use, interruption recovery and maintenance, with the tested software and peripheral versions recorded.
Test startup, normal operation, interrupted sessions and maintenance on the proposed configuration. Record the OS image, application version and peripheral models that pass.
  1. Startup: after a restart, the intended application opens and the operator can recover it through the agreed management method.
  2. Normal use: complete the real search, ordering or check-in workflow with the selected peripherals and representative content.
  3. Interrupted use: disconnect and restore the network, cancel an operation and restart the app. The interface should recover without exposing the previous visitor’s session or duplicating a transaction.
  4. Maintenance: install an application update, verify free storage and repeat the workflow. Record the OS image, app version and peripheral models that passed.

This is a proposed acceptance sequence, not a claim that every application has already been tested. YJCEN can preinstall and test customer-supplied software; software licences and project integrations are specified separately.

Use the information kiosk hardware guide to choose the enclosure around visitor tasks, or the self-ordering software and peripheral checklist for an ordering deployment.

Specify a kiosk around your application

Send the APK or application URL, supported OS versions, any native-library or Google-services requirements, peripheral models and management method. Include screen size, installation environment and quantity so YJCEN can review a suitable system and hardware configuration.