The application developer could specify a reason for each <uses-permission> in the manifest. The Market and the APK installer could then somehow make this information available to the user.
I know the permissions screen is one of the very few don't-touch UIs in Android and should not be watered down with developer provided content. The UI really would've to make sure that users know which information can be trusted and which can't. So this would probably require a new screen just showing the explanations or having the user click on some sort of button to reveal the developer's explanation. Or maybe that's all just too complicated for the average user and we have to stick with explanations in the user guide (which unfortunately user's most of the time won't see before they install). Christoph On Fri, Feb 6, 2009 at 4:00 PM, Nanard <[email protected]> wrote: > > I suppose many application creator, had fun creating great app during > 1 year (for ADC1) on their PC using the emulator. > > And playing with all Android API. > > During this great coding time they didn't really care about > authorizations : they just have to add it in a xml file. > > Once 'real' users, and 'real' phone arrived, well... this popup > informing the user of the required permission arrives, and... not all > application developper though about that ! > > I am in this case. > > I think google should keep this permission check by phone owner, and > that application developer should explain in their User Guide the > reasons why those permissions are required. > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
