On 8/2/2012 11:37 PM, Justin Anderson wrote:
The reason to use a permission that you're not using NOW is that
if you add the permission later, you're likely to get a pile of
negative reviews and uninstalls as people are forced to re-agree
to permissions and freak out when they realize what it is that
you're NOW asking for.
This has been discussed here before, and the advice given was to
always ask for everything that you might ever need, or suffer
major negative consequences when you do need it. People on the
list have reported this, and I've seen it happen to a half dozen
apps myself. You can't claim it won't happen, because it DOES.
I've seen it many times!
I disagree... I have an app that uses far fewer permissions than most
of my competitors. I have received numerous emails telling me how
much they love my app and that they chose to insall mine over my
competitors because I had less permissions.
You're not actually disagreeing here, but rather you're arguing
something orthogonal: That you should minimize the permissions you might
ever ask for. I agree with that.
But if your first release needs 3 permissions, but you know that version
1.1 will need a fourth, it's better to add all four right away than to
start out by asking for 3 and then adding the fourth on a later release.
Tim
--
You received this message because you are subscribed to the Google Groups "Android
Discuss" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/android-discuss?hl=en.
