A common piece of advice for app creators is to take a step back to appreciate the product that’s actually in front of you, rather than always looking ahead to what you want to make and how close you are to that vision.
In many cases, resolving to stay with one idea rather than see what’s emerging, and then adapting, leads to overlooked errors and unrealistic expectations.
Without perspective, developers often lose sight of the gap between their mission and their status. The only way to prevent this is to remain in the present, and in the process. Especially when you’ve got money on the line, sometimes you want to rush toward the end zone, without pausing to check if you’re actually checking the marks along the way – in terms of quality assurance, functionality, and design.
Similarly, you can lose sight when you focus too hard on the end goals of app testing.
For example, in science, you start with a hypothesis that you’re setting out to prove, so that you can remain unbiased in your examination of your theory’s weaknesses and strengths. However, when some people reach the app-testing phase of production, they already think they know exactly what to test and how to test for it – without questioning their methodology itself.
This is especially possible with a groundbreaking platform like Eyece – but only because it invites you to tailor your testing to your exact needs, and deliver instructions to the test users you select. Of course, it’s easy to get the best results by doing a series of tests that are more explicit in their vision and aim, as well as some that are more for you to learn if there’s anything you haven’t thought of yet. As with a scientific inquiry, you want to make sure that you aren’t skewing your results in terms of what you tell your testers to do or look out for.
Eyece lets you get as specific, or be as open, as you wish – though we think the best results come from a blend of both.
Sometimes, the best testing results happen by surprise – with organic user discovery.
One way to avoid end-gaming your feedback is to hire real-life testers to explore your app without too much explicit oversight or specific instruction – inviting them to enjoy your product through the process of discovery.
To get great results, you can ask a series of guiding questions rather than telling the user exactly what to do. “What happens when you do XYZ?” will often produce better results than “We’re trying to see if an error message is prompted when users do XYZ.”
You can also point them to different areas to explore, but not tell them what you’re looking for; for example, asking a gamer to explore a new level, without letting them know that it’s the sound experience you’re testing. Rather than say: “Pay attention to the sound levels,” you could ask for notes and see if people report any sound problems. Then, you can see if those complaints come up with more than one user and if they’re recurring on the same type of device. These results are more valuable – and more accurate – than you’ll get describing your goals exactly.
Eyece gives app developers the opportunity to customize tests – but we also invite you to ‘discover’ results simply by letting users ‘discover’ your app on their own.
#apptesting #reallifetesters #endusers #appdevelopers #customizetest #smartdevicetest