For POS terminals, Android edge devices, and smart retail hardware, sequential speed class is not the metric that determines user experience. A card can be V30-rated and still make an Android POS terminal feel sluggish if its random read/write performance is poor. That is where Application Performance Class comes in.
The SD Association defines two application performance classes for microSD cards: A1 and A2. They specify minimum random read/write IOPS, which directly affect OS boot time, app launch, database transactions, and background logging. This guide compares A1 and A2 for POS, Android edge, and smart retail workloads, and explains how to specify the right card for commercial-grade deployments.
Application Performance Class ratings measure random 4K read/write IOPS and sustained sequential write speed.
| Rating | Random Read IOPS | Random Write IOPS | Sustained Sequential Write | Additional Requirements |
|---|---|---|---|---|
| A1 | 1,500 IOPS | 500 IOPS | 10 MB/s | None beyond basic SD support |
| A2 | 4,000 IOPS | 2,000 IOPS | 10 MB/s | Command queuing and cache functions required in the card |
Key points:
A1 is the entry-level application performance class. It is suitable for light OS tasks, simple logging, and basic retail devices.
A2 roughly triples random read performance and quadruples random write performance versus A1.
A2 cards require command queuing and cache support, and the host device must also support those features to realize the full benefit.
A2 cards are backward compatible with A1 hosts. They will still work, but may not deliver full A2 random performance.
A1 and A2 both guarantee only 10 MB/s sequential write. They do not replace V30 or V60 for 4K video recording. For video-heavy devices, speed class still matters.
POS, Android edge, and smart retail devices rarely write large sequential video files. They perform many small, random reads and writes:
POS terminals: payment authorization, transaction logs, receipt printing, local databases, loyalty programs, inventory sync.
Android edge devices: OS boot, app launch, background services, OTA updates, camera capture, AI inference results, telemetry.
Smart retail: kiosks, digital signage, vending machines, self-checkout, smart cameras, shelf sensors, customer analytics.
These workloads are dominated by small random operations. A card with low random write IOPS can cause:
Slow app launches and UI lag
Delayed payment authorization
Stuttering digital signage
Failed or slow OTA updates
Database corruption under sudden power loss
Poor multi-app performance on Android
For these devices, A2 is usually the better choice when the host supports it. A1 remains adequate for simpler, single-function terminals with light random I/O.
| Characteristic | A1 | A2 | Practical Impact |
|---|---|---|---|
| Random read | 1,500 IOPS | 4,000 IOPS | Faster app launch, OS boot, database reads |
| Random write | 500 IOPS | 2,000 IOPS | Smoother logging, transactions, background writes |
| Sequential write | 10 MB/s | 10 MB/s | Same minimum; not a 4K video guarantee |
| Command queuing | Not required | Required in card | Improves multi-threaded random performance |
| Cache function | Not required | Required in card | Helps absorb burst writes |
| Host support | Broad | Needed for full A2 benefit | A2 card in A1 host may perform like A1 |
| Best fit | Light POS, simple signage | Android POS, edge AI, smart retail kiosks | Match to workload, not just price |
| Application | Recommended Class | Why |
|---|---|---|
| Basic payment-only POS | A1 | Light random I/O; cost-sensitive |
| Android POS with multiple apps | A2 | App responsiveness, database, OTA |
| Handheld POS with camera | A2 | Image capture, scanning, background sync |
| Android edge gateway | A2 | OS boot, container workloads, logging |
| Digital signage, static content | A1 | Mostly sequential reads; light writes |
| Digital signage with analytics | A2 | Random writes from analytics and logs |
| Smart vending machine | A1 or A2 | A2 if telemetry, payments, and camera are combined |
| Self-checkout kiosk | A2 | Transaction database, UI responsiveness |
| Smart retail camera with edge AI | A2 | Event writes, metadata, model updates |
| Fleet/telemetry edge device | A2 | Continuous logging and random database writes |
Rule of thumb:
If the device runs Android, a database, or multiple concurrent apps, specify A2.
If the device only logs small amounts of data or displays static content, A1 may be sufficient.
If the device records 4K video, also check for V30 or V60. A1/A2 does not cover video speed.
A1 and A2 describe performance, not endurance. POS and smart retail devices often run 24/7, write logs continuously, and may lose power without warning. For these deployments, also evaluate:
TBW or P/E cycle endurance: Match total bytes written to daily write volume and expected service life.
Wear leveling: Prevents localized NAND wear under continuous logging.
ECC and bad-block management: Maintains data integrity over years of operation.
Power-loss protection: Critical for POS transactions and database integrity.
Health monitoring: S.M.A.R.T. support allows proactive replacement.
Operating temperature: Commercial-grade cards are typically rated 0°C to 70°C. Verify the device’s internal temperature, especially in fanless kiosks and enclosed retail terminals.
HT Semi commercial-grade microSD cards are rated for 0°C to 70°C and are designed for commercial edge, POS, and retail workloads. For deployments outside that range, additional validation is required.
Use this checklist when specifying A1 or A2 microSD cards:
Profile the workload: Is the device random-I/O heavy or sequential-video heavy?
Check the host: Does the SoC, OS, and driver support A2 command queuing and cache?
Choose A2 for Android and databases: A1 is usually not enough for responsive multi-app Android.
Choose A1 for simple, low-write devices: Do not overpay if the workload is light.
Verify endurance: A1/A2 ratings do not tell you TBW or P/E cycles.
Confirm temperature: Commercial-grade 0°C to 70°C is typical; validate in the enclosure.
Test power loss: POS and retail devices need robust recovery from abrupt shutdown.
Validate in the device: Run boot, app launch, transaction, and OTA tests with the actual card.
Plan replacement: Use health monitoring or replace at 70% of estimated endurance life.