Is there a plan for releases to play store for a Day 1 OTA? 🙂 Like a beta that we stabilise for Kotlinconf?

I was wondering about that as well....particularly given delay sometimes in getting review

I think it's a safe approach. And probably good we build towards a stable version, with enough time for beta, and enough time for that tested beta to get published.

That makes sense. Btw, maybe we can post-pone (or disable on the public release) my notification changes. Would like to do @yschimke changes before that going public. https://github.com/joreilly/Confetti/pull/544

Other option here is to use Firebase config to disable/enable such things. Makes it safe to land, but turned off.

Just to clarify....do we think we would have notifications for the version available for KotlinConf?

I would like to have the notifications but I wouldn't add to the public release without a way to disable. My implementation is quite naive, and misses basic features (like clicking in the notification and opening the sessions, less wasteful worker, request permission, etc).

Yeah, was just going to suggest same thing.

What about firebase config? If I put up an example then we could try experimental features, rather than more settings.

would that just disable/enable feature for everyone....as opposed to somebody being able to do it for their themselves?

Yep.

Yes, I was imagining it more like a local feature flag until we built the firebase config ones. 🤔

just as an aside, and not directly related to this, but we're thinking we'll probably need to move to a "normal" full screen settings options at some point....just to give us more real estate etc to manage options. Re. this change, I would perhaps move it below dark mode option to keep separate from theme related ones.

IMO, we can simple group whatever feature is not stable as experimental and later when we move to firebase remote config we just delete this (hopefully after conf).

yeah, that's true

I have updated my PR FYI.