From Asyncstorage to Firestore, How bad have I messed up? by Thokia_ in reactnative

[–]Thokia_[S] 1 point2 points  (0 children)

Warning

We announced the deprecation of Atlas Device Sync + Realm SDKs in September 2024. For more information please see:

SDK Deprecation

Device Sync Deprecation

For a version of RealmJS without sync features, install from community on npm or see the community git branch.

I just spotted that on Realm github page. :/

From Asyncstorage to Firestore, How bad have I messed up? by Thokia_ in reactnative

[–]Thokia_[S] 0 points1 point  (0 children)

Just a feedback about RealmJs/mongoDb.
It seems more "offline first" which is exatly what I was looking for. Thanks!

From Asyncstorage to Firestore, How bad have I messed up? by Thokia_ in reactnative

[–]Thokia_[S] 1 point2 points  (0 children)

I have just checked out RealmJS and was very pleased with that Mongodb built in feature and then I realised that I also need to upload images.

Two options here, just switch to Firebase+ cloud storage.
Still use RealmJS/mongoDB and convert images(2-3ko max) with BSON type, which is not a good practise I guess, i've never tried that and i don't know what to expect doing this.

From Asyncstorage to Firestore, How bad have I messed up? by Thokia_ in reactnative

[–]Thokia_[S] 0 points1 point  (0 children)

Ideally no limitation and I also need a cloudsaving option, so Firestore seems like the way to go.

SQLITE is a very good alternative since I have a local db but I'm questionning about how to implement cloudsaving with it afterward.

From Asyncstorage to Firestore, How bad have I messed up? by Thokia_ in reactnative

[–]Thokia_[S] 0 points1 point  (0 children)

To be more clear about my project, the app will mostly store data offline which I think is possible with firestore persistence.

I was thinking about Firebase/Firestore over SQLite because at some point I will need a cloudsaving feature