swift-composable-architecture VS swiftui-introspect

TCA for short. Very scalable, quite promising, quite popular. A decent alternative for MVVM enhanced by the Clean Architecture. You can learn more about it in a Point-Free tutorial and on GitHub.

🙏 Built with SwiftUI and The Composable Architecture (TCA): This isn’t a feature, but I just want to express my gratitude to the creators and maintainers of these two frameworks, which have played a huge part in making me fall in love with iOS development.

Razliciti alternativni frameworci i arhitekture - Recimo, na pamet mi padaju Composable Architecture (https://github.com/pointfreeco/swift-composable-architecture) i RIBs arhitektura (https://github.com/uber/RIBs). Ok, ove arhitekture resavaju neke probleme. Ali da li problemi koje te arhitekture resavaju solidan developer ne moze sam da resi bez vendor locka za kreatore tih arhitektura. Jesu one open-source, ali meni je rizik da se vezujem za bilo sta sto sutra moze da prestane da se odrzava.

I came across this post discussing MVM, MVVM, MVP, and composable architecture.

At a minimum, Composable Architecture, and now Dependencies from Point-Free.

I’ve built a couple of apps with this framework: https://github.com/pointfreeco/swift-composable-architecture

While there are apps that use a Redux-style architecture, the arch is still in its infancy in the community. There are a number of implementations each with their own take on Redux. TCA is probably the one with the most name recognition and documentation.

Learn it if the project at hand requires it. A lot of older, more mature apps will still use UIKit, so it’s likely if you plan to work an iOS developer job that you will need it. But it’s getting to the point where a lot of the forward thinking shops are already starting to integrate SwiftUI. (Me being one of them) which, btw, a lot of people will say SwiftUI isn’t quite there yet, and I mostly disagree. SwiftUI is good for a great many use cases. Yes, there are still pain points, but you can write most of the apps you’d need to write in SwiftUI. And there are great architectural frameworks out there that actually give SwiftUI an opinionated way to structure apps that is testable and maintainable. Check out pointfreeco’s The Composable Architecture (https://github.com/pointfreeco/swift-composable-architecture)

The SwiftUI Introspect package can probably help here. I know what the correct implementation is for NSLayoutManager in macOS, but I haven’t tried it in iOS.

That's inaccurate. It's built on top of UIKit, at least at the moment, or this kind of project would not be possible. https://github.com/siteline/SwiftUI-Introspect

Curious if an iOS version bump has ever led to introspect not working and/or crashing.

You can use Introspect to get the underlying UIScrollView

That’s because refreshable support to ScrollView was added only in iOS16. If you want to have it also for iOS15 you have to access ScrollView‘s underlying UIScrollView and set an UIRefreshControl on it. The Introspect library is helping here.

You need to install Introspect library.

The scroll indicator insets are not exposed to SwiftUI, as far as I know, but you could use something like SwiftUI-Introspect to get access to the underlying UIScrollView and then set the verticalScrollIndicatorInsets

I don’t believe this is possible I’m SwiftUI, but you should be able to do it if you grab the underling UIKit navigation view controller using this library: https://github.com/siteline/SwiftUI-Introspect

You're welcome :) I work and worked with UIKit quite a bit and they look exactly the same and have very similar features - but also from some articles I read a few years back when SwiftUI was introduced and tools like SwiftUI-Introspect.