3 replaced http://meta.android.stackexchange.com/ with https://android.meta.stackexchange.com/
source | link

There are two ways to generally ask questions of this nature. The Good and the Bad.

How NOT TO ASK questions that may require an app recommendation:

  • "What is the best {category} app?"
  • "List of apps that do {some function}"
    • or, closely related: "Is there something that does {some function}"
  • "What is an alternative to {some app}?"

These questions are not useful to the general community and lead to "fluffy" link-only fodder answers. They really don't solve any problems (the main focus of any site) and it is hard to filter what is good and what isn't when there are 10+ answers all at the same rough vote count.

How TO ASK questions that may require an app recommendation:

First of all: Do your research. Have you thoroughly searched for an answer? Have you searched in the Play Store? Do you even have a real problem you need to solve? And if so, have you attempted to solve the problem yourself? Instead of assuming a solution, ask about your problem instead.

If you did your research and you can describe what the problem is, then here's how to ask:

  • "I have {this problem} that I don't know how to solve. I've already tried {these other solutions}. How do I do this?"
  • "I have {an app} that doesn't work anymore. How do I troubleshoot or fix this?"
    With this type of question, make sure that you are as detailed as possible about the issue(s). If you just say "My app doesn't work!" and that's it, the question will be closed. Also, be open to other apps or solutions that may solve your issue.

Questions like these are problem-based, and lead to useful answers.

See also:

There are two ways to generally ask questions of this nature. The Good and the Bad.

How NOT TO ASK questions that may require an app recommendation:

  • "What is the best {category} app?"
  • "List of apps that do {some function}"
    • or, closely related: "Is there something that does {some function}"
  • "What is an alternative to {some app}?"

These questions are not useful to the general community and lead to "fluffy" link-only fodder answers. They really don't solve any problems (the main focus of any site) and it is hard to filter what is good and what isn't when there are 10+ answers all at the same rough vote count.

How TO ASK questions that may require an app recommendation:

First of all: Do your research. Have you thoroughly searched for an answer? Have you searched in the Play Store? Do you even have a real problem you need to solve? And if so, have you attempted to solve the problem yourself? Instead of assuming a solution, ask about your problem instead.

If you did your research and you can describe what the problem is, then here's how to ask:

  • "I have {this problem} that I don't know how to solve. I've already tried {these other solutions}. How do I do this?"
  • "I have {an app} that doesn't work anymore. How do I troubleshoot or fix this?"
    With this type of question, make sure that you are as detailed as possible about the issue(s). If you just say "My app doesn't work!" and that's it, the question will be closed. Also, be open to other apps or solutions that may solve your issue.

Questions like these are problem-based, and lead to useful answers.

See also:

There are two ways to generally ask questions of this nature. The Good and the Bad.

How NOT TO ASK questions that may require an app recommendation:

  • "What is the best {category} app?"
  • "List of apps that do {some function}"
    • or, closely related: "Is there something that does {some function}"
  • "What is an alternative to {some app}?"

These questions are not useful to the general community and lead to "fluffy" link-only fodder answers. They really don't solve any problems (the main focus of any site) and it is hard to filter what is good and what isn't when there are 10+ answers all at the same rough vote count.

How TO ASK questions that may require an app recommendation:

First of all: Do your research. Have you thoroughly searched for an answer? Have you searched in the Play Store? Do you even have a real problem you need to solve? And if so, have you attempted to solve the problem yourself? Instead of assuming a solution, ask about your problem instead.

If you did your research and you can describe what the problem is, then here's how to ask:

  • "I have {this problem} that I don't know how to solve. I've already tried {these other solutions}. How do I do this?"
  • "I have {an app} that doesn't work anymore. How do I troubleshoot or fix this?"
    With this type of question, make sure that you are as detailed as possible about the issue(s). If you just say "My app doesn't work!" and that's it, the question will be closed. Also, be open to other apps or solutions that may solve your issue.

Questions like these are problem-based, and lead to useful answers.

See also:

2 added 3 characters in body
source | link

There are two ways to generally ask questions of this nature. The Good and the Bad.

How NOT TO ASK questions that may require an app recommendation:

  • "What is the best {category} app?"
  • "List of apps that do {some function}"
    • or, closely related: "Is there something that does {some function}"
  • "What is an alternative to {some app}?"

These questions are not useful to the general community and lead to "fluffy" link-only fodder answers. They really don't solve any problems (the main focus of any site) and it is hard to filter what is good and what isn't when there are 10+ answers all at the same rough vote count.

How TO ASK questions that may require an app recommendation:

