Options de carte mère pour bornes : Android vs Windows

The mainboard is the computing core of a self-service kiosk. It runs the operating system and kiosk application, processes touchscreen input, communicates with peripheral devices, manages network connections, and exchanges data with POS, ERP, payment, membership, or cloud platforms.

Selecting a kiosk mainboard is therefore not simply a choice between Android and Windows. The correct platform depends on the software environment, required peripherals, processing workload, security policies, maintenance method, deployment scale, and expected service life.

This guide explains the practical differences between an Android kiosk mainboard and a Windows kiosk mainboard. It is intended for software companies, system integrators, project managers, maintenance teams, and kiosk operators who need to select, configure, or troubleshoot a kiosk computing platform.

AONKIOSK develops configurable self-service kiosk hardware that can be built around different computing platforms and peripheral combinations. The final mainboard specification should always be confirmed against the customer’s software and complete device list before production.

1. What Is a Kiosk Mainboard?

A kiosk mainboard, sometimes called a kiosk motherboard, embedded computer board, industrial PC, or Android control board, is the central electronic platform inside the kiosk.

It normally connects to:

• The touchscreen and LCD panel
• Receipt or ticket printers
• QR-code and barcode scanners
• Terminaux de paiement
• NFC or RFID readers
• Cameras and microphones
• Speakers
• ID card or passport readers
• GPIO-controlled buttons and indicators
• Ethernet, Wi-Fi, Bluetooth, or cellular modules
• Remote device-management systems

The mainboard determines which operating system can be used, how quickly the application runs, how many peripherals can be connected, and how easily the kiosk can be maintained.

A correctly specified board should offer adequate processing performance without adding unnecessary cost, heat, or power consumption.

2. Android and Windows Mainboards at a Glance

This comparison is a general reference. Actual performance depends on the processor, memory, storage, operating-system version, firmware, drivers, and software design.

3. Android Kiosk Mainboards

An Android kiosk mainboard usually uses an ARM-based system-on-chip. The processor, graphics unit, multimedia functions, and many communication controllers are integrated into a compact platform.

Common Android kiosk configurations include:

• Quad-core or octa-core ARM processor
• 2 GB, 4 GB, or 8 GB RAM
• 16 GB, 32 GB, 64 GB, or higher eMMC storage
• Ethernet
• Wi-Fi and Bluetooth
• Multiple USB ports
• HDMI, LVDS, or eDP display output
• Serial communication interfaces on selected industrial boards
• Android firmware customized for the kiosk application

Advantages of an Android Kiosk Mainboard

Lower Hardware Cost

Android boards generally provide a cost-effective solution for standardized deployments. They are commonly used when the kiosk performs a limited number of clearly defined tasks, such as displaying a menu, collecting an order, scanning a QR code, or submitting information to a cloud platform.

The lower board cost can become significant in projects involving hundreds or thousands of terminals.

Low Power Consumption

ARM-based Android boards normally consume less power than full x86 computers. Lower power use can reduce internal heat and simplify thermal management.

This is helpful in slim enclosures, wall-mounted kiosks, countertop terminals, and devices with limited ventilation space.

Compact Physical Size

Android boards are often smaller than Windows industrial PCs. Their compact dimensions leave more room for printers, payment devices, cable routing, power supplies, and maintenance access.

Fast Startup

A properly configured Android kiosk can usually start its application quickly after power-on. The application may also be configured to launch automatically and prevent users from accessing system settings.

Suitable for Touch-Oriented Applications

Android is designed around touchscreen interaction. It can be a practical platform for:

• Restaurant self-ordering
• Product catalogs
• Digital directories
• L'inscription aux files d'attente
• Visitor check-in
• Membership inquiry
• Advertising and information display
• QR-code payment workflows
• Simple ticket selection

For example, AONKIOSK’s APK04 restaurant self-ordering kiosk supports Android and Windows configurations, allowing the computing platform to be matched to the restaurant’s ordering or POS ecosystem.

Limitations of an Android Kiosk Mainboard

Driver Availability Must Be Confirmed

A USB device may be physically connected to Android but still fail to operate if no compatible driver, SDK, application programming interface, or serial communication protocol is available.

This issue commonly affects:

• Specialized payment devices
• Passport readers
• Some thermal printers
• Cash-handling modules
• Industrial card dispensers
• Biometric readers
• Legacy serial devices

Do not assume that a peripheral is compatible simply because it uses a USB connector.

Limited Compatibility with Windows Applications

