On 1.09.2010 11:36, Dianne Hackborn wrote:
On Mon, Aug 30, 2010 at 1:37 PM, Brad Gies <[email protected]
<mailto:[email protected]>> wrote:
Now... I also want to use the camera (optional) and vibrate
(optional but most users will want it) so I have to add :
<uses-permission android:name="android.permission.CAMERA" />
<uses-permission android:name="android.permission.VIBRATE" />
Here again, vibrate is a normal permission, so it will not be seen
unless the user wants to dig into it. (And seriously, "makes your
phone vibrate." I think the vast majority of users, if they *do*
explicitly go to see it, will have no trouble figuring out that they
are okay with it.)
What's the point of the VIBRATE permission anyway? I can't imagine a
case where the user decides to not install some application because it
has the VIBRATE permission - so why is there a requirement for apps to
declare this permission?
--
You received this message because you are subscribed to the Google
Groups "Android Developers" 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-developers?hl=en
