CommentComment

This week, Apple published what is probably our long-awaited 'privacy-impacting SDK list'. We'll get to that next; please keep reading!

But first, a brief meta-update about the newsletter itself: if you're thinking it's been a long time since Mobile Growth News last showed up in your inbox… you are quite right, and I apologize. With six months of material to select from, this issue will unavoidably be more retrospective than usual.

To me, 'newsletter' implies something that comes a little more frequently than twice a year. So this is my final appearance behind the pen. In future, MGN will be ably curated by my friend and colleague, Adam Landis.

If you already know Adam, it's probably a toss-up whether the thing you remember best is his insightful mobile industry commentary…or his fabulous three-piece suits (he's the only person I know who still wears these on a daily basis). But I am confident his take on the newsletter will be worth your time. I certainly plan to read it.

Thank you for all your attention over the years. And if you've enjoyed any of the last 58 issues, I'd love to hear from you — I read every reply!

Alex Bauer

Spotlight

Apple finally releases the Privacy Impacting SDK list…probably?

WWDC 2023 seems like an age ago, and while privacy wasn't a headline topic this year, Apple ended the event owing the mobile community a number of IOUs on upcoming privacy changes.

They've been slowly knocking those down ever since, but one was still outstanding: a list of 'privacy-impacting SDKs', inclusion of which in an iOS app would trigger new requirements for a Privacy Manifest file and a code signature.

This Thursday, Apple finally published a list of SDKs. But it's quite different from what most observers were expending, so if this is closing the loop on what was promised after WWDC, it raises more questions than it answers:

  • Apple doesn't call this the 'privacy-impacting SDK list', which is a term they've used repeatedly up until now. Why not? A lot of these SDKs probably don't even collect data.
  • What is the criteria for inclusion? Apple says these are 'commonly used in apps on the App Store', but there are 86 SDKs on this list. That's not exactly an obvious number, and only makes sense if the cutoff is based on something like total app downloads (not popularity rank).
  • Where are all the adtech SDKs?
  • If this isn't the privacy-impacting list, then what is it? Something additional, meaning another list of SDKs is still pending?

As usual with Apple, we'll just have to wait and see. Maybe there is something else coming, or maybe this is it and the inconsistencies will only shake out once App Store Review starts to provide enforcement precedent next spring.


That said, all this should end up being little more than a small logistical item for most mobile marketers. So long as you've been setting your team up for the future of measurement (instead of chasing workarounds), and working with reputable vendors (who will be implementing Privacy Manifests and code signatures voluntarily anyway), you should be able to wake up in a few months and not even notice the change.

Interesting Reads


Industry Buzz


Walled Gardens

Privacy & Security

Tools

Tips & Techniques

UX

Data


PodcastPodcast