Appearance
System Requirements
Use this page to decide whether your target audience can reliably complete the LIQA capture flow. The requirements focus on the client outcome: a smooth mobile experience, enough camera quality for analysis, and enough device performance for real-time guidance.
LIQA is primarily designed to be utilized on modern smartphone (mobile) devices in web environment. The provided information is valid for the moment of writing - Q2 2026.
For clinic, salon, booth, kiosk, and other physical capture setups, see the On-Site Setup guide.
Requirements for Device
Device Requirements
| Requirement | Minimum | Recommended |
|---|---|---|
| Operating system | iOS 16.0+ / Android 12+ | iOS 16.4+ / Android 13+ |
| Camera | Rear-facing and front-facing cameras (rear with autofocus) | Rear-facing and front-facing cameras (rear with autofocus) |
| Camera resolution | 5 MP+ | 8 MP+ |
| WebAssembly | WebAssembly support | WebAssembly SIMD support |
| Graphics | WebGL2 support | WebGL2 support |
You can screen participants' phones from your app before showing LIQA with the checkDeviceCapability() method — it reports whether the device is capable together with the reasons for any failed checks. The screen verifies a phone-class device, the operating system version (iOS at the Recommended 16.4+, Android at the Minimum 12+), the browser features LIQA needs (including WebAssembly SIMD and WebGL2), and — where the browser reports it — an approximate device-memory floor. Pass { camera: true } to also verify on Android that the front camera meets the Minimum 5 MP resolution.
Example devices meeting recommended requirements
| Manufacturer | Recommended devices |
|---|---|
| Apple | iPhone 11 and newer |
| Samsung | Galaxy S21 and newer |
| Samsung | Galaxy A54 and newer |
| Xiaomi | Xiaomi 12 and newer |
| Xiaomi | Redmi Note 12 Pro and newer |
| Pixel 6 and newer |
Desktops
LIQA is not recommended for usage on desktop devices in production because desktop setups often reduce the user success rate and final image quality. There are 2 main reasons:
- Insufficient resolution of majority of embedded web cameras, see limitations.
- Usually stationary positioning of the desktop device limiting the end-user capabilities to improve the light and position.
If your setup allows to overcome the problems mentioned above, it might be possible to effectively use LIQA on desktop. For most desktop products, consider Two-Device Flow so users can start on desktop and capture with a phone camera. Please, check the supported browsers list.
Limitations
Here is a list of the investigated limitations that should be taken into account when choosing LIQA for your target audience.
| Limitation | Explanation |
|---|---|
| Insufficient camera resolution | Camera must have min 5 MP resolution for correct texture representation |
| Required OS version is not supported | iOS 16.0+ and Android 12+ are required. See more details in the list of supported browsers |
| Insufficient RAM amount | iOS-powered devices must have min 3 GB RAM, Android-powered devices min 6 GB RAM for AI execution |
| Insufficient performance | CPU+GPU/NPU must have enough computational resources for AI execution |
Requirements for Environment
Supported browsers
Here is an upper-level overview of supported popular browsers. Use this table when estimating launch coverage for your users or when triaging capture issues reported from a specific browser.
| Browser | Browser Versions | Functionality Status | Known Issues |
|---|---|---|---|
| Safari Mobile | 16.3-16.7, 17.0-17.3 | ✅ Functional | - |
| Safari Mobile | 16.1, 16.2 | ✅ Functional | 🟨 No focus auto-switch feature for back camera |
| Chrome | last 5 versions | ✅ Functional | - |
| Samsung Internet | 21-25 | ✅ Functional | - |
| Firefox | last 5 versions | ✅ Functional | - |
| Edge | last 5 versions | ✅ Functional | - |
Container size
LIQA fills the container it is placed in. For the capture UI to render correctly, give the container a height of at least 600px and the full available width. Embedding LIQA in a smaller container can cause layout issues with the AR guidance and controls.
Need Help?
Did not manage to find the answer on this page? Please, reach the HautAI support team with a specific inquiry.