CoreStore VS GRDB-ORM

It’s not from Apple, but there’s a framework called CoreStore which you might find easier to pick up initially.

CoreStore (though iCloud support is still in the works)

CoreStore works really well for pure Swift models: https://github.com/JohnEstropia/CoreStore/blob/develop/Playground_iOS.playground/Contents.swift

CoreData through CoreStore. Full disclosure: I’m the author of the lib

After years of working, I finally completed Beezle Social, discover local events!

Beezle Social is an app that is ready to be downloaded on the App Store and possibly soon on the Play store as well! With Beezle, you can explore events happening nearby. Check out the website at https://beezleapp.com/. The app can be downloaded at: https://apps.apple.com/us/app/beezle-social/id1661982809. I completed this on my own.

Rust is used at the backend. I did choose Rust because of its safety and speed. I took me awhile to get used to the type-system, but after that, I was amazed by the functionality and ecosystem. It is a joy working with macro's, cargo and code quality of other libraries.

Swift is used at the frontend. Obviously I preferred Swift over Obj-c. I used SwiftUI + UIKit to make the UI. The whole chatting part is done with UIKit because SwiftUI does not support advanced text editing options. I used some hacks in the chatting part to make sure SwiftUI doesn't reload everything all the time when a new message comes in.

AWS is used at the deploying side. I used ECS and Docker to deploy the server and a lot of other services for media, CDN and mailing system.

Beezle used libraries I created: https://github.com/Jasperav/Catalytic and https://github.com/Jasperav/GRDB-ORM. Catalytic is an ORM for the scylla-rust-driver and GRDB-ORM an ORM for GRDB.

I am happy to answer any question! Please download the app, leave a review and ping me if you missing features.

I created GRDB-ORM awhile ago: https://github.com/Jasperav/GRDB-ORM. If you wanna use GRDB, make sure to check out the ORM as well. You won't be able to write quicker code yourself :). Note that the setup may take an hour to figure out, but after that you will never ever touch database entities

GRDB (and with the orm I made, it should be extremly easy to do anything SQL related: https://github.com/Jasperav/GRDB-ORM)

GRDB with https://github.com/Jasperav/GRDB-ORM. I wrote the library. I doubt there is any easier way to manage and use a database since this generates the swift structs and ensures compile time checked queries

I also wrote a SQLite orm but it has GRDB as dependency: https://github.com/Jasperav/GRDB-ORM. Here you just write the .sql file and this library will generate the structs for you with a lot of predefined queries: https://github.com/Jasperav/GRDB-ORM/blob/master/GRDBPerformance/GRDBPerformance/Generated/DbUser.swift. Does your library create queries on runtime with the help of metadata? That would be a performance hit