Done properly I can appreciate it, especially on Android where permissions are often nonsensically bundled together. Although I'm never sure when it's crossed the line into scam. Is the permission for getting the user's gamer id really "make phone calls"?!
Not to mention, the pre permission dialog is usually deceptively similar to the Apple one.
(And to be clear, I've never built one of these extra permission prompts, so I'm saying this purely from the perspective of a user.)
Fuck you.
However, it doesn't seem like you are interested in furthering this discussion. Would you have rather I not posted at all?
There are many YC companies listed on this Dark Patterns site, and their founders definitely frequent this form. So far everyone else has been completely mum.
Given that you are on YC's community web site, may I suggest using some tact?
Remember, as an app developer, if a user denies the iOS permissions dialog in your app, you can't EVER show the dialog again -- the user has to manually leave the app and re-enable the permission in the iOS Settings.
Successive calls to the function to ask permission automatically return false for "denied" so it is in the developer's best interest to try to avoid showing the real iOS permission pop up unless the user somehow indicates that they are going to accept the permission (in this case, in the "pre permission" clone dialog).
There's even GitHub projects and CocoaPods for this: https://github.com/yahoo/YMPromptKit
When I used this "trick" (yes, I'm guilty), only a handful of thousands of users actually accepted the soft-prompt and then successively denied the real iOS hard prompt.