Software developed as a Windows executable cannot run directly on Android. It must be redeveloped, replaced with an Android version, delivered through a browser, or hosted remotely.

Firmware Customization Can Be Board-Specific

Features such as automatic startup, scheduled power control, screen rotation, status-bar removal, watchdog behavior, or USB permissions may require customized firmware.

Changing the mainboard model later may therefore require new firmware development and application testing.

Less Suitable for Complex Local Processing

High-resolution video analytics, large local databases, advanced computer vision, multiple display outputs, or complex background services may require more processing capacity than a basic Android board provides.

4. Windows Kiosk Mainboards

A Windows kiosk mainboard normally uses an Intel or AMD x86 processor. It may be supplied as an embedded motherboard, fanless mini PC, industrial computer, or integrated open-frame PC.

Typical configurations include:

• Intel Celeron, Processor N-series, Core i3, Core i5, or Core i7
• 4 GB, 8 GB, 16 GB, or more RAM
• M.2, mSATA, or SATA solid-state storage
• Multiple USB ports
• RS-232 or RS-485 serial ports
• Ethernet
• Wi-Fi and Bluetooth
• HDMI, DisplayPort, LVDS, or eDP output
• Windows 10 or Windows 11, depending on project requirements and hardware support

Advantages of a Windows Kiosk Mainboard

Broad Software Compatibility

Windows is often selected when the kiosk must run:

• Existing POS software
• Desktop applications
• .NET applications
• Browser-based applications with local services
• Database clients
• Device-control utilities
• Enterprise security software
• Legacy business applications

This makes Windows particularly suitable when a kiosk is being added to an established IT environment.

Strong Peripheral and Driver Support

Many commercial devices are initially designed for Windows. Manufacturers often provide Windows drivers, configuration tools, test utilities, and SDK packages.

This can simplify integration with:

• Terminaux de paiement
• Receipt and ticket printers
• Lecteurs de codes-barres
• ID and passport readers
• Document scanners
• Distributeurs de cartes
• Cash acceptors and recyclers
• Weighing devices
• Biometric hardware

Windows is therefore frequently used for integration-heavy retail and payment kiosks.

Greater Local Processing Capacity

Windows industrial PCs can provide higher processor performance, greater memory capacity, and faster expandable storage.

They are often preferable for:

• Large local databases
• Multiple applications running simultaneously
• High-resolution media
• La vision par ordinateur
• Multi-screen interfaces
• Complex POS integrations
• Local reporting
• Advanced security services
• Virtual private network clients

Familiar Enterprise Management

Many IT departments already use Windows deployment, monitoring, antivirus, account management, disk encryption, and remote-support tools. Using the same environment can simplify operational management.

Limitations of a Windows Kiosk Mainboard

Higher Cost

Windows-compatible industrial computers usually cost more than entry-level Android boards. Memory, SSD storage, operating-system licensing, and higher-performance processors can further increase the total hardware cost.

Higher Power and Thermal Requirements

An x86 processor may generate more heat than an ARM-based board. The kiosk enclosure must provide adequate ventilation, heat spreading, or controlled airflow.

A poor thermal design can cause:

• CPU throttling
• Unexpected shutdowns
• Reduced component life
• Application instability
• Fan noise or fan failure

More System Maintenance

Windows systems may require more attention to:

• Operating-system updates
• Driver updates
• User permissions
• Antivirus policies
• Startup services
• Disk space
• restart scheduling
• application whitelisting

Uncontrolled updates can cause a kiosk to restart during operating hours or introduce a driver compatibility issue. Update policies should therefore be planned before deployment.

Longer Startup Time

Windows may take longer to start, especially when many services, security tools, or startup applications are enabled. A kiosk shell or startup screen can be used to hide the desktop while the application loads.

5. Which Mainboard Should You Choose?

The decision should begin with the software and peripherals, not with the processor name.

Choose Android When:

• The kiosk application is already developed for Android.
• The workflow is based mainly on a web application.
• Cost and low power consumption are priorities.
• The device performs a standardized set of tasks.
• All required peripherals have confirmed Android support.
• A compact or slim enclosure is required.
• The deployment uses centralized Android device management.
• Fast startup is important.
• Local processing requirements are moderate.

Android is often appropriate for restaurant ordering, information inquiry, queue registration, advertising, directory, and simple check-in applications.

Choose Windows When:

