swift-composable-architecture VS GRDB.swift

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)

I'm using GRDB , you can use existing pre-populated sqlite DB file. https://github.com/groue/GRDB.swift/wiki/Performance .

Not quite exactly sure what you mean but if its a .sqlite3 file then you can use it with this easy to use library https://github.com/groue/GRDB.swift

The 3rd party library I use GRDB SwiftyUserDefaults Kingfisher SwiftDate Popovers

The other thing is that it could be an overkill for your app if you just need to basically "store an array of 100 objects". Then you could probably consider other solutions like SQLite (with wrappers like GRDB) or plain JSON files.

https://github.com/groue/GRDB.swift#readme https://github.com/groue/GRDB.swift/tree/master/Documentation https://swiftpackageindex.com/groue/grdb.swift/documentation/grdb/

https://github.com/groue/GRDB.swift/blob/master/Documentation/AssociationsBasics.md might be interesting to look at for how it handles relationships between entities.

I recently used GRDB.

Check the performance comparison page. GRDB comes with a convenient and ready-made support for Swift Codable that performs quite well. When needed, it is possible to write less convenient but optimized record types that add very little overhead to SQLite, and perform really well.

Hey all. So I just got done developing an app that does visitation tracking. Basically the user creates an account with email, name, password etc.. the info is then saved to a SQLite database (using GRDB) with a table named "User" and then injected into the next view controller and so on... I plan on allowing the user to store their account in icloud in the future.