Hacker News new | ask | show | jobs
by ysavir 2438 days ago
* In app library, clear and upfront expectations of what permissions each app uses (as well as an explanation for each permission in the app creator's own words).

* In app library, ability to filter apps by permissions required

...... Specifically, I would want to be able to blacklist permission sets. Eg, search for Keyboard apps, but exclude any apps that require access to my contacts.

* Ability to pay for apps directly through those apps rather than having to go through the smartphone's software author.

...... Totally fine with the software having a default payment option in case I don't want to entrust a certain app with my payment info.

* An interface that lets me see logs of which URLs each app hits and what data it sent.

* An interface that lets me see which servers are sending data to my apps and what data is included.

"App Library" here representing the same sort of app as the Play Store, but looking to disassociate from the term "Store", as that model is not necessary.

Edit: Formatting sub-lists on HN isn't intuitive, apparently

1 comments

This is the one I agree most with so I'll add mine here:

- network connectivity as a separate permission (no reason every app should be allowed network access)

- also, permissions systems everywhere need to get updated for this millennium. Some thoughts:

-- to read my photos is OK as long as they don't have direct network access.

-- but today every app has Internet access by default

-- and just because I trust an app to read my photos doesn't mean I should have to give it permission to delete photos

I would like finer grained control on photo permissions. Particularly I don't necessarily want to grant it access to ALL of my photos.

And in general, I would prefer most apps actually don't have any access to photos, the photo picker could be completely OS level and the app never actually has access.

This is possible and has been for a long time.

https://developer.android.com/guide/topics/providers/documen...

I'd go as far as requiring a statement of intent (soi) from developers requesting network access, describing the frequency and payload content and size. If the code doesn't match the soi then the app is crippled.