purchases-ios VS GRDB.swift

RevenueCat — Hosted backend for in-app purchases and subscriptions (iOS and Android). Free up to $2.5k/mo in tracked revenue.

You got it! Yea, I can't promise everything will work perfectly with all those other platforms, but I will promise that I believe we have the best handling out there. We have 10+ engineers fielding issues from 1000s of developers every month and incrementally improving.

We try to collect as little data as possible, but we use RevenueCat for handling the IAP. We currently use it with anonymous (randomly generated) IDs and don't save additional attribution metadata, so we try to be as privacy-friendly as is possible with this setup.

For IAPs, RevenueCat is one of the simplest setup that exists for React Native. And they have an expo plugin. But having this expo management workflow is the first thing you want to do. https://www.revenuecat.com/

Alternatively you could use RevenueCat which would handle receipt validation for you. I haven’t used it personally but everyone seems to sing its praises.

There are services out there like revenuecat (disclaimer: I have no connection with them, other than being a satisfied customer) that help make these things easier. I recommend looking into them if you’re struggling to wrap your head around it on your own, apple’s documentation can be pretty hard to decipher at times.

I'm Josh Holtz, the author of this article. You might now me from my lead maintainer role of fastlane, creator of Indie Dev Monday, and founder of the new Deep Dish Swift conference ☺️ But I also work at RevenueCat to help developers make more money by making in-app purchases and subscriptions easier!

I have integrated RevenueCat in my previous Startup Fitenium to manage subscriptions, and it was one of the best decisions. Instead of having to integrate both Apple and Google play SDK for subscriptions, with RevenueCat I simply integrated their SDK, which is well documented and much easier to work with. Everything else is magically managed by RevenueCat behind the scenes, to properly handle the payments, users, and analytics.

RevenueCat — Hosted backend for in-app purchases and subscriptions (iOS and Android). Free up to $10k/mo in tracked revenue.

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.