Change name?

[russhwolf]

Kevin called me out in a podcast and said the name Multiplatform Settings isn't catchy enough. I've had this thought as well but I haven't yet come up with anything I like better. Leaving this here to track the possibility of changing it and potentially source ideas.

[kpgalligan]

I have no idea. I'm not great with names either.

[mustafaozhan]

Definitely agree with a change :) it is confusing if you have already SettingsView/SettingsFragment/SettingsViewController and plus a SettingsViewModel (which can be possible in many apps)

Then you want to use this library for entire app persistence and created a SettingsRepository. Upps! It will be used in entire app, not only in settings screen :)

[kurthuwig]

What about

• KnobsAndLevers (something catchy for "settings")
• PersistentKeyValueStore (which is what is actually does)

My main point is, that the library does not set anything or change any settings outside of itself. So why call it "settings"?

[CaelumF]

It could be used for settings, and that's the use case it's designed around, which does probably have implications. I like non-catchy primary names.

How about "multiplatform-kv-settings"

[mustafaozhan]

Ohh, years after you just reminded me @CaelumF 🙂 I have already got used to it but could be just Persist or Persistence too.

Also, @russhwolf this can be converted to discussion, Probably even discussions was not announced when this issue is created 🙂

[josegbel]

kase - to maintain kotlin's theme of using puns that contain the letter k.