I think it might be beneficial to make the wording of the first one more broadly applicable than just "software development questions". Something like:
Questions about writing and publishing Android apps, writing custom ROMs, and other topics that are primarily of concern to developers are off-topic. Consider taking advantage of other resources that may ...
The short answer, of course, is that you can't expect decisions made by humans to be consistent.
The longer answer is that what's off-topic and on-topic is not determined by one user's comment on a question, but by the democratic process of voting to close. On a wider scale, discussion here on meta sets a written policy for what is on- and off-topic, and it'...
tl;dr as long as there is no appropriate close reason, leave them open
I would leave them untouched. There is no real problem with them continuing to exist. One could argue that they will show up as irrelevant search results, and if closed they could be filtered out if the search is made with isclosed:0. But that's the only real argument I can think of.
Usually questions that could fill a whole book as answer are closed as "too broad" on all sites within the SX network. I can't comment on why this hasn't happened on the Security SX example question you gave. The have the same policy about "too broad" as any other site. But as eldarathis pointed out, the two questions are not on the same level regarding ...
Adding onto the second one to cover other recommendation type questions seems beneficial, in my opinion. I would suggest wording along the lines of:
Questions seeking app recommendations, device recommendations, or other purchasing advice are off-topic as they become obsolete quickly. Instead, describe your situation and the specific problem you're trying ...
I fully agree with the question. And checking our closure reasons, there's nothing that matches this case. As I already mentioned in chat: Maybe we should propose an appropriate closure reason on Meta SE; I was thinking about something like "NLR" (no-longer-relevant), as matching the "too localized (in time)" (this term also would avoid the confusion we had ...
The form of words in the site-specific close reason is certainly broad enough:
Questions about writing and publishing Android apps, writing custom ROMs, and other topics that are primarily of concern to developers are off topic
I think this is clear and reasonably unambiguous - or at least, any areas of ambiguity are in areas where the community has ...
This question is about unauthorized copying of apps, or otherwise violating software copyright. For legal reasons, and to support the Android ecosystem, we don't accept questions that facilitate piracy.
We don't get that many piracy questions, but there are occasional ones, so we might as well be ready for them.
Questions on Android Enthusiasts should be asked from a end-user point
of view and within the scope defined in the [help].
Not sure if my english is good enough to sound natural. @Native speakers: Feel free to edit and improve. @All: Your comments are welcome :)
This close reason is designed to let people know not to ask about general phone issues or generic hardware issues, rather than the much broader "something not in scope". We get quite a lot of these questions, and approximately 0.1% of their askers bother to read the help center. A slightly larger number read the close reason, so I'd say it's helpful.
eldarerathis recently split off that section to give it more prominence, which is great. I think you have a fair point about the wording, though. I've added this line:
Creating or modifying custom ROMs is also off-topic.
I think that should be sufficient, but let me know if not.
Shopping questions are off-topic within the whole SX network. This fact and the 'avoid the XY problem' suggestion resulted in the following help text about on- and off-topic questions:
Please note the following topics are expressly off-topic here:
... or "Can you suggest an app that does X?"
So if you make sure that your question is on-...
No question should ever be closed as "too localized" because of the question stats alone (view count/answers/age/...), as it only solves a cosmetic problem (low accepted answer ratio on Android Enthusiasts) and does not provide any benefit.
Instead only the content of a question should be used as reason to close a question as "too localized" (e.g. because ...
I've re-opened it. I don't think one person verifying that they can see the buttons is enough to say that no one else will be unable to see them, like you. I can't think of any reason why this would be happening to you and only you, so I think it passes the "potentially useful to others" metric.
The nature of the question obviously changed due to the ...
I don't think app recommendations should be a separate close reason. We turn away app recommendations for two reasons:
They're usually opinion-based and subjective.
There are usually many apps, any of which might be the best answer for the OP. We end up with one or two recommendations per answer, with no definitive answer.
If the question falls under 1, ...
As you say, there's no particular reason to leave these questions open. At the same time, there doesn't seem to be a compelling reason to close them either.
The risks/costs of leaving them open are:
Users might answer them inappropriately. On the face of it, this seems unlikely: nobody's even likely to add a "me too" or "thanks" answer any more.
I don't think this is the same as rooting questions. Each permission gives access to (a) specific thing(s), there's not a potentially long and complicated answer for each one.
We could organize answers better, but I think splitting it up into different questions just makes it harder to find. I'd rather focus on formatting. For example, we could split ...
As we already do with rooting questions, we will permit "one question per permission", and link to it from What do android application permissions mean? This way we have a double profit:
our "permission index" stays compact
with the time, we might have closer and more detailed information on each permission, easy to find via the links
When we've consensus ...
Since we still had one empty slot and given the fact that I encountered a few of such questions in the last week, I added the following off-topic reason;
Questions which are Android-independent, such as "Does Carrier X have
prepaid plans?", are off-topic. Consider taking advantage of other
that may be appropriate for your question.
I think we should work on a common policy that we all agree on about closing questions as "too localized". A new meta post with different suggestions about when a question is obviously of no use would surely help to find reasonable criteria.