> So if you grant someone the permission and they screw you, google will > say:it's your fault. Our Android is secure, it's your problem if you > accepted permission without reading.
The difference between a typical EULA and the permissions screen is enormous. I don't think they are comparable. The problem with letting people selectively enable/disable permissions is that now apps have to handle every possible combination of permissions. Some of those they will actually need to do something useful, so you don't win by letting people toggle them on/off, you just force devs to add their own dialog box showing how to go toggle the permission on. I agree that Android needs a better way to handle optional permissions, and I think prompting at runtime the first time they are requested would provide a good user experience. But this has come up many times and the Android core team don't like it, so, for now let's drop it. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
