react-native-sqlite-storage VS Realm

Hey, I know MySQLite, what about ReactNative support? Well, last commit on official repo was almost two years ago and I really don't like using outdated libraries.

One issue that irked me during Spicebreaker's development was how painful it was to update the SQLite database with my questions. I tried various solutions, including deleting the database before loading it - it seems to work for some people, but definitely did not work under my setup with my simulator or phone. After wasting hours, I decided it's not worth shortening my lifespan further, and settled on renaming the database file each time I update it. Absolutely disgusting.

I have two apps in prod one using https://github.com/andpor/react-native-sqlite-storage and one using https://github.com/realm/realm-js, both offline only, so I guess I can report my experience with those.

In a react-native app we use react-native-sqlite-storage for dealing with sqlite3 both on iOS and Android.

We ended up using https://github.com/andpor/react-native-sqlite-storage + typeorm and are happy with that.

I'm trying to add SQLite tables dynamically in React Native using react-native-sqlite-storage. The names of the tables are specified by the user. Alternative 1 that works for me is to directly create the query like so:

Presumably realm in Element for Android. https://realm.io/ "Realm by MongoDB"

See also https://github.com/vector-im/element-android/issues/1025

Looks really cool, I like to make very minimalistic dependency choices for the web apps I work on. Web Components look interesting and it's great to see frameworks that build upon it and provide features that are currently missing from it.

When I landed on the page I remembered another Realm framework I used a lot long time ago. https://realm.io has the same name and the logo looks very similar too. Not sure if it's a problem, just wanted to share. :)

Realm (Open Source but Sync is SaaS)

Realm is a fast, scalable alternative to SQLite with mobile to cloud data sync that makes building real-time, reactive mobile apps easy.

I would focus on Kotlin instead of Java, there's really no point in sticking to Java at this point. And when it comes to databases, some local ones that are pretty easy to get into are Realm and ObjectBox, SQLite can definitely be a bit overwhelming at the beginning.

So yeah, if you don't have a server with API which will store data for you - you should really look into CoreData and Realm

Try Realm.

Just to add to this, there's also Realm and ObjectBox as alternatives.

There is some crossover between the BaaS of Firebase and what MongoDB Atlas is offering if you are developing using Atlas Sync and Realm. Even so, there is a whole lot more you can find in terms of tutorials and community support for Firebase so it is hard to know how many of the Mongo claims are just future bugs for your project vs what people are currently doing with Firebase.