Believe it or not, we still have one more day of techniques for this project before we get into the implementation phase, and I’ve left the hardest stuff to the end.
Today you’re going to look at some of the complexities around how SwiftUI works with UIKit. If you’ve ever used UIKit before these things won’t be too taxing, but if UIKit is new to you then today might hurt almost as much as when you first met closures in Swift. Yes, really.
Stick with it! After today we’ll start putting all these concepts into action, so you’re really close to the fun part. Take your inspiration from the postage stamp – as the writer Josh Billings once quipped, “its usefulness consists in the ability to stick to one thing until it gets there.“
Today you have just two topics to work through, in which you’ll learn about coordinators, delegates,
@objc, selectors, and other things that go bump in the night.
I’d love to hear what you think of these APIs now that you’ve had some time with SwiftUI, whether or not you’ve used UIKit before. Send me a tweet!
If you use Twitter, the button below will prepare a tweet saying you completed today, along with a celebratory graphic, the URL to this page, and the challenge hashtag. Don't worry – it won't be sent until you confirm on Twitter!
Need help? Tweet me @twostraws!
SPONSORED In-app subscriptions are a pain to implement, hard to test, and full of edge cases. RevenueCat makes it straightforward and reliable so you can get back to building your app. Oh, and it's free if your app makes less than $10k/mo.
Link copied to your pasteboard.