Those idiots killed app ops!

[moosc]

Only 2 supporters your going far

Sent from Bad Azz VZW LG G2 Cyan Tapatalk

 

[darth android]

Only 2 supporters your going far

Sent from Bad Azz VZW LG G2 Cyan Tapatalk

Wow. Such sarcasm. Wow.

I find your lack of faith in android disturbing.

 

[barth2]

I think the permission list is pernicious. Just as what the TSA does is mostly security theater, the permission list is mostly privacy theater.

First, it is all or nothing. How many people are going to turn down an app they want b/c of one request too far, assuming they even read the list. The permission lists are all long and similar sounding, so people are usually just going to skim them and click ok. If it is a trivial app with 20 others just like it, maybe they will look for another app with fewer requirements. But if it's an app they want, they'll click yes.

Second, it's asked up front, when you haven't run the app, don't know if it's worth it, can't readily connect the permissions with its functions (why does it want to access the ____?). The way iOS does it is better. It asks when you are running the app, at the time the app wants to access something. So for example, if you go pick a photo to upload with your forum app and and it asks to access your photos, ok that makes sense. You can selectively grant or deny (eg, say no to push notification). It's still not great because it gets annoying and you're likely to just reflexively click ok or don't allow, and there isn't a central place for permissions. But iOS is pretty restrictive any way so permission handling is not as crucial as android.

 

[mrsmumbles]

I think the permission list is pernicious. Just as what the TSA does is mostly security theater, the permission list is mostly privacy theater.

First, it is all or nothing. How many people are going to turn down an app they want b/c of one request too far, assuming they even read the list. The permission lists are all long and similar sounding, so people are usually just going to skim them and click ok. If it is a trivial app with 20 others just like it, maybe they will look for another app with fewer requirements. But if it's an app they want, they'll click yes.

Second, it's asked up front, when you haven't run the app, don't know if it's worth it, can't readily connect the permissions with its functions (why does it want to access the ____?). The way iOS does it is better. It asks when you are running the app, at the time the app wants to access something. So for example, if you go pick a photo to upload with your forum app and and it asks to access your photos, ok that makes sense. You can selectively grant or deny (eg, say no to push notification). It's still not great because it gets annoying and you're likely to just reflexively click ok or don't allow, and there isn't a central place for permissions. But iOS is pretty restrictive any way so permission handling is not as crucial as android.

I don't quite see what you're saying in the last sentence. Anyway, as aggravated as we are by bizarre Android app permissions, and as amazing as iPhone may be, we're using Android and posting about it in Android forums. Aren't humans strange and contradictory creatures.

Sent from my LG870 via Tapatalk 2

 

[robert_in_la]

It may have been removed because the developer want something enabled for a reason. If the wrong thing is disabled, then it can cause the app to misbehave.

I am sorry but that's nonsense. On my BB I can limit any section of the permission of the apps. Fact is Google should allow the owner of the phone to limit its permissions if they so choice so. Hopefully Google will bring back App Ops.

 

[Golfdriver97]

I am sorry but that's nonsense. On my BB I can limit any section of the permission of the apps. Fact is Google should allow the owner of the phone to limit its permissions if they so choice so. Hopefully Google will bring back App Ops.

How is it nonsense? If someone disables 'Cell State' and then misses phone calls, that is causing the app to misbehave.

 

[Almeuit]

How is it nonsense? If someone disables 'Cell State' and then misses phone calls, that is causing the app to misbehave.

This is true.. If a user disabled things without knowing the consequences they could then be causing more harm than good.

Sent from my T-Mobile Note 3 using AC Forums.

 

[brosko]

Exactly, some apps naturally have to have certain permissions in order to do their required functions. Just common sense

 

[robert_in_la]

How is it nonsense? If someone disables 'Cell State' and then misses phone calls, that is causing the app to misbehave.

Nonsense in the sense that by limiting certain permissions doesn't mean that the app won't work. For example I limit my WhatsApp to only my contacts... the app functions perfectly. When I want to send a photo via WhatsApp I just turn the permission on to allow to share files. Then I can send a photo no problem.

Point I am making is that you as the user should be allowed to limit features... it shouldn't be an "all or nothing" approach that Google has currently.

 

[robert_in_la]

Exactly, some apps naturally have to have certain permissions in order to do their required functions. Just common sense

True... but limiting permissions that they wouldn't need or a feature you as the user wouldn't want to use should be an option. With Android currently its not.

 

[robert_in_la]

This is true.. If a user disabled things without knowing the consequences they could then be causing more harm than good.

Sent from my T-Mobile Note 3 using AC Forums.

Sorry but you can't hand hold someone and if they limit something without knowing they need to take responsibility for it. I personally don't believe my options as a user should be limited in order to protect someone who might, or might not, understand what it means to limit an app(s) permission.

 

[Golfdriver97]

Nonsense in the sense that by limiting certain permissions doesn't mean that the app won't work.

But my example shows a situation where it does. You wouldn't want to miss a phone call, and if that permission is disabled, then it misbehaves.

 

[robert_in_la]

But my example shows a situation where it does. You wouldn't want to miss a phone call, and if that permission is disabled, then it misbehaves.

Point taken... however I don't want my options limited because of someone else might not understanding what it means if they disable "X" permission. I don't need that kind of guiding hand because others can't, or don't, understand what they are doing.

 

[maxburn]

I like the idea of AppOpps and I don't believe we have seen the last of it. I'm hoping we see something ready for release in L.

 

[physioprof]

App developers, OS makers, hardware manufacturers, and network carriers have an extremely strong incentive to not allow users to break stuff. The number of users who are willing and able to use this kind of functionality properly is vanishingly small compared to the number who will break stuff and not understand what they did and then require tech support.

Sent from my Nexus 7 using AC Forums mobile app

 

[maxburn]

Probably why it got pulled. Still it would be nice to have in a developer menu maybe.

 

[mrsmumbles]

Probably why it got pulled. Still it would be nice to have in a developer menu maybe.

It's still on Cyanogen. I'm still not sure how to use it, I should look it up.

 

[maxburn]

It's still on Cyanogen. I'm still not sure how to use it, I should look it up.

Yup, I'm presently using it on Cyanogen. I learned twitter accesses your contacts on a new install about for times before they ask if that's OK in the app. Everything else I use seems to be about what you'd expect.

 

[mrsmumbles]

Yup, I'm presently using it on Cyanogen. I learned twitter accesses your contacts on a new install about for times before they ask if that's OK in the app. Everything else I use seems to be about what you'd expect.

Lol, I should be surprised but Twitter is so aggressive I'm really not.