If you ever have adventured yourself using
SwifUI you must certainly know how powerful it can be for making it a lot easier to create interactive and reactive UI, but jumping a step forward you can use SwiftUI on multiple platforms and but it’s pretty much obvious you can't wright the same UI rules for all of them.
With that being said, I’ll show you a quick solution to localize yourself inside the code and decide where to put certain rules for each platform you want your app to support.
Many men and women, have struggle to keep their sanity, while working with asyncronous programming, most have wondered beyond reactiveness, and many have failed, many times. The part the succeded, and now lives in the reactive world, perhaps are scared and don't fully understand how the pillars of reactive programming work. And the fallen, but brave developers who were demolished by complexity and framework adoption, find themselves deep in a callback hell.
Sorry about the dramatic introduction, but it was necessary, reactive programming isn't a simple subject and many people, myself included, have struggled with the concept and with frameworks…
So if you're here, you definitely want to use SwiftUI in your current project. Unfortunately the complete migration in some cases, are close to impossible, but maybe SwiftUI can help us spark a little of joy in our day to day ⌘+R, to check out our awesome UI, that we created using view code (because we're cool kids 😎, who likes to build and run our projects 72 times a hour).