While I'm sure that buried in the TOS you can be banned at any time for any reason, and the sheer volume of apps they referee makes things difficult to have hum

While I'm sure that buried in the TOS you can be banned at any time for any reason, and the sheer volume of apps they referee makes things difficult to have humans manage. The "right" thing to do here would be to at least provide some sort of substantiation of your assertion that it violates policy. -App is asking for more permissions than it needs -App is violating privacy -App is direct copy of/ mimicking Core OS functionality -App is using non opensource code etc. They obfuscation of the reasons for the ban seem to me to be one of the following 1) laziness 2) malice 3) fear that it would somehow expose the methodology for finding the policy violations and create a cat and mouse game. It seems like mobile development is becoming less and less an attractive platform to spend my cycles. There are basically 2 markets with millions of apps that already implement your idea in some form or fashion that are free or cheap. Meanwhile being a Luddite and writing enterprise code for business has consistently paid more each year I've done it.