You don't need that permission if the user gives their implicit consent by selecting the Documents directory in the browse window. That's why most apps don't even show up in the Privacy Settings at all. Most apps don't need that, because they don't try to access that directory on their own. They only do it when the user selects the directory.
I guess the improvement can be to show the implicit consent in the privacy settings page as well, and have a way to revoke it.
I guess not. Looks like if you choose the Documents directory once, you give your implicit permission to the app until you choose another restricted directory.
That's not what's happening here.
Forget about the first 5 steps. If you install the app and start from step 6, the behaviour will be the same. If the user chooses the Documents folder in the browse window in an app, the app can use the contents of the Documents folder without the need for that permission in the Settings page.
The Privacy settings applies only to access to the Documents folder without the user interaction.
"6. Click on Open from folder and select your Documents folder there. Confirm that works as expected and displays the name and contents of one of the text files in Documents."
It's because in step 6 the user explicitly selected the Documents folder.
The app can access the Documents folder because the user chose that directory in the native file browse dialog during the same run of the app. IMO that's a reasonable trade-off.
In the same county, maybe.
But electricity is a tradable commodity. The electricity price goes up for the neighbouring counties without the tax benefits.
Typically the glucose level in the interstitial fluid takes longer to respond to your food intake, and the GCMs measure that instead of the blood glucose level.
No. I mean the Mail app itself. It can be used like a lite version of Outlook.
The app can be used as a client for standard IMAP/POP mail servers. It also has GMail integrations.
The mail is usually downloaded into local mbox files.
It's not that difficult to build the scanner into the firebase dashboard. Ask the developer to provide their website address, do a basic scanning to find the common vulnerability cases, and warn them.
I guess the improvement can be to show the implicit consent in the privacy settings page as well, and have a way to revoke it.