Realm VS localForage

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.

Not really an answer but have you looked into https://github.com/localForage/localForage

I may not be pointing you in the right direction but, please read about [IndexDB storage](https://developer.mozilla.org/en-US/docs/Web/API/IndexedDB\_API) method and packages like [localForage](https://localforage.github.io/localForage/) that use it under the hood.

LocalForage: this is a wrapper around IndexedDB, WebSQL, LocalStorage, and SessionStorage with a way to define more interfaces (called drivers) *for additional storage solutions. It does a great job handling all your serialization needs, it is **asynchronous **and handles a large set of data types. Its **API resembles Web Storage API* and it is ridiculously simple to learn.

Depending on what kind of storage requirements you have, LocalForage might be a good fit. It provides a unified API to access WebSQL, indexedDB or localStorage.

I find localForage is pretty helpful for this stuff https://github.com/localForage/localForage

localForage (https://localforage.github.io/localForage/) mirrors localStorage syntax, but uses IndexedDB in the background. If that's not supported, it uses WebSQL and then LocalStorage

This is why we have localForage.