On Tue, Jul 31, 2012 at 4:58 PM, dmmh <[email protected]> wrote: > Actually I am writing a similar application, and ran into the platforms > numurous odd and apparently silly limitations. > > While some limitations are probably needed, a lot of features which should > be available to developers are disabled where they were previously were > enabled, or are simply lacking, or blocked/ hidden. > If I, me, the user, wants control over how the device behaves, it should be > my decision to automate it by installing an app, or do it manually from a > settings menu. > If I want to be dictated by my device, I can always switch to Apple... > That has nothing to do with a "denial of service attack against other > applications on the device", it has to do with wanting to have control over > your device.
Of course it doesn't, but I never said you were launching a denial of service attack on other applications, I said it was possible using the same API. > Ask yourself: is it a "denial of service attack" if the user changes the > features the platform blocks in the settings menu? > No, but how many of these features can accurately be reflected and conveyed to the user? Some. > If I download a application knowing it can programmaticaly enable/ disable > NFC, then I must be fully aware that it does just that, arent't I? > No, actually I am not, not with the current way the permissions system > works. > This is because the it is inheritly flawed, and thus unsecure, resulting in > the need to block certain features. > That's right. > All permissions are treated equally when you install the application, > because of this most people won't read the whole permissions list. > "Dangerous" permissions can even be (and are mostly, ironically) on the > lower part of the list. > These should be on top of the list, highlighted even, in red or whatever, so > it catches your attention when you install a dangerous application. > If it catches your attention, you will think twice to install it as a user. > At the same time, you have no choice whether or not to install the app. > And this opens up the way for developers to access features which are needed > and should/ could be opened in the API, when new permissions are created for > currently deemed "dangerous" features, lifting the problem of having to > limit seemingly harmless things like NFC enable/ disable. > that's right.. kris -- 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