• The kiosk must run existing Windows software.
• The project requires extensive POS or enterprise integration.
• Several specialized peripherals must be connected.
• Peripheral vendors provide Windows-only drivers or SDKs.
• Higher local processing performance is required.
• The kiosk uses large local databases or multiple background services.
• The IT department already manages Windows devices.
• Legacy hardware or software must be retained.
• The project requires greater storage or memory expansion.

Windows is frequently selected for supermarket self-checkout, hotel check-in, financial services, ticketing, healthcare registration, identity verification, and cash-handling projects.

Do Not Select Based Only on Purchase Price

A less expensive mainboard is not economical if it later requires software redevelopment, replacement peripherals, manual maintenance, or repeated field visits.

The correct calculation should include:

• Mainboard and operating-system cost
• Software development
• Peripheral drivers and SDK integration
• Testing
• Remote management
• Power consumption
• Maintenance labor
• Replacement availability
• Expected deployment life

6. Recommended Specification Process

Before confirming an Android or Windows kiosk motherboard, prepare a complete technical requirement list.

Step 1: Confirm the Application

Document:

• Application name and version
• Supported operating systems
• Minimum CPU requirement
• Minimum RAM requirement
• Required storage
• Graphics requirements
• Browser or runtime version
• Database requirements
• Offline operating requirements

Do not rely only on the software’s minimum specification. A kiosk normally needs additional performance headroom for operating-system services, updates, logging, remote support, and future software versions.

Step 2: List Every Peripheral

Create a device table containing:

• Manufacturer
• Model number
• Connection type
• Required driver
• Required SDK
• Power requirement
• Communication protocol
• Operating-system support
• Test status

This process is especially important for projects involving payment terminals, printers, cash modules, passport readers, or biometric devices.

Step 3: Check the Required Ports

Count the actual interfaces needed:

• USB 2.0
• USB 3.x
• RS-232
• RS-485
• Ethernet
• HDMI
• LVDS or eDP
• Audio
• GPIO
• Mini PCIe
• M.2
• SIM card interface

Allow spare ports for maintenance and future expansion. A USB hub can add connectors, but it does not always provide the same stability or power capacity as native motherboard ports.

Step 4: Evaluate Thermal Conditions

Confirm:

• Ambient operating temperature
• Enclosure volume
• Ventilation openings
• Heat sources near the board
• Continuous operating hours
• Fanless or fan-cooled requirement
• Dust exposure
• Installation location

The processor should be tested inside the final kiosk enclosure, not only on an open workbench.

Step 5: Define the Maintenance Method

Determine how technicians will:

• Access BIOS or firmware
• Reinstall the operating system
• Replace storage
• Retrieve logs
• Restart the kiosk
• connect a keyboard or service device
• perform remote diagnostics
• restore the approved system image

La gamme de kiosques services de fabrication de bornes en OEM et ODM can accommodate processor platform selection, internal layout, thermal design, cable routing, peripheral integration, and maintenance-access requirements.

7. Performance and Storage Recommendations

There is no universal kiosk specification. The following ranges are starting points rather than fixed requirements.

Basic Android Kiosk

Suitable for simple information, ordering, or web-based applications:

• Quad-core or octa-core ARM processor
• 2–4 GB RAM
• 16–32 GB storage
• Ethernet and Wi-Fi
• Required USB or serial interfaces

Use more memory and storage when the application contains large media files, offline menus, transaction logs, or several background services.

Advanced Android Kiosk

Suitable for richer interfaces or multiple integrated functions:

• Higher-performance octa-core ARM processor
• 4–8 GB RAM
• 32–128 GB storage
• Gigabit Ethernet where required
• Additional serial or GPIO interfaces
• Hardware watchdog
• Customized firmware

Basic Windows Kiosk

Suitable for browser applications, light POS software, or standard check-in:

• Entry-level Intel processor
• 8 GB RAM
• 128 GB SSD
• Ethernet Gigabit
• Required USB and serial ports

Advanced Windows Kiosk

Suitable for complex POS, computer vision, multi-screen operation, or large databases:

• Intel Core-class processor selected according to workload
• 16 GB or more RAM
• 256 GB or larger SSD
• Multiple display outputs
• Hardware watchdog
• Industrial network and serial interfaces

Avoid selecting an excessive processor purely for marketing value. Unused performance increases cost and heat without improving kiosk reliability.

8. Peripheral Compatibility Checklist

Before mass production, test the complete hardware chain.

Écran tactile

Confirm:

• Touch controller driver
• L’interface USB ou série
• Multi-touch requirement
• Calibration behavior
• Screen rotation
• operation after reboot
• operation after sleep or display power-off

Imprimante

Confirm:

