[jvzr]

Hey,

Sorry for the kerfuffle, I mean no harm to you, your reputation & your app. I wish I had screenshotted that. I remember almost reaching out to you on Twitter about it, but thought "hey it's the first one I'll let it slide". I vaguely remember it about the premium subscription, which I found odd. I was not pissed, just surprised. Was it push or local notification? I can't say if I can accurately tell them apart, in my opinion a notification is a notification. It was definitely not in-app as unfortunately I won't get to ride this season so I haven't opened the app in a year :( It was around Christmas or New Year IIRC

Also, I used Slopes as an example because it's the most recent one but frankly it's far from the egregious stuff others pull, especially Apple and the few other developers mentioned in this thread.

[parrots]

No worries, if I was a bad actor you'd be doing the right thing, and as many have already pointed out more often than not it is a bad actor. It's tough (trying to be) of the good guys not abusing the system chasing revenue at all costs, no worries.

I don't use local push notifications for advertising, either. I use them for A) location-based recording reminders created by users and B) notifications when a recording from the Watch is synced to your phone and ready to view, since that can take a minute or so if you're off wifi.

I remember one person reaching out shortly after the iOS 13 launch that I trigged the "Slopes has been using your location in the background" notification when I wasn't recording, which was an error on my side and I fixed that right away.

I did have an email or two go out around Christmas for a giveaway, so I certainly had some email marketing in play then. Maybe Slopes appeared in a notification from your mail client? But Slopes itself did not trigger any notification, push or local, for that campaign.