I’d like some input from others in the mobile testing area on whether they have opted for real devices on this one and how their testing went?
It seemed like a no brainer, just purchase a new device that supports it and test away. My consideration is that there do not seem to be many with it installed as default and its a dev options kernel level change that likely resets entire device. Kernel and bricking a new phone is my slight concern.
Having had a chat with browserstack, all of their live testing devices are currently 4k only and on live testing you dont get access to try that dev option change approach. There maybe an extra cost option with full access but seems overkill for a couple of health tests.
Emulator approach, this is the path I’ve taken so far, documentation and setup with 16k on android studio was straight forward. The risks themselves is likely a different discussion, 3rd party integrations and webviews was one area I thought could be an issue.
Developer tools that scan and give details on 16k compatibility also seem useful.
I suspect but could be wrong but the playstore checks are likely about an app being configured to support 16k so a scan approach rather than real device approach.
Is anyone else looking at this, I could do with your thoughts and approach from actual testing of this and any finding you feel worth sharing?
Given the fact that there aren’t many 16K display resolution devices out there, I’d say whatever you manage via emulators should be good enough for this.