• Operating-system driver or SDK
• USB or serial protocol
• Paper width
• Cutter control
• low-paper reporting
• paper-out reporting
• error recovery
• encoding and language support

Scanner

Confirm:

• USB HID, virtual COM, or SDK mode
• Supported barcode formats
• Prefix and suffix configuration
• focus behavior in the application
• scanning under actual lighting conditions

Terminal de paiement

Confirm:

• Physical dimensions and mounting
• USB, Ethernet, or serial connection
• Payment provider certification
• SDK or middleware
• operating-system compatibility
• network requirements
• cable security
• regional compliance responsibility

A kiosk manufacturer can integrate the physical device and communication hardware, but payment certification, acquiring-bank approval, gateway setup, and transaction-software compliance normally involve the payment provider and solution integrator.

Camera and Identity Devices

Confirm:

• Resolution and frame rate
• USB bandwidth
• driver support
• SDK architecture
• lighting requirements
• privacy policy
• local or cloud processing workload

9. Security Considerations

Both Android and Windows can be deployed securely, but neither platform is secure by default.

Android Security Measures

Recommended controls include:

• Restricted kiosk mode
• Disabled status and navigation bars
• Application auto-launch
• Password-protected settings
• Disabled unauthorized USB access
• Signed firmware and applications
• Secure API communication
• Unique device credentials
• Remote update control
• Data and log cleanup policies

Avoid installing applications from unknown sources or sharing one administrator password across the entire fleet.

Windows Security Measures

Recommended controls include:

• Assigned Access or a dedicated kiosk shell
• Standard user account instead of administrator access
• Application whitelisting
• BitLocker where appropriate
• Controlled Windows Update policies
• Firewall and endpoint protection
• Disabled unnecessary services
• BIOS password
• Restricted boot devices
• Secure remote-support configuration

Payment and personal-data projects may require additional controls defined by the software provider, payment processor, customer IT department, or applicable regulations.

10. Troubleshooting an Android Kiosk Mainboard

The Kiosk Does Not Power On

Vérifier :

1. AC input and power adapter output.
2. Mainboard DC input voltage and polarity.
3. Power-button or auto-power-on wiring.
4. Loose internal connectors.
5. Fuse or power-distribution board status.
6. Visible board damage or abnormal heat.

Do not repeatedly connect power when the voltage or polarity has not been confirmed.

Android Starts but the Kiosk Application Does Not Open

Vérifier :

1. Whether auto-launch is enabled.
2. Application permissions.
3. Application compatibility with the Android version.
4. Storage availability.
5. Network-dependent startup services.
6. Crash logs.
7. Whether the package was changed after firmware configuration.

A USB Device Is Not Detected

Vérifier :

1. The device on another USB port.
2. USB cable and extension length.
3. USB power consumption.
4. Android driver or SDK support.
5. OTG and host-mode configuration.
6. Application permissions.
7. Whether a powered USB hub is required.

The Screen Is Blank but the Mainboard Is Running

Vérifier :

1. LCD power.
2. Backlight power.
3. HDMI, LVDS, or eDP cable.
4. Correct display timing and resolution.
5. Firmware display configuration.
6. Loose or reversed internal display cables.

11. Troubleshooting a Windows Kiosk Mainboard

Windows Does Not Start

Vérifier :

1. Whether the SSD is detected in BIOS.
2. Boot order.
3. Power supply stability.
4. Windows recovery status.
5. Recent update or driver changes.
6. Storage health.
7. Whether the approved system image can be restored.

A Peripheral Disconnects Intermittently

Vérifier :

1. USB cable quality and length.
2. USB power-management settings.
3. Device Manager error messages.
4. Driver version.
5. USB hub power capacity.
6. Grounding and electrical interference.
7. Whether the issue occurs under peak system load.

The Kiosk Becomes Slow Over Time

Vérifier :

1. Available SSD space.
2. Temporary files and application logs.
3. Background update processes.
4. Antivirus scanning.
5. Memory utilization.
6. CPU temperature.
7. Database growth.
8. Unnecessary startup services.

Windows Displays the Desktop Instead of the Kiosk Application

Vérifier :

1. Startup task configuration.
2. Kiosk shell or Assigned Access settings.
3. User account permissions.
4. Application executable path.
5. Whether an update changed the login process.
6. Whether the application closed because of an error.

12. Validation Before Mass Production

A prototype that powers on is not yet ready for commercial deployment.

Complete the following validation stages before approving production:

Functional Test

Verify every application function and peripheral.

Reboot Test

