Issue 351

11^th May 2018

Written by Dave Verwer

Comment

So Google had their I/O conference this week and you almost certainly saw the demo of Google Duplex which has been everwhere since it happened. I don’t want to get into it in too much detail here, but my thoughts can be summed up as follows:

1. The assistant should probably identify itself at the start of the call by saying something like “This is the Google Assistant calling on behalf of …” for a few reasons mentioned below.
2. I don’t have a problem with the ethics or concept of the technology for this specific use case. If the business receiving the call doesn’t want this kind of call, they just implement a compatible online booking system and Google will use that instead of calling them. Of course we need to be very careful with how this kind of technology is used in the future, but I don’t think this is the start of the apocalypse just yet.
3. Yes, the tone of the assistant was a little direct/short but I wonder if this is to potentially limit the type of responses that the human will give? If I start a conversation being direct, the tone of the conversation is set by that and the assistant won’t have to try and deal with the more complex responses of a less formal conversation. This would also happen if the assistant identified itself as mentioned in point 1.
4. This is going to go wrong in the real world all the time and I’m really curious love to hear how it copes when that happens. At what point (if any) does it admit that it’s a computer? Also, implementing point 1 would make this a lot easier.

I’m quite sure Google thought about all of these points, at length, but these were my initial takes on it.

Anyway, all of that has very little to do with iOS (or even mobile) development, so let’s move on. As with WWDC, that main keynote is for the general public and it’s the developer keynote that contains the real news for us, and there were several things that stood out to me:

1. Google Assistant has a huge amount of support for third party apps, and so much more announced in this keynote. SiriKit started with a very limited set of possible integrations so that the supported domains are well understood. Google started with a much more open API and are now trying to use the data gathered to better understand the domains. Two very different approaches.

• There’s a comedy naming situation going on with AR and ML frameworks but those technologies were definitely the theme for almost everything that Google talked about in the keynotes. MLKit is also available on iOS as it is part of Firebase which is interesting.
• App slices are really cool and I can see this becoming a much bigger part of how users interact with apps. It feels like iOS app extensions, but again with a different approach.
• Android Studio (and other Linux apps) can now run on Chrome OS. THIS IS THE YEAR OF LINUX ON THE DESKTOP! 😂

Anyway all of that is interesting to look at but we’re here to talk about iOS, so let’s get on with those links.

Dave Verwer

Sponsored Link

Automate the Build-Test-Distribute process for your mobile projects in GitHub. Continuous Integration and Continuous Delivery (CI/CD) are a click away-simply install App Center from the GitHub marketplace or through a notification in the GitHub UI. Get started now.

News

This isn’t hugely surprising news, but if you delayed updating your app to Swift 3 (or 4) then you’ve got a big job on your hands. As always, this will kill a few apps, but in the spirit of Apple’s constant drive to keep the App Store full of maintained apps, I’m sure that they’re well aware of that.

Anything that gets more apps to remove the black borders on the iPhone X is alright by me! 📱

It’s great to see projects such as Kitura and Vapor as well as tools like SwiftLint being officially recognised like this. All of the new forums are on the related projects section of the official Swift forums.

Tools

This is a new tool from Gus Mueller (creator of Acorn) looks very cool. Think of it like Automator for image processing. If you’re regularly processing assets for your apps, you’ll want to check out this public beta.

Continuous Integration, but running on your own machine and without any kind of server side component? Obviously a hosted system is going to have clear advantages for larger teams, but if you’re a solo developer this is certainly worth a look.

Looks like this was added to simctl in Xcode 8.3 but I completely missed it at the time. Thanks to Antoine van der Lee for the reminder that it exists. Looks like support in fastlane is still being worked on, but you can do it manually for now!

Code

It’s great to see this major release from the Vapor team and it’s encouraging to see that it’s been built on top of SwiftNIO as well. The release is pretty well summed in this article so head over there for the full details of exactly what’s new and changed.

Ohhh Core Data, the most controversial of frameworks… I’ve said many times here that I’m not a huge fan of it and I’ve certainly seen it used in many cases where it really isn’t needed. So I’m linking this post, along with this follow up by Marcus Zarra not really as a recommendation, but as a warning that this framework comes with some baggage! 😂

The only thing more controversial than Core Data is date handling, so let’s listen to Richard Turton on that subject to finish off the Code section this week! 😀

Design

Allen Pike with the best explanation I’ve ever read on why your clients should pay for design as part of an app project if it’s not something you do yourself.

Business and Marketing

Interesting, but don’t hold your breath for this to happen on iOS. The App Store is in a very different place to the Microsoft Store.

Sponsored Jobs

Axios needs an iOS engineer to lead the build-out of our first app.

And finally...

This made me laugh so much I was thinking “How do I double ❤️ this on Twitter?” I link to it right here in And Finally… that’s how! 😀