Expand my Community achievements bar.

Learn about Edge Delivery Services in upcoming GEM session
SOLVED

Best practices for testing

Avatar

Level 3

We will be launching our new app for tablet and phone (Android & iOS) in a couple months, but wanted to ask if there was a good list of devices that the app should be tested on? Obviously we can't go buy every device on the market to test on, so is there a good list of 4-6 devices that will give us a good representation of the entire market? Any other testing pro tips would be welcome! Thanks.

1 Accepted Solution

Avatar

Correct answer by
Employee

In addition to Colin's remarks (which are great and apply to both Android and iOS), here is a bit more detail for Android:

* Variety is the key. Your first few test devices should be very different from each other not only in screen size, but also in manufacturer, Android version, and screen density.

* Definitely include a Samsung phone, not only because they sell well (so your customers will likely have them), but also because Samsung tweaks Android in ways that surface bugs we don't see in other manufacturers.

* Unless you have more specific data on your demographic, pay attention to the general adoption statistics. For example, it's still worth testing on 4.4.

* There were significant changes in the WebView from 4.4 to 5.0, so another reason to test on 4.4 would be if you're using a lot of HTML content.

* Nexus devices are the most loved test devices among our engineering team, because they're cleaner (meaning they don't have the add-ons that so many other manufacturers have). Google devices are also the only devices with which to test previews of latest Android versions (which may or may not be important depending on the target audience of your app).

View solution in original post

2 Replies

Avatar

Level 6

Device choice should be influenced by your expected audience (or maybe you have data on your audience.)

Is an iPad audience a primary user set? Or is it phone based?

Where are most of your users based? The North American market is different than Europe or Asia.

Is your app aimed more at on-the-go consumption (phone) or not-as-mobile (tablet)?

Old device may use old OSs, so what should you support?

HTH

Avatar

Correct answer by
Employee

In addition to Colin's remarks (which are great and apply to both Android and iOS), here is a bit more detail for Android:

* Variety is the key. Your first few test devices should be very different from each other not only in screen size, but also in manufacturer, Android version, and screen density.

* Definitely include a Samsung phone, not only because they sell well (so your customers will likely have them), but also because Samsung tweaks Android in ways that surface bugs we don't see in other manufacturers.

* Unless you have more specific data on your demographic, pay attention to the general adoption statistics. For example, it's still worth testing on 4.4.

* There were significant changes in the WebView from 4.4 to 5.0, so another reason to test on 4.4 would be if you're using a lot of HTML content.

* Nexus devices are the most loved test devices among our engineering team, because they're cleaner (meaning they don't have the add-ons that so many other manufacturers have). Google devices are also the only devices with which to test previews of latest Android versions (which may or may not be important depending on the target audience of your app).