> I too think this change is a bad idea and will decrease the user's > experience with my application.
Perhaps, but it'll probably improve the users experience with the phone in general. I'm sure the battery life complaints have reduced G1 sales, and yet my own G1 doesn't seem to have such terrible battery life. If JBQ says their research linked these complaints to specific apps (like Locale) then I believe them. Kill the few to save the many? > Additionally, I don't think the average teenager or grand-mother knows > what any of the fine grain permissions in Android mean and will just > go ahead and allow any app to have the permissions it wants. Some people won't read them, I agree. They might lose. However, this is still a huge upgrade from the current state of desktop computing, where no matter how skilled or careful you are, you are guaranteed to lose because you have no idea or control over what apps do. > Being > somewhat knowledgable, I wonder if the app is using the permission for > the stated purpose or does it do more than it says. I agree that some permissions could be better thought out, the "Prevent phone from sleeping" permission needs to go (and probably can be removed when Android surfaces battery usage information better). The "access internet" permission needs to be split into several permissions IMHO, for instance basic internet access with caveats should be permission free, but internet access over a certain rate or on certain ports (eg smtp) should require permissions. Perhaps a same origin policy could be designed such that internet access to a programs "home" site is free but other sites require a permission. Of course it's not clear how you define home site. After all, what is the point of this permission? Preventing users getting big charges? Saving the net from abuse? I think the use case for this permission needs to be carefully thought out and then better permissions designed. However, I also see that the Android team have a ton of things on their plate, and that currently this permission isn't being abused. Fortunately it's possible to change permissions after the fact - permissions that aren't necessary any more can be silently granted, and permissions that need to be split can be done by making old apps request every new component. The only thing that can't be easily done is add permissions to things that previously didn't require them, this thread shows how painful that is. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
