[Wheaties466]

Personally, I don't even think this is sillyness. yes it should be strict to release apps and you should be accountable and have to explain why you need access to specific permissions on the app stores.

The age of open permissions is should be long over.

I'm sick over overreaching app permissions wasting my battery trying to collect more data on me. If you want more data, provide more value.

[mablopoule]

But it's a camera app. Of course it needs the camera.

It's not overreaching app permission, it's been rejected because the text "The camera will be used to take photographs" wasn't considered a good enough explanation for the permission.

[compsciphd]

how hard is it to say "This is a camera app. Therefore it needs camera permissions in order to take photographs".

[mablopoule]

While I believe that the app store reviewer was being dense on purpose, I agree that this is a better prompt.

[Wheaties466]

If you cant sufficiently explain why your app needs the permissions it does thats on you and the submitter needs to take accountability here. Resubmit with a better explanation.

I get that the app store is strict. But its strict for a reason. Apple or the app store isn't out to get your app or you.

[AndroTux]

All right, mister smarty pants. Let's hear it then: What is a better explanation than "this app need camera permissions, because it takes photos, because it is a fucking camera app"?

[Wheaties466]

Halide is a professional-grade camera application that offers advanced photography features such as manual controls, RAW and ProRAW capture, live histograms, focus peaking, depth capture, macro photography, augmented reality overlays, adaptive gesture controls, exposure tools like zebra stripes, and advanced video recording options. In order to provide these functionalities, these require camera permissions to access and control the device's camera hardware in real-time. Each feature relies on direct interaction with the camera to adjust settings, analyze live image data, and offer immediate feedback, making camera access essential for the app to function as intended and enhance the overall user experience.

moral of the story. spend 3 extra minutes writing something out and save yourself from a headache.

why are we assuming every person that reviews apps knows what ur app does? with submissions like this the explain it like im 5 approach is necessary.

[quesera]

I agree that permission requests should include sufficient context -- but I think that paragraph is way too long for the purpose. People do not read unexpected dialog text. I'd save that for the App Store description, when people are more receptive to detail.

For the permission request, I'd condense your paragraph into a sentence or two.

It's not unusual to download an app, but not launch it immediately. Demanding that the user remember your App Store description is unfair. It's your baby, not theirs.

They might not launch your app for hours or days after downloading. And Apple, reasonably I think, wants developers to try harder to accommodate user's realities.

[mablopoule]

There's strict, and there's kafkaian. It's not as if the reason why a camera app would require the camera is pretty obscure, especially if neither the app nor the permission text changed that much between reviews.

[burnte]

Ok, but this is the worst example of permission overreach, as it's an app to take photos, obviously it needs access to the camera.

[xtracto]

I disagree. The permission should be allowed/denied by the end user. There's no reason why a third party has to have say in that.

[mablopoule]

As far as I understand it, the permission is allowed/denied by the end user.

It's the App Store reviewer that considered the permission prompt to be unclear, and thus rejected the app from the platform.