4 ms·

> Turns out you can have that screen but you can't ask a question on that screen or offer a way to dismiss and not get the system dialog. That was news to me si

> Turns out you can have that screen but you can't ask a question on that screen or offer a way to dismiss and not get the system dialog. That was news to me since I had seen countless "Do you want to enable push notifications (yes|no)?" screens in top apps but that rule has changed and no longer allows you to pre-ask. We regularly (multiple times per month) launch new applications in new Apple developer accounts where we present a screen explaining what notifications we send and two buttons, one of which says “Notify me” that triggers the system permissions prompt, and one of which says “Not now” and continues without triggering the system permissions prompt. I’m not sure of the precise difference Apple sees between what you are doing and what we are doing, but this is not a roadblock for us, so perhaps copy that approach more closely and Apple will relax a bit?

joshstrange 4y ago
I'm in the exact same boat as you. It's a whitelabel app that we have launched many times in the past on new Apple Developer accounts but we just randomly got hit with this. Our screen also said "Enable Location" or "Not now" but that wasn't satisfactory. If you look at the "Pre-alert screens" section of this HIG document [0] you will see even your way of doing it isn't allowed but with all things app review, it's a game of roulette if the reviewer notices/cares. I've run into this before where I set up 2 apps within days of each other, different accounts, same core base base, and one gets dinged in review and the other doesn't. I've shipped new apps that didn't have the ability to delete user data well after Apple's deadline and some sneak through ("sneak" but I wasn't trying to sneak, I just forgot to add it to one of my apps, I quickly added it in the next update so I didn't run into a brick wall later if they noticed) and some are caught. [0] https://developer.apple.com/design/human-interface-guidelines/patterns/accessing-private-data#pre-alert-screens https://developer.apple.com/design/human-interface-guideline...
- JimDabell 4y ago
  Apple are definitely inconsistent in how they apply their rules but we’ve never had to tweak this screen as far as I know, across several hundred applications. Maybe it was a one-off? In my experience, Apple don’t really reject things based on the HIG any more. Last time they did for me was back in 2008. If they rejected things based on the HIG, they’d reject almost everything – look at how many applications abuse launch images to show a splash screen, for instance.
- JohnFen 4y ago
  I have to admit my bias up front -- as a user, I hate pre-alert screens in general. But this wording: > Our screen also said "Enable Location" or "Not now" is one of my pet peeves. It's that "not now" that does it for me. The lack of a "No" option, and having a "not now" option, is a big red flag to me. At best, it's just manipulative. At worst, it hints that I'm going to keep getting asked about it over time. Either way, it's removing the ability to say "no", which feels scummy.
  - JimDabell 4y ago
    It’s understandable to feel that way, but it tells the user that this decision doesn’t have to be permanent and makes it easier to say no if they aren’t sure. Remember that if you say no to the system permissions prompt then it can’t be shown again, and this is embedded in a lot of people’s brains – “use it or lose it”. “Not now” is a way of taking the pressure off to stop them getting stuck on that screen, and also pretty idiomatic at this point.
  - MaxikCZ 4y ago
    Exactly this thing triggers me as well. If you have "Not now" option, give us "Not ever" option as well. Or have you ran out of buttons? Same with "No, thanks" button on dialogs that are expected to be denied most of the time (plz subscribe to our newsletter). Sometimes I wish there would be a "No, f*ck off" button next to it, but I feel it's kinda the developers loss for not willing to collect sentiment feedback. Or just give me "No" button, but I am not thankful for being forced to dismiss your nagging.

joshstrange 4y ago

I'm in the exact same boat as you. It's a whitelabel app that we have launched many times in the past on new Apple Developer accounts but we just randomly got hit with this. Our screen also said "Enable Location" or "Not now" but that wasn't satisfactory. If you look at the "Pre-alert screens" section of this HIG document [0] you will see even your way of doing it isn't allowed but with all things app review, it's a game of roulette if the reviewer notices/cares. I've run into this before where I set up 2 apps within days of each other, different accounts, same core base base, and one gets dinged in review and the other doesn't. I've shipped new apps that didn't have the ability to delete user data well after Apple's deadline and some sneak through ("sneak" but I wasn't trying to sneak, I just forgot to add it to one of my apps, I quickly added it in the next update so I didn't run into a brick wall later if they noticed) and some are caught. [0] https://developer.apple.com/design/human-interface-guidelines/patterns/accessing-private-data#pre-alert-screens https://developer.apple.com/design/human-interface-guideline...

JimDabell 4y ago
Apple are definitely inconsistent in how they apply their rules but we’ve never had to tweak this screen as far as I know, across several hundred applications. Maybe it was a one-off? In my experience, Apple don’t really reject things based on the HIG any more. Last time they did for me was back in 2008. If they rejected things based on the HIG, they’d reject almost everything – look at how many applications abuse launch images to show a splash screen, for instance.
JohnFen 4y ago
I have to admit my bias up front -- as a user, I hate pre-alert screens in general. But this wording: > Our screen also said "Enable Location" or "Not now" is one of my pet peeves. It's that "not now" that does it for me. The lack of a "No" option, and having a "not now" option, is a big red flag to me. At best, it's just manipulative. At worst, it hints that I'm going to keep getting asked about it over time. Either way, it's removing the ability to say "no", which feels scummy.
- JimDabell 4y ago
  It’s understandable to feel that way, but it tells the user that this decision doesn’t have to be permanent and makes it easier to say no if they aren’t sure. Remember that if you say no to the system permissions prompt then it can’t be shown again, and this is embedded in a lot of people’s brains – “use it or lose it”. “Not now” is a way of taking the pressure off to stop them getting stuck on that screen, and also pretty idiomatic at this point.
- MaxikCZ 4y ago
  Exactly this thing triggers me as well. If you have "Not now" option, give us "Not ever" option as well. Or have you ran out of buttons? Same with "No, thanks" button on dialogs that are expected to be denied most of the time (plz subscribe to our newsletter). Sometimes I wish there would be a "No, f*ck off" button next to it, but I feel it's kinda the developers loss for not willing to collect sentiment feedback. Or just give me "No" button, but I am not thankful for being forced to dismiss your nagging.