First of all: Do your research. Have you thoroughly searched for an answer? Have you searched in the Play Store? Do you even have a real problem you need to solve? And if so, have you attempted to solve the problem yourself? Instead of assuming a solution, ask about your problem instead.

If you did your research and you can describe what the problem is, then here's how to ask:

  • "I have {this problem} that I don't know how to solve. I've already tried {these other solutions}. How do I do this?"
  • "I have {an app} that doesn't work anymore. How do I troubleshoot or fix this?"
    With this type of question, make sure that you are as detailed as possible about the issue(s). If you just say "My app doesn't work!" and that's it, the question will be closed. Also, be open to other apps or solutions that may solve your issue.

Questions like these are problem-based, and lead to useful answers.

See also:

There are two ways to generally ask questions of this nature. The Good and the Bad.

How NOT TO ASK questions that may require an app recommendation:

  • "What the best {category} app?"
  • "List of apps that do {some function}"
    • or, closely related: "Is there something that does {some function}"
  • "What is an alternative to {some app}?"

These questions are not useful to the general community and lead to "fluffy" link-only fodder answers. They really don't solve any problems (the main focus of any site) and it is hard to filter what is good and what isn't when there are 10+ answers all at the same rough vote count.

How TO ASK questions that may require an app recommendation:

First of all: Do your research. Have you thoroughly searched for an answer? Have you searched in the Play Store? Do you even have a real problem you need to solve? And if so, have you attempted to solve the problem yourself? Instead of assuming a solution, ask about your problem instead.

If you did your research and you can describe what the problem is, then here's how to ask:

  • "I have {this problem} that I don't know how to solve. I've already tried {these other solutions}. How do I do this?"
  • "I have {an app} that doesn't work anymore. How do I troubleshoot or fix this?"
    With this type of question, make sure that you are as detailed as possible about the issue(s). If you just say "My app doesn't work!" and that's it, the question will be closed. Also, be open to other apps or solutions that may solve your issue.

Questions like these are problem-based, and lead to useful answers.

See also:

There are two ways to generally ask questions of this nature. The Good and the Bad.

How NOT TO ASK questions that may require an app recommendation:

  • "What is the best {category} app?"
  • "List of apps that do {some function}"
    • or, closely related: "Is there something that does {some function}"
  • "What is an alternative to {some app}?"

These questions are not useful to the general community and lead to "fluffy" link-only fodder answers. They really don't solve any problems (the main focus of any site) and it is hard to filter what is good and what isn't when there are 10+ answers all at the same rough vote count.

How TO ASK questions that may require an app recommendation:

First of all: Do your research. Have you thoroughly searched for an answer? Have you searched in the Play Store? Do you even have a real problem you need to solve? And if so, have you attempted to solve the problem yourself? Instead of assuming a solution, ask about your problem instead.

If you did your research and you can describe what the problem is, then here's how to ask:

  • "I have {this problem} that I don't know how to solve. I've already tried {these other solutions}. How do I do this?"
  • "I have {an app} that doesn't work anymore. How do I troubleshoot or fix this?"
    With this type of question, make sure that you are as detailed as possible about the issue(s). If you just say "My app doesn't work!" and that's it, the question will be closed. Also, be open to other apps or solutions that may solve your issue.

Questions like these are problem-based, and lead to useful answers.

See also:

1
source | link

There are two ways to generally ask questions of this nature. The Good and the Bad.

How NOT TO ASK questions that may require an app recommendation:

  • "What the best {category} app?"
  • "List of apps that do {some function}"
    • or, closely related: "Is there something that does {some function}"
  • "What is an alternative to {some app}?"

These questions are not useful to the general community and lead to "fluffy" link-only fodder answers. They really don't solve any problems (the main focus of any site) and it is hard to filter what is good and what isn't when there are 10+ answers all at the same rough vote count.

How TO ASK questions that may require an app recommendation:

First of all: Do your research. Have you thoroughly searched for an answer? Have you searched in the Play Store? Do you even have a real problem you need to solve? And if so, have you attempted to solve the problem yourself? Instead of assuming a solution, ask about your problem instead.

If you did your research and you can describe what the problem is, then here's how to ask:

  • "I have {this problem} that I don't know how to solve. I've already tried {these other solutions}. How do I do this?"
  • "I have {an app} that doesn't work anymore. How do I troubleshoot or fix this?"
    With this type of question, make sure that you are as detailed as possible about the issue(s). If you just say "My app doesn't work!" and that's it, the question will be closed. Also, be open to other apps or solutions that may solve your issue.

Questions like these are problem-based, and lead to useful answers.

See also: