SYSTEM ONLINE ZYGISK · REZYGISK · KPATCH · A16-A17
← Back to use cases

Test Mobile Apps on Multiple Devices: Physical vs Profile Matrix

Choose each environment by the behavior you need to verify. This page separates physical-device coverage from profile-based checks; for one-phone profile scenarios, see multiple profiles from one phone.

Physical device matrix

Include the real Android versions and device families that matter to your users. Prioritize critical differences in firmware, permissions, WebView, camera, sensors, screen size, and OEM behavior. Use your own devices for daily checks and a device farm when you need additional real models.

When profiles are enough

Use profiles for controlled app logic checks: different identifiers, build fields, model values, location, or network context. Profiles are appropriate for repeatable comparisons on one real phone, but they do not replace real OS and hardware coverage.

A practical split

Test needEnvironmentEvidence
Profile-driven app behaviorSaved profiles on one real phoneProfile name, changed values, repeatable result
Android API and OS behaviorReal devices or suitable emulator imagesActual OS version and image
OEM and hardware behaviorPhysical devices or device farmDevice model, firmware, hardware-specific logs

Related guides

Compare testing environments · OS compatibility checklist · Test without a device farm