4 ms·
It's a great idea, but wouldn't this only work for well curated repositories? Basically, it only works if someone is actually enforcing it? Forgive my ignoranc
by csydas 11y ago
It's a great idea, but wouldn't this only work for well curated repositories? Basically, it only works if someone is actually enforcing it?
Forgive my ignorance since I've only had two iPhone freebies as smart phones, but I was under the impression with Android that you could load apps from virtually anywhere and that for the Play store there wasn't much in the way of curation.
As far as the implementation goes, at least, with iOS, if you forbid access even to a key service such as Location Services for an app, the app still launches, it just doesn't do the function requiring the service, and you get a small nag every time you launch the app/try to use the service telling you "X service is disabled for this app, go to Settings to enable". I can't imagine a similar function for Android is that much more difficult.
- dudul 11y agoI have very little experience with mobile apps. I only worked on a few iPhone apps, and on the backend :) I wasn't suggesting this for store admins to review and approve. Simply to force devs to provide informaiton. Maybe we can trust users to curate. The form should be there at submission time, a field per requested permission, devs should be forced to put at least 100 characters for example. If they put garbage, we can trust that the users who care will do the right thing and ignore the app. A lot of apps already try to provide this information on their website, or apps description. Maybe the next step is to embed that in the store itself.