Willow

Reading their code it's actually only singleton as much as you instantiate it so it doesn't matter *that* much. i kind of want to try and implement `DataStore` for just...

What if we just... ```kotlin // TODO: name and stuff data class PrefData( val testProp: String ) object PrefDataSerializer : Serializer { private val gson = Gson() override val defaultValue:...

Phew this was more effort than I wanted but we have DataStore. I can implement writing to prefs and change events now. I must say, I think we have *way*...

I did not figure out how to do editing yet with this approach though. If we don't use SharedPreferences then the whole `androidx.preference` becomes useless (we already reimplement good part...

We already do hacks to make account preferences work and from what I see now we actually *do write values accidentally* for account preferences even though we don't want it....

Yeah you theoretically can use `PreferenceDataStore` but then you are back to untyped API and we don't want that. Poked into UI a bit, I'm not sure how to do...

I have a bit of a problem with the language picker, I think because it is accessed so early it gets some wrong instance of preferences, need to debug...

A bit on how themes can be injected into gui library: https://mui.com/joy-ui/customization/approaches/

After building a prototype there are few points we should address before implementing: 1. Which instance should it be stored on? It should be a per-user entity 2. How should...

Not relevant anymore