Tag Info

Yes. These questions can only be accurately answered by someone who works for the company/app. It clogs Web Apps with a bunch of unanswered questions that turn into tumbleweeds. It's not that your question is getting no attention it's that it's objectively unanswerable unless you built it yourself. WebApps do not have employees from these companies on hand ...

I had added this as a close reason. I am waiting for another moderator to approve the change before it goes live.

I've added it, but requires approval vote from another Moderator.

The reason is now live:

Looking at the most recent questions that have been closed as off-topic, I see: A question on Drupal that probably should have been closed as NARQ An overly broad web development question A web app feature request A question on how easy it would be to install some software (presumably a web app); I think it should have been NARQ Asking for experiences in ...

Because the question is concentrating on the problem to be solved. That the only practical solution is a third-party solution is just an unfortunate side effect. If a native way is found (or added by the app developer) later, an answer to that effect can be added. You might have a look at How do I ask a question that may require recommending a web app? ...

It should not be re-opened as nowadays it's an off-topic question, actually it already has 2 delete votes. If it receive one more, it will be deleted. IMHO the best way to proceed is to post a similar question on Software Recomendations. Related Meta Q&A Should we apply an historical lock to "Alternative to Facebook"? Related Help Articles ...

OK so the help center has been updated. Please note that the following subjects are considered off-topic here: [...] Web application recommendations The offtopic close reason has not yet been updated, will do in a bit..

I'm all for this. I like the idea of being able to recommend something to someone after they've tried something else, but no one ever seemed to follow through with that advice. Even with a decent recommendation question (where they list out their requirements) it would, at best, attract one-line answers (sometimes without even links). As for the wording in ...

I agree with making recommendations off-topic here, because Software Recommendations is now doing great (as many questions per day as webapps) See Software Recommendations's webapp recommendations tag. Like Vidar said, recommendation questions should be migrated there. It is the most logical thing to do. If there is a rule against such migrations, let's ...

I just edited the question to remove the emphasis on web app recommendations, then voted to undelete it.

Yes, the referred question is off-topic on this site. While nowadays it's very common that popular "web applications" have a mobile app, this site's scope doesn't encompasses all the front-ends, it's only about using such web applications. Even on applications like Instagram, WhatsApp and other software as services which their main functionality is ...

Yes, questions about problems that can't be reproduced should be closed as it's very likely that it will not be helpful for anyone. Maybe the closing reason could be "unclear what you are asking" but it's worth to say that Stack Overflow have the a close as of topic that could serve as baseline for a custom closing reason for this situations: This ...

It turns out that there are, in fact, only 3 custom close reasons available. I'm going to propose this as a change. I will certainly entertain opposing viewpoints if it becomes problematic.

I am not entirely sure this close reason is warranted at the moment. I searched for recently closed questions and looked through the first 50 questions. There were approximately 3 questions that had been closed with the reason Not about {site subject}, within the scope defined in the Help Center. On this basis, my opinion is to leave the close reasons as ...

Maybe. If the environment, as described by OP, won't reproduce the result then such Qs should be closed. Usually OPs forget or don't know to mention relevant conditions so something critical is overlooked. Those voting to close should be better informed than OP about what may make all the difference and if they consider OP has provided all details that may ...

No, I don't think it's strictly necessary. Every once in a while we encounter something where the Asker simply misinterpreted something, there was a transient network error, or there was a bug that has since been fixed. Those sorts of questions should be closed. But sometimes not all variables have been accounted for. A browser add-on that the people who ...

I am against this: It takes a lot of time to seek a service corresponding to one's need, so to me it makes sense to ask for a recommendation even if we didn't look carefully at a existing solutions. Often the user's needs can change depending on the existing solutions (e.g. when the user has no idea that such thing existed). Users' feedback on their ...