Which is arguably a good security practice, reminding the user once in a while what permission they've granted.
That highly limited permission actually makes me more likely to install this.
That highly limited permission actually makes me more likely to install this.
For my Chrome extension[1], a change[2] in the Airbnb URLs that it runs on caused a significant spike in uninstalls[3] just because it probably scared people a bit. Not a huge deal or anything. Just wanted to share my experience with this stuff.
[1] https://chrome.google.com/webstore/detail/airbnb-price-per-n...
[2] https://github.com/davidsawyer/airbnb-price-per-night-correc...
Requesting additional permissions without an explanation accompanying it can cause confusion, users may think that the request is unwarranted, or that there is something wrong with the extension. They may also decline it out of habit, given how extensions are auto-updated during the browser session, and the request seemingly pops out of nowhere.
See the version adoption[0] for one of my extensions, 1.1.0 has requested additional permissions. This may be problematic when you are trying to deliver a critical update that requires new permissions.