0:00:00Welcome to Under the Radar, a show about independent iOS app development.
0:00:03I'm Marco Arment.
0:00:04And I'm David Smith.
0:00:06Under the Radar is never longer than 30 minutes, so let's get started.
0:00:10So for this week's episode as well as next week's episode, we're going to kind of try
0:00:14and unpack and kind of work through some of the changes and announcements that came out
0:00:20of WWDC.
0:00:21I think we both had sufficient time at this point to kind of digest a lot of what was
0:00:25going on there, in some cases even to dig into things, to try things out, to watch a
0:00:31lot more WWDC session videos.
0:00:33So hopefully we can get a slightly more comprehensive view at this point.
0:00:37And I think it's also kind of nice, rather than doing this kind of thing in real time,
0:00:41is that I think we've had the benefit of the collected wisdom of the community as well
0:00:46to kind of help shepherd this around.
0:00:49So I think we're kind of, I think we're structured.
0:00:51We're going to first start off talking about iOS 12, which is kind of a strange thing,
0:00:56because usually iOS, I would say, is the marquee, the major significant change to operating
0:01:03system at WWDC.
0:01:04But this year, that was not really the case.
0:01:08I mean, there's certainly a lot of changes.
0:01:10There's certainly a lot of things going on more under the hood.
0:01:13But in terms of, there have been years where Apple starts off with these, like, we have
0:01:18seven tentpole features that we're going to bring this year.
0:01:22And this year, they had maybe one or two of those type of that kind of changes.
0:01:28And the rest of the changes are fairly low level.
0:01:30And so at this point, I will recommend a website maintained by Matt Stevens, which includes
0:01:38the old style SDK diffs.
0:01:42So back in the day, before Apple changed the new documentation system, which makes looking
0:01:47for changes completely inscrutable to me, they used to just publish a list of all the
0:01:51method names that had changed and any things that was added.
0:01:54And Matt Stevens still publishes one of those.
0:01:57So just a little plug for that.
0:01:58Yeah, that's awesome.
0:01:59That used to be the very first thing I would open up when getting every beta.
0:02:03At WWDC, it would be sitting in Moscone in the lunch hall.
0:02:08And the very first thing I would do as soon as the site was up was go look at that API
0:02:11to see what of the APIs that I use or might use had brought me presents that year.
0:02:18Yeah, it's amazing.
0:02:20The new version doesn't really work.
0:02:22But anyway, I did the same thing.
0:02:24I always go through that.
0:02:25And now I really appreciate that someone's kind of worked out how to technically just
0:02:29continue to generate these.
0:02:31But looking in there, there's a lot of low level changes and minor changes.
0:02:36Some of them we'll get to later.
0:02:37But in general, it seems like there's not a lot of huge sweeping changes or things that
0:02:45most apps have to do, with the exception of shortcuts, which we'll get to in a minute.
0:02:49But in general, it's mostly just lots of little tweaks, lots of little improvements.
0:02:52And in general, Apple had said their big focus this year was performance.
0:02:56And I think there's even some changes in UIKit to reflect that.
0:02:59There's a great talk about what's new in Cocoa Touch that talks about a whole variety of
0:03:05kind of subtle performance and user experience and responsiveness changes that they've been
0:03:11making in UIKit, some of which we kind of get for free, some of which we have to work
0:03:14for.
0:03:15But in general, there's a bunch of just baseline performance.
0:03:19Things got a little bit better.
0:03:21But if you do nothing, your app's going to be fine kind of things, which in some ways
0:03:25is nice.
0:03:26I like having the opportunity to do that.
0:03:27But at the same time, it's always a little...
0:03:31I think we always just want more changes, then it's probably good for us in some ways,
0:03:36just because it's kind of fun and exciting.
0:03:38But the main marquee change this year is just not much changed.
0:03:42Let's all just make our apps collectively a bit better.
0:03:45Yeah, because every year there could be big flashy new user features, and sometimes there
0:03:51are.
0:03:52Usually there are.
0:03:53But there's also usually stuff under the hood that is something that would not even necessarily
0:03:58make the keynote and might be mentioned very quickly in the State of the Union.
0:04:03But things that just make our lives easier.
0:04:05Things like improvements to UIKit, stuff that most of us use for pretty much any kind of
0:04:10application or special new ways to do basic things like view controllers.
0:04:17When things like child view controllers, different transition types, auto layout, when all those
0:04:20things came out, that was a big deal for everyone.
0:04:23And as time goes on, as iOS has matured, it's gotten more and more specialized.
0:04:28And there are fewer of those better for everyone kind of improvements that come up every year.
0:04:34And over the last couple of years we've had narrower and narrower things like SiriKit
0:04:40Intents, the first version of it, that could only benefit seven different types of apps,
0:04:44stuff like that.
0:04:45And the rate of new things that benefited all of us seems to have definitely gone down.
0:04:50And this year seems like just a continuation of that.
0:04:54I'm a little biased because I have a lot to do with this year's changes, although not
0:04:59even that much on the iOS side, much more on watchOS, which we'll talk about next week.
0:05:02But on the iOS side, there's things like the Siri shortcuts, which are based on the
0:05:10Intents API, so I keep getting those confused.
0:05:12But Siri shortcuts are fairly limited.
0:05:15I wish they could do more than what they actually can do.
0:05:20And I hope they are the beginning of a story and not the end of one, because say next year,
0:05:26if Siri shortcuts could do things like be parameterized the way they already are in
0:05:30the API, but you just can't call them in a parameterized way.
0:05:34You can't say like, make a shortcut to play X where the user can specify any value of
0:05:38X from this dictionary of values.
0:05:41There's nothing like that.
0:05:42You know, they're all like kind of one by one, but hopefully that becomes a bigger thing
0:05:47next year.
0:05:48But I think at least this year we will have the beginning stuff like that.
0:05:51But other than that, there's not that much to do with iOS 12 for most app developers
0:05:56I know, or even for most app developers, period.
0:05:59But as we mentioned last week, I kind of like that at least once.
0:06:04I like that every so often because it gives us a chance to have like the eternal springtime
0:06:09of cleanup, basically, to have like a year where we just make our apps better in ways
0:06:14that aren't just trying to keep up with Apple's treadmill of new stuff and new releases.
0:06:19And what's also nice about iOS 12 is it doesn't seem to break much, with the exception of
0:06:23UI WebView, which is now deprecated, but still works.
0:06:27You know, you should move off of that.
0:06:28But like, with the exception of that, there's not that much that you really have to do for
0:06:33iOS 12.
0:06:34So it does leave a lot of room for people who don't make Apple Watch podcast apps to
0:06:39have a whole summer of freedom.
0:06:41Oh, sure, yeah, because so many of the big changes are increasingly so specialized.
0:06:49Like the changes for the password system, so that you can now have this common shared
0:06:55password management approach thing.
0:06:58That's great if you're one password or one of the other password managers, but if you're
0:07:03not, there's nothing related to that with you.
0:07:05Or you can do navigation in CarPlay now.
0:07:08Well, that's great if you make a navigation player or all the ARKit or core ML changes.
0:07:12They're like, awesome, really cool technology, but it's so specialized rather than being
0:07:19a sweeping change that would affect every app.
0:07:21And so it's like you said, there's so many things that I think both of us are going to
0:07:25have in some ways.
0:07:26There's lots of things for us to work on this summer, but they're becoming so much more
0:07:32isolated and specialized into a particular area, which in many ways, yes, I think is
0:07:36quite nice.
0:07:37I think there's some even improvements to the way they worked on some of the things
0:07:41you can do now in notifications, for example.
0:07:45So many of those changes are the kind of thing that if you don't adopt on day one, the default
0:07:50behavior is going to be fine for you, probably, but you have the ability, should you want,
0:07:55that you can now in notifications, you can have slightly more rich graphics and user
0:07:59interactivity there.
0:08:00You can do slightly more advanced and clever things with threading and for how the way
0:08:04the notifications get grouped, the way the changes work for authorization where you can
0:08:12send quiet notifications now without the user having to authorize them.
0:08:17There's a variety of changes there that are kind of interesting and kind of cool in notifications,
0:08:22but it's a kind of change that you don't have to do anything to start with.
0:08:27It's not one of these things that if you don't update on day one, if you're not ready for
0:08:31iOS 12, whatever it is, usually the third Wednesday in September is usually around when
0:08:37it launches.
0:08:40If you're not ready, it'll be fine.
0:08:42And honestly, in some ways, even with the Siri shortcut stuff, which we can get into
0:08:47a bit more detail, but what I love there is the first simple version of that is just piggybacked
0:08:53right on top of the user activity API, which you may be already using right now if you
0:09:00have a support handoff or any of the other kind of activity-based mechanisms.
0:09:05It's all basically built around the same technology, so you almost kind of get it for free if you've
0:09:14been doing that kind of work anyway.
0:09:16So there's a lot of these things that are just like, "Okay, this is nice.
0:09:19We can make the apps better."
0:09:21And then we have some opportunities in terms of things like Siri shortcuts where if you
0:09:25want to go full into that and you have an application where that makes sense, I think
0:09:30there's a lot of apps where the Siri shortcut stuff really doesn't make much sense beyond
0:09:37using it as kind of a sophisticated launcher, where maybe you want to launch an app into
0:09:42a particular mode or a particular screen, but there may not necessarily be a lot of
0:09:48deep integration for that where it would make sense, but nevertheless, it's a new little
0:09:52sort of interface to plug into.
0:09:56I'm a little skeptical, if I'm honest, though, about Siri shortcuts.
0:09:59I find that I think they'll be useful for a small percentage of the population.
0:10:06They'll be very useful and very well used, but for a large group of my user base, I don't
0:10:12expect them to ever know that they're there or even would find a use for them, even if
0:10:18they did know that they were there.
0:10:19Yeah, I honestly probably won't be using them myself.
0:10:23I see them more as a continuation of workflow and related apps.
0:10:29So apps like Drafts or Editorial and Workflow, these are all iOS power user apps, basically,
0:10:37that allow people to get a lot of work done on iOS or to automate things in various cool
0:10:42ways, save some time.
0:10:44And those are a community worth serving, but not all apps are going to be able to justify
0:10:49having a whole bunch of effort put into that community because it might not be very big
0:10:52for your app.
0:10:54And so to me, supporting Siri shortcuts, I'm treating it-- when I'm trying to think of
0:10:59my time budget for how much time I'm willing to spend on these kinds of features, I treat
0:11:04Siri shortcuts, I think, the same way I would treat things like URL scheme support, but
0:11:08a little bit more than that because it's more visible, or things like continuity support,
0:11:13as you mentioned.
0:11:15That kind of-- or handoff, rather, that kind of thing is worth a little bit of effort.
0:11:20But it's not worth tons of effort because not a lot of people who use most apps are
0:11:24going to actually use those features.
0:11:26The good thing is it seems like-- I haven't actually implemented this API yet.
0:11:30It's next on my to-do list.
0:11:31But it seems like it doesn't actually take that much effort to implement Siri shortcuts.
0:11:37So from that point of view, it should be like a URL scheme where it should be fairly easy
0:11:42to implement.
0:11:43I suppose the only thing that differentiates it and adds to the cost of implementing it
0:11:48is that it needs UI of sorts, right?
0:11:51Or if you want it to be good, it needs a button somewhere on various parts of your interface
0:11:55that says add to Siri, right?
0:11:58There's two types of shortcuts that you can add to your app.
0:12:01So the simple one is just the NSUserActivity-based shortcuts, which are functionally just like
0:12:08what you're doing now.
0:12:09You just need to set a flag to true that says this can be a part of this mechanism.
0:12:13And those are just launching your app with a continue activity into your AppDelegate
0:12:19call.
0:12:20So there's nothing really that you would have to do there.
0:12:23It's only if you want to add the intent-based, more dynamic one that you would need to add
0:12:29the other additional logic to your app.
0:12:32You add an extension handler.
0:12:34You can add a button into your app to add the command phrase to it, but you don't have
0:12:41to do any of those types of things unless you have a kind of -- those typically only
0:12:45make sense in a situation where there's a background handler for the user action that
0:12:52would make sense.
0:12:53So if you're -- in the example they always like to give of ordering a coffee or something
0:12:57like that where you don't have to launch the app in order to do that, that's when I think
0:13:02those other more robust things come into play.
0:13:04But I could imagine, for example, in Overcast that, say, every time I hit play in the app,
0:13:11it had a user activity object that said like -- that indicated that I had just started
0:13:17listening to a podcast.
0:13:19In theory, if I listen to podcasts on a regular basis or in a particular place or whatever,
0:13:25in theory the relevance API or engine that they're using should detect that and say,
0:13:30"Oh, wow, it seems like every morning at 7 o'clock you open your phone and go to Overcast
0:13:38and hit play."
0:13:40And in theory, it should be able to surface that to the user at that point and say, "On
0:13:44my lock screen," or if I pull down into the spotlight area on my phone, that I could have
0:13:52a button that just says "Continue playback," basically, even involving Siri and the voice
0:13:59control part of that, just the Siri as the smart assistant part, which it gets so confusing
0:14:06that they smush everything together and call it Siri, even though I think most people think
0:14:11of Siri as the voice command persona inside of the phone.
0:14:17So that's the side of things that I think for a lot of apps, if that relevance engine
0:14:20is actually really good, and of course people have to have predictable behavior, then those
0:14:26kind of basic, it's just a super advanced launcher, is potentially just a nice little
0:14:31acceleration for people.
0:14:33But the more sophisticated stuff I think is going to be much more isolated in terms of
0:14:38real utility, because I could sort of see the thought, even though you're an example
0:14:43of "You can order a coffee," but really?
0:14:45Is that how someone's going to order a coffee?
0:14:48How many people's order is going to be exactly the same at the same time, and are they going
0:14:53to feel comfortable with doing it that way?
0:14:55I don't know.
0:14:56I'm skeptical, but maybe I'm just skeptical because it's not a thing that's for me.
0:15:05And all features certainly don't need to be for me.
0:15:07So I support them even if I don't think I would use them myself.
0:15:10We are brought to you this week by NS Screencast.
0:15:13NS Screencast features quality video screencasts on Swift, iOS, and Mac development.
0:15:18They cover a wide range of topics from beginner to advanced skill levels.
0:15:22There are currently over 340 episodes and more being added all the time.
0:15:27Every week with NS Screencast you will find a new fantastically produced episode that
0:15:32will help you build and enhance your development skills.
0:15:34On the short videos you can learn a lot over time without a huge time commitment.
0:15:38You'll be able to learn new things even if you've been doing this for a while like us,
0:15:42like in the latest series where you'll be learning about testing iOS applications, which
0:15:46is something that a lot of my friends tell me I need to do.
0:15:50So as well as watching NS Screencast videos on the web, they also have apps for iPhone,
0:15:54iPad, and even Apple TV.
0:15:56So you can watch them whenever and wherever you have time.
0:15:59NS Screencast costs just $18 per month or $168 for the year and it's great for your
0:16:04team too.
0:16:05So take advantage of their team pricing if you can.
0:16:08As listeners of this show, you can get 30% off your first month by signing up at NSScreencast.com/Radar18.
0:16:16And that works whether you opt for the monthly or the annual plan.
0:16:19So invest in yourself or your team.
0:16:22Head to NSScreencast.com/Radar18 now.
0:16:26Thank you so much to NS Screencast for their support of this show.
0:16:30So since iOS 12 is in some ways kind of thin, honestly that's probably about all there
0:16:35is to say about it.
0:16:36We'll have a summer of doing performance tweaks, maybe making some serious shortcuts,
0:16:41maybe enhancing our notifications.
0:16:43But for most people, that will kind of be it.
0:16:46The other thing that I think we should probably talk about is they dropped a mountain of iOS
0:16:52app review guideline changes along with W3C this year.
0:16:57Some of them are just sort of clarifications.
0:16:59Some of them are a bit more specific.
0:17:01But overall, it's certainly something that I think is worth mentioning.
0:17:05I'll have a link in the show notes to a great YouTube resource, which is the App Store
0:17:10Review Guidelines History.com, which is just a website that someone kind of curates the
0:17:14changes and runs nice, pretty diffs of the changes rather than just like a textual diff
0:17:19that try and actually interpret what's changing and highlight some of the important things.
0:17:24So the first place to start I think is there's made a couple of changes to kind of metadata
0:17:28stuff.
0:17:29This is related to what is now App Store Connect, which is going to take me forever to actually
0:17:32switch over from iTunes Connect.
0:17:35Everything is now App Store Connect, which, great, that makes a lot more sense.
0:17:39But anyway, that's the change.
0:17:41But the two metadata changes that I saw in there is that every app must include a privacy
0:17:45policy now.
0:17:47And it must also be available within, linked to from inside of the app.
0:17:53So this is across the board.
0:17:54Previously, I believe this only applied to health and fit health related apps were required
0:17:58to have a privacy policy.
0:18:00Also anything with auto renewing subscriptions.
0:18:01Oh, sure.
0:18:02Okay.
0:18:03So there were two categories now.
0:18:04And I believe now the changes, everybody's got to have one.
0:18:07And this doesn't necessarily come as a surprise with all the GDPR changes and privacy as general
0:18:12as a big theme for Apple.
0:18:14But it's certainly something that I'm sure we're going to see a lot of rejections for
0:18:18this summer as people don't notice that, submit their app, get rejected back from Apple saying
0:18:24that you need a privacy policy.
0:18:25So if you don't have one, you're going to need to write one.
0:18:28And if you do, you just need to make sure that you have a link to it in the app as well
0:18:32as in the metadata field in App Store Connect as well.
0:18:35Yeah.
0:18:36I mean, in this day and age, especially with GDPR, I think at this point, you should all
0:18:40have privacy policies for all the apps and services that you have.
0:18:45If you've never done one before, it sounds intimidating or it sounds like something that
0:18:49only companies can or should do.
0:18:52But not only is the latter point no longer true if it ever was, but you shouldn't look
0:18:58at it as this impossible thing that you have to have a team of lawyers write for you and
0:19:03cost a fortune and everything else.
0:19:05You should consider having a lawyer look at it, but you can write it yourself if you look
0:19:11at other privacy policies, look up the requirements, the current legal requirements and various
0:19:17jurisdictions for what privacy policies have to or should include, and just kind of use
0:19:21other ones as a guide and then look at your app.
0:19:24If you are an indie, you probably know what it does and what it doesn't collect and actually
0:19:31codify.
0:19:32Your privacy policy has to be correct.
0:19:33It is a legally binding document of sorts.
0:19:38You can't lie in it, so you have to tell everything you do.
0:19:41This might give you a reason, if you haven't already audited your stuff for GDPR compliance,
0:19:46this could give you a reason to really look through and figure out, "Is there any information
0:19:50I'm collecting that I don't need or that I can get away without?"
0:19:53Things like that.
0:19:55Just write it as clearly and concisely as you can while hitting all the requirements.
0:20:00A, your users will thank you, and B, it isn't as hard as it sounds.
0:20:07I think it's a good thing in general.
0:20:10I would recommend that developers write it themselves.
0:20:13I think that is better in a lot of ways because it enforces you to understand what it is that
0:20:21you're publicly saying that you're doing.
0:20:24I personally appreciate, as a user, a privacy policy that is clearly written by a person
0:20:31rather than a lawyer because there's a certain degree to which it's that much easier to
0:20:36understand.
0:20:37In many ways, the point of a privacy policy is just to communicate with your user what
0:20:41data you collect and how that data is used.
0:20:45The clearer that communication can be is certainly the better.
0:20:50It doesn't hurt either to look at what other people have in theirs because there might
0:20:53be information that you're inadvertently collecting that you didn't even think about,
0:20:57really.
0:20:58Things like what your web server logs store.
0:21:00Things like user agents or IP addresses.
0:21:03Things like storing cookies in people's computers for logins.
0:21:08When they email you for support, you store that email.
0:21:11Therefore, you have their email address and you can use it to do things like reply to
0:21:16their support email.
0:21:18Stuff that you might not think about.
0:21:19Check out other privacy policies.
0:21:21I give you full permission to copy whatever you want out of mine under the condition that
0:21:25if a lawyer tells you some part of it is horrible or wrong or missing, let me know.
0:21:28That seems like pretty good advice.
0:21:30I think I've certainly learned a few things from your privacy policy.
0:21:32I've always thought it was very well written.
0:21:36Another change related to metadata that is kind of interesting is they've changed the
0:21:40wording around the change log part of our app.
0:21:44Another quote from section 2.3.12 that apps must clearly describe new features and product
0:21:50changes in their what's new text.
0:21:52Simple bug fixes, security updates, and performance improvements may rely on a generic description,
0:21:57but more significant changes must be listed in the notes.
0:21:59Which I think is kind of an interesting change, both in terms of it is encouraging you to
0:22:06be specific to your user.
0:22:07And then also in the back of my mind, I read that as almost like they're trying to curtail
0:22:12A/B testing related types of things.
0:22:16It sounds in some ways as though what they're talking about, they're saying that any significant
0:22:20change must be listed in the what's new as a tool for them to avoid the thing where an
0:22:26app that is, say you're the Twitter app, which as best I understand, does a lot of this,
0:22:31where they roll out different features and different modes and the app is wildly dynamic
0:22:38depending on which all their A/B testing system says the app should behave.
0:22:44I don't know if that's what they're going after this, but either way, I think we've talked
0:22:49many times on this show about your change notes are a rare opportunity for you to communicate
0:22:55with your user, so take advantage of that and write something useful and interesting
0:22:59there.
0:23:00But I think it's interesting to see that Apple is calling that out specifically now as something
0:23:04that they want you to be specific in.
0:23:06Yeah, I mean it's easy to look at this and say like, "Yeah, this is probably aimed at
0:23:11the Twitters and the Facebooks and the Instagrams of the world," but ultimately are they going
0:23:15to really follow this?
0:23:16I doubt it.
0:23:17Are you really going to see a guideline?
0:23:20And obviously the reason for this is Apple wants them to be more accountable and they
0:23:23want a record.
0:23:25Part of Apple clamping down on this kind of stuff is probably Apple recognizing its own
0:23:29GDPR liability and recognizing that their platform enables a bunch of other third-party
0:23:34apps that they don't have control over, and that might become a problem for them down
0:23:38the road if these other apps are shown to be violating people's privacy or anything.
0:23:46Some of the fallout from that could hit Apple on the way.
0:23:49So Apple needs to do things like make sure that they have rules against third-party data
0:23:55giving, stuff like that, but also they want to know that they have a record of what you've
0:23:59changed in your app.
0:24:00And you can't edit the change log fields after the app has been approved.
0:24:05So what this is basically asking for people to do is to give Apple a real record of things
0:24:10that have changed in your app.
0:24:12Not just to say, "But we're always improving our app.
0:24:15Check back every two weeks."
0:24:16Not just to say, "Go to this external URL that we host on our site that Apple doesn't
0:24:20control and we'll tell you what we changed," which no one does.
0:24:25Apple wants a record of that, but again, I see this as being probably largely unenforced
0:24:31against the apps and companies that are the biggest offenders.
0:24:34I can't see how they're going to possibly enforce this.
0:24:36Sure.
0:24:37I mean, I think in general it's probably good to say with these kind of discussions on App
0:24:40Review Guidelines is I think there's a strange tension around enforcement and these kind
0:24:46of rules where I think Apple's intention might certainly be to overall to affect change,
0:24:53maybe not necessarily at a 100% level, that I think enforcement absolutely across every
0:25:00application is probably impossible for both practical, logistical, and then political
0:25:06reasons in terms of the relationship they have with larger apps or those types of situations.
0:25:12But I think their goal, my guess is, there's quite a lot of changes that happened this
0:25:16year and I think my guess is they're trying to course correct the App Store slightly and
0:25:22push it in a slightly different direction, and they don't have to enforce these rules
0:25:26completely or absolutely to affect that correction, that they can make a change that sort of steered
0:25:33the App Store in a slightly different direction just by the way they're both writing it in
0:25:37here, by doing enforcement, especially against egregious cases, and those types of things
0:25:43will start to move the App Store in a slightly different direction.
0:25:47I think that's something that is always just good to keep in mind. The Review Guidelines
0:25:52are always just guidelines, they're not like this very specific black and white text, and
0:25:58usually because there's an element of discretion involved that what I think is a simple bug
0:26:06fix you might think of as a significant change, and that could be just an area of honest agreement,
0:26:13of disagreement, so who knows?
0:26:16Another change that I think is interesting is for advertising-based applications, there's
0:26:20now a requirement that users must be able to see all information that is being used
0:26:26to target the ad that they are being shown, and they need to be able to view that information
0:26:31without leaving the app.
0:26:33That's a big thing.
0:26:34Yeah, it's a pretty big thing, and honestly I'm quite curious to see how this actually
0:26:38rolls out, because as far as I know, none of the major advertising platforms include
0:26:43the ability to do this now, so most people who rely, including myself, I use Google's
0:26:48AdMob platform for my advertising, until they add this to their SDK, then I can't really
0:26:54support it, so I'm not entirely sure if this is going to be something where this requirement
0:26:59isn't enforced right away, or is gradually enforced, or you get a warning, or exactly
0:27:05how this will play out, because it would be quite a catastrophic change if it's starting
0:27:13tomorrow, Apple said, every app that was advertising must do this, because all of the ad-supported
0:27:20apps in the store are reliant on the SDKs that they include in their apps, so until
0:27:24those all get updated, they can't really go there, but nevertheless, I think it is certainly
0:27:28an admirable goal for Apple to try and surface this information to their customers, and I
0:27:35think broadly that seems like a theme, that they're trying to surface privacy and permission-based
0:27:40stuff more specifically and explicitly to customers, so that they're able to make more
0:27:46informed decisions and choices, as well as to hopefully also dissuade people from being
0:27:52too creepy or doing stuff that the users may not like, because it's different if you're
0:28:00able to do it in a more quiet, hidden way than if you're specifically required to show
0:28:06that information to your user.
0:28:09All right, closing out the iOS and general section for the summer, what do you think
0:28:14is the very first thing that you are going to do for iOS this summer?
0:28:20I think the biggest thing for iOS for me is just going to be doing a basic pass of the
0:28:24simple Siri shortcuts stuff.
0:28:26I think that is the default thing that everybody should do this summer, is just go through
0:28:31if there's going to be a few key moments in your application that would make sense to
0:28:36plug into the Siri shortcuts thing.
0:28:39Go ahead and do that.
0:28:40And then I think it's wise probably to see how the fall shakes out before you necessarily
0:28:45go whole hog into the rest of the shortcut stuff.
0:28:48But at the very least, do that.
0:28:49It should take you like half a day to do probably for most people, and then you can just kind
0:28:53of have it in the app, it be available, and if people start loving it, then you can enhance
0:28:58that.
0:28:59And if they don't, you can kind of move on.
0:29:00What about you?
0:29:01Pretty much the same thing.
0:29:03I'm buried in WatchKit right now, which is what we're going to talk about next week,
0:29:06but as soon as I'm done with that, which might be a while, I intend to tackle Siri shortcuts
0:29:12and then start doing things like AirPlay 2 and maybe a visual refresh of some sorts.
0:29:16But we'll see.
0:29:17Those are both large undertakings that are not a high priority right now.
0:29:22So most likely we'll finish WatchKit for a long time.
0:29:26So we'll talk about that next week.
0:29:29And I guess that's it for this week.
0:29:30So tune in next week for our wonderful WatchKit discussion, and we'll talk to you then.
0:29:35Bye.
0:29:35[BLANK_AUDIO]