Re: ebook-reader permissions - no explanation given

Andrew wrote:

Personally, I admit I never understood how Android does permissions.
 To see how other similar apps handled permissions, I arbitrarily installed
  Cool Reader Unlike com.github.axet.bookreader Book Reader, Cool Reader asked for
permissions as it required them (i.e., when I opened an epub using it).
 In the Muntashirakon "Uses Permissions" tab, it looks very different.

The "old" way was that the manifest file listed perms required, and you agreed to them at install-time, except there were some perms that apps got "for free", i think the android version that an app is targetted to can change the perms it needs/gets, there's a lot of history ...
Then runtime perms came along, which offer you the grant/grant-while-running-this-app/deny options, I prefer those.
I think the "new" way means (for example if an e-reader app did need to write annotations back to file) that it would only need to request write permission if a user actually used the annotation feature ...