DocC and SwiftUI error handling

Jeroen Leenarts: Hi, and welcome to episode 68 of our podcast. My name is Sheena Elena's and I've been developing software for over 20 years developing iOS app for over 10 years, and I'm running a Dutch Cocottes for over nine years. If you're an iOS app developer, you should listen to my podcast because it will keep you updated on interesting articles, conferences and events you might not have heard about. In this episode, I'm going to talk about deep linking and URL scheme in iOS, setting up Xcode cloud for automatic build test and distribution, error handling with combined and swift UI, and tips for getting the most out of Doxy. This podcast is a podcasting tutorial podcast. But what this means is that you can stream value for value by using a suitable podcast player. One of these players is foundation app. If you sign up for foundation app and start listening to my podcast with their app, you can enter yourself into a raffle to receive 50,000 sets. That's about $20. Once you signed up with the foundation app and registered my podcast in your player, you should send a DM to at fountain underscore app on Twitter and share the code fountain underscore AF one with them. You should also share your fountain username. This will enter you into a raffle to win 50,000 sets. After about a week a user will be chosen at random and they will receive their they will receive their sets in their fountain wallets. Within the fountain app. I will receive which user has received these sets so that I can do a shout out to them on Twitter. Just for clarity. I'm not receiving any kickback or compensation for anyone who signs up with fountain app through this promotion. I do hope that if you're a crypto enthusiast that you would consider streaming some sets on a value for value basis to my podcast when you're listening to my episodes. So there's a lot of stuff going on right now I'm preparing myself for a presentation at swift heroes. I'm also working on something with try swift that's going to be in March. And next to that. I'm also looking already at a conference in August in the United States. It's going to be in Denver 360 I def definitely check them out on Wednesday evening to Bowditch, we'll do a presentation with Koko Head Snell it's going to be about his new server side swift based CMS called feather. So I'm very much looking forward to that one as well. Next, let's stay on and I will do a Twitter space on Swift UI vs. UI kit. So that will be a good one as well link in the show notes or check us out on Twitter because we have to Twitter space mentioned there. And the other big news item is that next month, we are going to have hopefully our first in person meetup again with Coca Hassanal. And if that all works out, then maybe we will start considering doing a do iOS conference again later this year. So that's a conference organized by a coca Hassanal. So a nonprofit doing a nonprofit conference. And yeah, if there's some developments there, you can be sure that I will share that on my podcast. And I will also make sure that you know what's up there and how we can get involved with this conference. So once we start organizing, otherwise big improvement I had at my home is, is having Fiber Internet connection. So I've been tweaking my Wi Fi setup a little bit. And it was able to improve my internet speeds at my workstation, like three times over, which is great, because now I can just get stuff uploaded to the internet much faster. And yeah, it's now I just noticed everyday that it's just a lot better. And it seems that my wife and my kids are also enjoying the more stable and quicker Wi Fi setup that we now have in our home. So just tweaking it a little bit here and there still, but it's developing nicely on the iOS side of things. Yeah, I'm really trying to dig into signing with Apple and integrating with other cloud providers. And yeah, some really interesting stuff that I'm working on that I'm hopefully able to share more on soon. Biggest items right now, as already mentioned, are those conference participations, and those workshops that I'm working on. So more on that later. So I think it's now important to really dive in on the content of this week. The first article of this week is called deep linking and URL scheme in iOS by Benoit Puskar. So we all know what a URL is and what a URL scheme is, and how it can use deep linking within your app to get somewhere in your app in a convenient way so that your users can find something online click link, and then they end up in your app. For those who are not familiar with this, Benoit has written a nice write up on how you can do deep linking with URL schemes in iOS. It's a nice overview. And it also shares the difference between using a URL scheme, a custom URL scheme, and the universal link. So there's a big difference there. He already did an article on the universal link thing. But that's also linked from this custom URL scheme article that Panama has written. So it's a good overview takes you through the steps that you need to take in Xcode, and what things you need to be aware of when doing a scheme based deep link within your app, and how you can actually get this implemented and going for yourself in your own code base. So nice right up nice overview. The next article is also a article in the sense that it's a nice overview of another technology. It's an article by Martin Fowler bracket, and it's titled Setting Up Xcode cloud for automated builds, tests and distribution. And pretty much this title coverage at all, because in his article modes will take you through the steps that you need to take to make sure that from a GitHub repository, you can create automated builds with Xcode cloud, run tests on them, make sure that those builds are distributed through either test flights, or App Store, and any specific steps that you need to take along the way. So again, if this isn't technology that you want to look at, just have a look at this article, because it gives you a nice rundown of the things that you can do with Xcode clouds, and it helps you get started quickly. And if you're not doing CI CD yet, and you are developing an iOS app, definitely check this out, because it will improve your life significantly, because you just push your code. And then of course, you have to wait a little bit. But then you will get a test flight built available to you on your device or on your testing device, or maybe even to your betta testers. So well worth the read well worth the effort, because it will save you time and issues down the line. So now let's dive into an article that is a little bit more in depth. And that is about code. It's an article by Peter freezer. He also did a YouTube video on this, I think. And the article is titled error handling with combined and swift UI. It's an article that details details how you can handle errors, and expose them to the user. So that a user can actually have an informed decision on the error situation that you're in, so that he can choose what you want to do. Most likely this will be a retry or something along those lines. Error Handling is a very important aspect of the quality of the software that you deliver as software developer. And there's a lot of information out there. And I think that the article, written by Peter is a very concise and good overview of a way that you can deal with errors in a swift UI combine worlds. So the fourth article is by Joseph hack, and it's titled tips for getting the most out of Doxie. Doxie is the new documentation compiler that is available within Xcode. And with this article, Joseph give you some guidelines on how you can improve the inline documentation in your code to make sure that all the output generated by Doxie is more meaningful and more useful to yourself and to people using your codes and API's. So a very concise overview of just those extra steps that you should take if you want to integrate Doxie within your development workflow. And that's it for this week. I'm going to skip the Danny's Monday morning tweet because very much pressed for time and a wants to get this episode out there as quick as possible. So if you have any feedback, any questions, just let me know reach out on Twitter. My DM is always open at Air Force One, and I look forward to any feedback that you might have. Talk to you again next week.