I'm building a mobile app about asking questions and getting responses.

The responses can be almost immediate (~10-15 seconds) but about half of the time it may take hours for a response to be sent.

Is prompting the user for a question immediately on launch a good idea? Or should both questions and responses be shown? Or maybe something else?

I'm not sure what's the best way to structure this.

  • You could A/B test the effectiveness of both ways you described, I suppose it all really boils down to what you want the user to do. – El Wexicano May 3 '15 at 8:27
  • I'd like to help answer this question, but I'm not entirely sure what the issue is here. Is the primary objective to ask questions, or are users expected to browse existing questions and answers before asking? – Alan Jun 16 '15 at 18:24
  • Thanks for looking @AlanGeorge. This would be a one on one thing. People would ask questions and get responses from a bank of hired professionals. – Sam Washburn Jun 16 '15 at 22:25
  • @AlanGeorge I guess you could say the primary objective is to get an answer. – Sam Washburn Jun 16 '15 at 22:25
  • So what's the issue regarding answer timing? Using a site like this for example, there's no immediate indication on response timing, and it's doing just fine. Could you elaborate on the time aspect? – Alan Jun 17 '15 at 1:19

Your Answer

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

Browse other questions tagged or ask your own question.