"getting back" ?
"getting back" ? Seriously, people should stop fantasying about app ops. This was an internal debug tool and I really hope that if we get better permissions, it will look nothing like that. AppOpps only allows you to block permissions after the fact. This won't prevent many apps like facebook to fetch all your contacts as soon as it is installed. An obscure entry in the settings menu will also be left unused by 99.9 % of the users. What we need are granular permission popups 'app x wants to access your calendar/contacts/..., do you agree ?'. -> You can display it right when the app needs it, so the user has a context for this permission and can decide whether he wants to let it access this data or not. -> It is displayed the first time the app tries to access to the private data, so no more mass fetch just after the app is installed. -> You can let the app know that the user refused that permission. That way, instead of displaying no data with no way to know that it is because it has been blocked (and no way to show it to the user), the app can react accordingly.
Posted by on_and_off on May 13, 2015, 8:00 AM
Tags
Related issues
- That's the biggest problem with iOS because Apple can be ordered to block them from the App Store and it would be instantly kill these pr...
- I'm intrigued about the "Trip Planner" being a top-level app.
- This asymmetry is IMO the biggest problem with AI-driven output.
- This is one of the most important objectives in software today.
- At least in Europe - these rouge corporations need to be reined in or just leave the market.
- I was skeptical, but this looks genuinely useful.
Raise real-world problems, find people facing the same issue, and discuss solutions.7,000 issues0 comments
hackernews (SaaS)
That's the biggest problem with iOS because Apple can be ordered to block them from the App Store and it would be instantly kill these pr...
I'm intrigued about the "Trip Planner" being a top-level app.
This asymmetry is IMO the biggest problem with AI-driven output.
This is one of the most important objectives in software today.
At least in Europe - these rouge corporations need to be reined in or just leave the market.
I was skeptical, but this looks genuinely useful.
Why has she gone through so many iPhones?
The biggest problem with Europe is the lack of innovation.
"getting back" ?
"getting back" ? Seriously, people should stop fantasying about app ops. This was an internal debug tool and I really hope that if we get better permissions, it will look nothing like that. AppOpps only allows you to block permissions after the fact. This won't prevent many apps like facebook to fetch all your contacts as soon as it is installed. An obscure entry in the settings menu will also be left unused by 99.9 % of the users. What we need are granular permission popups 'app x wants to access your calendar/contacts/..., do you agree ?'. -> You can display it right when the app needs it, so the user has a context for this permission and can decide whether he wants to let it access this data or not. -> It is displayed the first time the app tries to access to the private data, so no more mass fetch just after the app is installed. -> You can let the app know that the user refused that permission. That way, instead of displaying no data with no way to know that it is because it has been blocked (and no way to show it to the user), the app can react accordingly.
Comments (0)
No comments yet. Start the discussion.