Mobile Screen Device Resolutions

Video Transcript

Hi, I’m Erin Bailey, Director of Product Management at Kobiton. Back again with more on how to master mobile app testing.

Today’s session covers two important topics. How to prioritize which screen resolutions device models to test, and best practices for making sure your mobile app shines on the most common devices for your users. Let’s start with how to prioritize which screen resolutions to test.

Imagine you’re planning a trip around the world. There are so many amazing countries to visit, but you can’t see them all in one go. The same principle applies to mobile testing. You’ve got finite time and resources, so you have to be strategic. First, check your analytics. This is where your journey starts. Look at your user data to see which devices and screen sizes your audience is actually using. If 40 percent of your customers are on a particular iPhone model, you absolutely want that at the top of your list. Next up, market and regional considerations. Different regions favor different phones. If you have a strong user base in Southeast Asia, you might need to pay special attention to budget-friendly Android devices with 720 by 1600 resolutions. Third, understand the business impact of devices. If a big chunk of your revenue comes from a specific device type, testing that device thoroughly is a no-brainer to prevent costly user drop-offs or car abandonments. Fourth, where is your company in its life cycle? Are you a brand new startup just trying to cover the basics or a more mature company refining your approach?

Younger products might opt for broader coverage first, while established teams can refine based on historical data.

Lastly, do you have foldable and tablet use cases? Folding devices might still be a niche, but if your brand prides itself on innovation, don’t skip them. Tablets often dominate certain industries like healthcare or hospitality. It’s vital to test there if you serve those sectors.

Next, let’s talk about best practices for testing common screen resolutions, because once you’ve chosen which countries to visit, you want to make the most of each trip.

• First, use real devices alongside emulators. Emulators are handy for quick checks, but real device testing uncovers issues you might miss, like color calibration or performance bottlenecks. Platforms like Kobiton give you access to a real device cloud, making it simpler to run tests on actual hardware.
• The second best practice, test portrait and landscape. Your users rotate their screens, especially on foldables and tablets. A layout that looks great in portrait might become awkward or break entirely in landscape.
• Third best practice, check touch targets on devices with high PPI, that’s pixels per inch. Your buttons can appear tiny if not properly scaled. Following platform touch target guidelines like 44 by 44 pixels for iOS or 48 by 48 for Android ensures your app is comfortably tappable.
• The fourth best practice is to monitor performance metrics. High-res displays can drain GPU and CPU resources. Keep an eye on load times, frame rates, and battery usage across device types and screen sizes to maintain a smooth user experience.
• The fifth thing is accessibility testing. Always make sure fonts and buttons adjust for visually impaired users who enlarge text or use screen readers. Tools like accessibility scanner on Android or voiceover on iOS can help you spot problems early.
• And the last best practice I’ll cover is to mind notches, punch holes, and the dynamic island. Make sure critical features like your buy now button aren’t hidden by a camera cutout or another phone specific feature.

Following these prioritization tips and best practices will help you determine the breadth and depth of mobile device models to test for your users to have an amazing app experience.

I hope this helps you refine your mobile app testing strategy. Be sure to check out our blog Common Screen Resolutions for Mobile Testing which is linked in the notes for more insights and to try out a neat widget where you can visually compare screen resolutions of different device models.