SwiftUI apps at scale

<blockquote> <blockquote> SwiftUI is fantastic, but not perfect. Some of these imperfections are expected from a nascent 4-year-old framework, but just one creates the roadblock to wider adoption. </blockquote> Today, I’m going to tell the story of my SwiftUI journey at 3 startups; and explain my solution to the critical flaw preventing you from using SwiftUI full-time. <h1>SwiftUI through the years</h1> I’ve been lucky enough to be primarily using SwiftUI since its inception. When the beta dropped in 2019, I was working on a side-project-slash-start-up, Patcher — think Uber for car repairs. Like all naïve engineers on our first rodeo we decided to build everything before getting our first customers. This app had everything. A map, onboarding, profiles, job requests, payments, a repair-in-progress flow, and a second companion app for mechanics. It’s safe to say it was a pretty complex beast, and it’s safe to say SwiftUI was not ready for this in late 2019 and early 2020. Early UIKit inter-op was janky and it was difficult to pass state about. This was a problem when two major features used the Google Maps SDK (MapView didn’t exist!) and the camera. Worst of all, Navigation was entirely broken in SwiftUI 1.0. We eventually ended up using modals for the vast majority of in-app navigation. </blockquote> <a href="https://betterprogramming.pub/swiftui-apps-at-scale-19b7886384f7">Click Here</a>