Hi,
Regarding "Can it made redundant..through automatic application
introspection.."
It can be done, check out http://android-permissions.org/
"A static analysis tool and permission map for identifying permission
use in Android applications"
By the way, by saying that it can be done I'm not suggesting that this
tool will do the work :)
/Yaron
--
Yaron Reinharts
Smart Drive Applications
http://www.poncho.co.il/gateaway.php
https://market.android.com/details?id=com.poncho.gsm.gate.activities
On 02/23/2012 03:23 PM, Mark Murphy wrote:
On Thu, Feb 23, 2012 at 6:57 AM, Raja Nagendra Kumar
<[email protected]> wrote:
Can Android Run time introspect at run time or during compile time and
prepare such info based on the API used by the application...
No.
Can it made redundant..through automatic application introspection..
No.
Basically looking for why android is designed for explicit permissions
declaration.. when it can be automatically discovered at compiler time
or at run time..
While the need for permissions could be determined at runtime, if you
would prompt the user for the permission then, you wind up with a
Vista-style "The CPU would like to execute an instruction: allow?
deny?" UX, which is not pleasant.
--
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
