That is a terrible reason to request camera access. It is just restating the access request and it should be rejected. Why will photographs be taken? Because it is a camera/photography application and will only take photographs on explicit user request.
But as you just downloaded a camera app that you want to use to take pictures, that description is actually already beyond what could reasonably be expected.
In my job capacity, I give status updates about many unrelated projects.
If I am not explaining full context in a seemingly simple update or question, I will get my hand slapped. And if I tell my boss to “read” it’s going to go worse.
I would have removed the risk of removal by simply prefacing the app is a professional camera app and taking photos is the primary user function.
And not just a lesson for here but also in life: One-liners are fun to say, but people generally don’t like being on the receiving end of them.
Doesn't Apple try to justify their 30% revenue cut by saying they offer unparalleled curation services in their app store?
This is an example of such an unparalleled curation service. The app makers are just lucky enough to be popular (and even promoted by another arm of Apple) or they'd still be out of the app store.
It shouldn't be the developer's burden to ensure that the reviewer is operating above the reading level of a toddler. I am sorry that your boss apparently cannot, but that's not justification for all industries to operate that way. The purpose of a camera app is to take photographs. A user who downloads a camera app probably wants to use it to take photographs. This is something a child can understand. If I have to hold the reviewer's hand and explain what a camera is, I severely question whether that reviewer is qualified to be doing that job.
In my painful and long experience, that mindset just doesn't work if you're trying to become a more effective communicator and save yourself time in the long run.
The text is not for the reviewer, it's for the user of the app.
Imagine the ridiculous level of explanatory humdrum apps would need to conjure if they were to explain themselves to uninterested people pressed for time like that reviewer you described?
Welcome to Halide. This is Halide. Halide needs camera access to take photographs. You can take photos of anything. Anything at all. The only limit is yourself. Anything is possible in Halide. You can do anything with Halide. The infinite is possible in Halide. The unattainable is unknown in Halide. Welcome.
I use it for lots of things that aren’t photography, scanning QR codes, AR uses like seeing how a piece of furniture will look in my house, identifying stars.
How is scanning a QR code photography? Photography is "writing with light"; the key property is that of making a lasting record of a transient handful of photons. When scanning a QR code, the imaging is incidental, but more importantly no record of the "light" is made. If scanning a QR code is photography, so is sitting on the porch reading a book...
Like photometry, and spectroscopy, and videography, and camera obscura, and a hundred other things. A camera is a tool for redirecting photons to create an image of a scene on a 2D plane. So many more things than just creating durable images by recording the spatial distribution of light on a plane (photography) are possible with such a tool.
That is a terrible reason to request camera access. It is just restating the access request and it should be rejected. Why will photographs be taken? Because it is a camera/photography application and will only take photographs on explicit user request.