what do you guys use to persist data in compose mu...

# compose

[Fudge]

what do you guys use to persist data in compose multiplatform? is there some library that does datastore on android, local storage on web, etc

[Konstantin Tskhovrebov]

https://github.com/terrakok/kmp-awesome

[Cicero]

You can find more in the link from Konstantin, but my go tos are:

SQLDelight - SQLite database
> SQLDelight generates typesafe kotlin APIs from your SQL statements. It verifies your schema, statements, and migrations at compile-time and provides IDE features like autocomplete and refactoring which make writing and maintaining SQL simple.
and

Multiplatform-Settings - Key-Value preferences
> This is a Kotlin library for Multiplatform apps, so that common code can persist key-value data

We also have Realm, if you are familiar with it

Realm - NoSQL database
> Realm is a mobile database that runs directly inside phones, tablets or wearables. This repository holds the source code for the Kotlin SDK for Realm, which runs on Kotlin Multiplatform and Android.

[Fudge]

Thank you, I think multiplatform-settings is what i'm looking for

[Stylianos Gakis]

I'd go with androidx DataStore if you want a key-value store tbh

[Stylianos Gakis]

Konstantin, I see that repo does not accept issues, but I feel like Datastore is missing from the "Storage" section.
If anything it's probably the one android devs should first consider because it's also the one they're most likely already using anyway

[Cicero]

It’s about compose multiplatform and not Android

[Stylianos Gakis]

Datastore is multiplatform
https://cs.android.com/androidx/platform/frameworks/support/+/androidx-main:datastore/datastore-core/build.gradle;l=66-70

[Cicero]

Great to learn about this, thank you Stylianos

[Konstantin Tskhovrebov]

the repo doesn't accept issues because there are PRs 😉

[Pau Marzo]

@Stylianos Gakis Doesnt support web though (ive seen some commits that suggest androidx wants to support wasmjs but still far from supporting room or datastore)

[Fudge]

no wasmJs in multiplatform-settings either 😕

[Cicero]

What’s the issue with the JS target?

[Cicero]

I find wasmJs not working in 50%+ of the existing browsers

[Pau Marzo]

@Fudge yep, the author said he was planning to add it (in some github branches you can see hes working on it) but still no eta for the wasm release

[Pau Marzo]

@Cicero wasm will work sooner rather than later (safari support is almost there). For my usecase, WASM desktop web, it works and its weird that the androidx team has not already implemented the js only target, if they want to support wasm its because maybe they know things...👀 idk

[Cicero]

I mean, as a practical solution, for like, now?

The JS target works.

I would love to use wasm but the implementation is the same and, right now, Wasm, for a general USER problem, it does not work.

Because people don’t use only the 2 most popular browsers.

I’m just saying, go JS, don’t have the headache and as soon as wasm is ready, it’s a flip switch complexity to go wasm.