Perform repeated cold starts and software restarts. Confirm that all peripherals reconnect automatically.

Network Recovery Test

Disconnect and restore Ethernet, Wi-Fi, and cellular connections. Confirm that the application recovers without manual intervention.

Power Interruption Test

Interrupt power during idle operation and controlled test transactions. Verify system and database recovery.

Thermal Test

Operate the complete kiosk continuously inside the final enclosure under expected ambient conditions.

Storage Test

Confirm adequate free capacity for the operating system, application, cache, offline content, transaction records, and logs.

Remote-Support Test

Verify monitoring, restart, update, log collection, and remote-access functions before field deployment.

Image Recovery Test

Confirm that technicians can restore the approved Android firmware or Windows system image.

A pilot deployment should be completed before volume production, especially when the project uses new software, payment hardware, or specialized peripherals.

13. Can Android and Windows Be Used in the Same Kiosk Model?

Yes. The same kiosk enclosure can often be engineered to support either an Android board or a Windows industrial PC.

However, changing the computing platform may also require changes to:

• Mainboard mounting brackets
• Power adapters
• Cooling design
• I/O extension cables
• Antenna placement
• Storage mounting
• Operating-system image
• Peripheral drivers
• Application software
• Internal cable routing

The platform should therefore be selected before the final internal structure and wiring harness are approved.

AONKIOSK supports configurable structures and hardware modules across restaurant, retail, payment, check-in, ticketing, and information-terminal projects. Customers can review related application documentation in the Base de connaissances AONKIOSK.

14. Information to Provide When Requesting a Mainboard Configuration

To help the hardware team recommend an appropriate configuration, provide:

1. Kiosk application and use case
2. Required operating system and version
3. Software minimum and recommended specifications
4. Complete peripheral model list
5. Required connection interfaces
6. Screen quantity, size, resolution, and orientation
7. Expected daily operating hours
8. Network method
9. Remote-management requirements
10. Storage and offline-data requirements
11. Ambient temperature and installation environment
12. Target quantity and expected product life
13. Regional certification or customer IT requirements
14. Future expansion plans

Providing this information early reduces compatibility risk and prevents unnecessary changes after prototype production.

Foire aux questions

Is Android Better Than Windows for a Kiosk?

Neither platform is universally better. Android is often better for cost-sensitive, standardized, touch-oriented applications. Windows is usually better for existing desktop software, complex peripheral integration, and higher local processing requirements.

Can Windows Software Run on an Android Kiosk Mainboard?

Not directly. The software must have an Android version, be redeveloped, operate through a browser, or use another compatible delivery method.

Can an Android Kiosk Connect to a Receipt Printer?

Yes, provided the printer offers a compatible Android SDK, driver, protocol, or command interface. Compatibility should be tested with the exact printer model.

Does a Windows Kiosk Need a High-End Processor?

Not always. A high-end processor is unnecessary for a simple browser or ordering application. The processor should be selected according to actual software workload and required performance headroom.

How Much RAM Does a Kiosk Need?

A basic Android application may operate with 2–4 GB, while more complex Android systems may need 4–8 GB. Windows kiosks commonly start at 8 GB, with 16 GB or more used for demanding applications. The software provider’s recommendation should take priority.

Is Consumer Hardware Suitable for a Commercial Kiosk?

Consumer hardware may be acceptable for prototypes or controlled light-duty projects, but commercial deployments normally benefit from stable component availability, suitable operating temperatures, secure mounting, sufficient interfaces, and long-duration reliability testing.

Can the Mainboard Be Upgraded Later?

Sometimes, but an upgrade may affect mounting, power, cooling, operating-system licensing, drivers, and software compatibility. Planning adequate performance headroom during development is normally more economical.

Conclusion

Choosing between an Android and Windows kiosk mainboard should be based on the complete system rather than on the operating system alone.

Android is generally a strong option for compact, energy-efficient, cost-controlled kiosks with standardized touch workflows. Windows is usually more suitable for enterprise software, legacy applications, specialized peripherals, and processing-intensive operations.

Before making the final selection:

• Confirm software compatibility.
• Verify every peripheral model.
• Count all required interfaces.
• Evaluate thermal and power conditions.
• Define security and update policies.
• Test remote maintenance.
• Validate the complete kiosk under real operating conditions.

A well-selected mainboard reduces integration problems, improves uptime, and makes future maintenance more predictable. For customized processor selection, peripheral integration, internal structure, and deployment-ready kiosk hardware, consult AONKIOSK during the early project-design stage.