3 ms·

That is a very odd take away. The first method is good to have for apps you trust, and requires permission from the user. https://developer.android.com/guide/

by zibzab 6y ago

That is a very odd take away. The first method is good to have for apps you trust, and requires permission from the user. https://developer.android.com/guide/topics/permissions/overview https://developer.android.com/guide/topics/permissions/overv... The second method is what you want with apps you don't yet fully trust or for some other reason don't want to give direct access to your contacts. https://developer.android.com/training/permissions/evaluating https://developer.android.com/training/permissions/evaluatin...

LeifCarrotson 6y ago
Why would an app developer ever think their own app should use the method reserved for untrustworthy apps? All incentives suggest the developer should prevent using the app without full permissions being given (basically force the user into giving permission) and only implement the first method.
- zibzab 6y ago
  Because it would be easier for the users and allow some customization you can't otherwise have? Sure it can be abused, but there are also legit use cases
  - MrDresden 6y ago
    While I get where you are coming from, but giving that option is a design flaw. As Android developers, we should only be given one pipe to consume from. The system should then present the user with the ability to choose if that pipe for this particular application is going to be: "All contacts" / "A subset of contacts" / "No contacts And even better yet just "A subset of the values for a subset of contacts"