Jump to content

"Must have" test devices

Karma Octopus

Recommended Posts

At work we are currently looking into what test devices we should acquire to be a strong player in the HTML5 market.


So what I'm wondering is what tablets and smartphones we should focus on getting first, we can always get more units later but right now we want to focus on the "must have" ones.


I would love your feedback on this topic.

Link to comment
Share on other sites

The approach I've gone for is to cover most screen resolutions in the ios market and then also get hold of one or more samsung phones. So something like the following:

* an iPhone / iPod with a 4 inch screen (1136 x 640

* an iPhone / iPod with an iPhone 4 type screen (960 x 640)

* an iPad / iPad mini

* a samsung S3 / S4

you could also consider getting an Android tablet of some description, maybe a Nexus.

Ideally you also need to consider which OS and browser versions you want to support, and ensure that you have access to devices running each of those as well. So for example make sure that some of your ios devices are running iOS 6 and some running iOS 7, likewise different Android versions on each device, and numerous versions of chrome and firefox on each. 

Inevitably you will soon come up against reported bugs on some combination you don't have, but at least you can cover most of the key players with something like the above (IMO).

Link to comment
Share on other sites

Agree with the above, also the Google Nexus devices are pretty solid for testing and don't come with all the bloat that Samsung phones do.


Might also be worth getting a windows mobile device (lumia?) but the market share is pretty tiny. Mobile IE can cause little bugs so it's worth testing if you intend to support it.


It's also worth going to a second hand electronics store and buying a load of old cheap phones. Gotta remember that a lot of people in the 'real world' outside tech are stuck on crappy old phones and don't particularly care about upgrading. If you can get your game working on say, a Galaxy S2 on Android 2.x, you'll know it'll work for a lot of older devices. Older devices are also a lot less forgiving not only performance-wise but in terms of their javascript runtimes, so you can sometimes spot buggy code quicker.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Create New...