0

I need to make a mobile app where the client described the problem, why they need the app, the idea about it, but nothing more. I already understand what kind of features it should contain to solve the problems that the end user experiences without the app (from my experience), but keeping in mind the point, that we need to understand the target user, what would be the best method for this if I can't get to the users? How can I gather this information, so I can validate my assumptions?

0

I would always advocate for talking to actual humans who are going to be the users of this app or service, but if you can't there are online tools for remote testing some basic usability concerns. I personally use usabilityhub for that kind of work. You can try to use social media or something similar to recruit the target audience. If not some research is better than nothing, so talk to anyone you can find; family, friends or people in a coffee shop.

Ask them some questions about what they think this app is for, what do they expect to happen when they do X or Y. What do specific areas mean to them.

| improve this answer | |
  • Thanks for your comment. I plan to go to some friends that are very close to the end users (they work in similar company or would be the kind of group that could use the app). And ask questions about what they think of it, about the features what could be necessary for them etc. I think this would be a good base for gathering info, what do you think? @Calum – istoby Oct 30 '19 at 8:38

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.