dwyl / dwyl/learn-user-experience-testing
Budget Test Devices?
- Dominant language
- No language data
- Stars
- 15
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
When user-testing you need a ***reliable device*** that mirrors the "real world" as close as possible
so that user-tests are realistic & valid. There's no point handing people your "iPhone X" or "Pixel 2" because it's **_too_ different** from _their_ personal device and may even _distract_/_detract_ from the test! (_if the device is **much nicer** than theirs it can have a "halo effect" on the UX you are testing..._)
We already have a **Moto G5** as our "Budget Android",
this is good for testing PWAs as it has the latest (_nearly_) "stock" Android.
# Question: Should we have a "Budget" iPhone to UX Test on?
For _example_ we can get an iPhone 5S in _good_ condition for **£63**:
https://www.ebay.co.uk/itm/Apple-iPhone-5s-16GB-Silver-Vodafone-Smartphone-No-Touch-ID/292464915832

I was _alerted_ to this very reasonable price by this promo: https://www.ebay.co.uk/rpp/june-20-party

But when I tried to _use_ it at checkout I got an Error:
```sh
We ran into a problem. Please try again later.
```

I tried _several_ times over the course of the _week_ to use the discount code while attempting to buy the phone but it simply does not work. _Thanks_ for the _reliable_ checkout promo code process, ebay ... 🙄
I think it's pretty cheap at £63 in _any_ case without the 20% discount.
But coming back to the question above: do we _need_ it?
Related to: https://github.com/dwyl/learn-user-experience-testing/issues/1 (_UX Testing on a Tight Budget_)
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.