Is there a plan for releases to play store for a D...
# confetti
y
Is there a plan for releases to play store for a Day 1 OTA? 🙂 Like a beta that we stabilise for Kotlinconf?
âž• 1
đź‘€ 1
I'm going to try to add the bookmarks on Wear.
j
I was wondering about that as well....particularly given delay sometimes in getting review
would be good to have something nailed down by weekend at least I think.....give us enough time to get promoted...wdyt?
y
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.
m
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
y
Other option here is to use Firebase config to disable/enable such things. Makes it safe to land, but turned off.
j
Just to clarify....do we think we would have notifications for the version available for KotlinConf?
m
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).
We could add a button to disable on the settings screen, and keep it by default disabled as an experimental feature.
j
Yeah, was just going to suggest same thing.
y
What about firebase config? If I put up an example then we could try experimental features, rather than more settings.
j
would that just disable/enable feature for everyone....as opposed to somebody being able to do it for their themselves?
y
Yep.
But not sure it's typical to have toggles for notifications, I mean maybe in slack
But generally you apply categories and then users can select those through android, not in the app
But a setting would be way simpler
m
Yes, I was imagining it more like a local feature flag until we built the firebase config ones. 🤔
j
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.
the other thing is I guess it's not really clear to user what those experimental features include....should we just mention notifications here explicitly for now?
m
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).
I think a “Enable Notifications” would be weird, as App -> Notifications already have an option to enable.
j
yeah, that's true
m
I have updated my PR FYI.