What happens when UIKit Swift and SwiftUI have a baby? The best of both worlds

Since the announcement of SwiftUI during the 2019 WWDC conference, the community was ever so divided on the core idea which SwiftUI introduced to the table with its declarative nature.

I myself as well as others have yet to accept SwiftUI as the true future of programming, yet most of us have already agreed that the general idea, which SwiftUI represents is in fact how programming evolves (and might even become the new standard).

As years passed by we developed amazing apps which completely changed out lives. We revolutionized the food and product delivery by making it so simple, that anyone can use it (even your grandma can do this!), we made tracking our chores and ToDo’s easier, navigating foreign roads in distant countries has never been simpler and various translator apps removed the borders between people. Now, all that was done by imperative programming — which tells the program how things should happen. This is fun and all but can get very complex at times.

SwiftUI brings declarative programming to the table which means — what should happen. This is fun too, lettings the program handles a lot of logic on its own, while only giving it a set of rules to follow. While great on the outside, this can cause us to lose some control of things.

As I develop apps mainly without a Storyboard (which in my opinion lets me have more control over what’s happening as well as helps me get more control over the UI itself), I