App Quality Control #1
Replies: 3 comments 1 reply
-
There should definitely be some kind of manual review when the Also: |
Beta Was this translation helpful? Give feedback.
-
Apps not meeting the requirements should be delisted after extended periods of time. |
Beta Was this translation helpful? Give feedback.
-
Apps requiring special, dangerous, or highly identifiable permissions like Phone, full file access, drawing over apps permission (NOT Picture-in-Picture), SMS, or other ones like ANSWER_PHONE_CALLS should require explanations and shown use-cases for the app reviewer and explanations for the end user. |
Beta Was this translation helpful? Give feedback.
-
Accrescent will have strict quality control for apps uploaded to its repository, mostly automated. This discussion is for suggesting specific app attributes we can check for to ensure we enforce a high level of security for Accrescent apps while still making it feasible for developers to meet our standards. Here is the current list of requirements:
Automatically checked:
Manually reviewed:
MANAGE_EXTERNAL_STORAGE
permissionQUERY_ALL_PACKAGES
permissionThis list will be updated as requirements are tentatively approved, but it is not considered final.
Things to look at:
Are there significant legitimate use cases for it? If so, are we willing to subject this to manual review?
Should any permissions be blacklisted? Are there any that are unnecessary for apps not updating themselves? Are there any deprecated permissions applicable to our current min target SDK(s)? Which permissions are only applicable to system apps?
Beta Was this translation helpful? Give feedback.
All reactions