All good - it is something that has been over-complicated for marketing/product reasons.
If you know what A/B testing is, feature flagging can really allow you to nail down how you should deliver an experience to an end user.
We track end-to-end engagements on our websites based on how the content is displayed on a page with more performant layouts/content winning the test to drive users through the funnel.
I don't love it though because it's a lot of waste that gets left over and not cleaned up leaving billing to grow exponentially as flags are continually called for no reason.
That's not a feature flagging service then (config as a service! not a thing really...)
I've done both client and server side implementations of the launch darkly sdk and that's how it's done to know client context.
If you're initialising the entire SDK only to load 1 set of configuration items, I'd argue you can host the config as a json file on a CDN and be done with it - feature flagging is overkill.
If it's not obvious I meant breathing while sleeping at night in a sleep apnea discussion, I think you need to analyse your own internal bias and possible self-hate.
I'm very sure i have sleep apnea now as i wake up literally in panic where i'm not breathing + have a full bladder and need to go a few times a night (which i've read as a kidney response with sleep apnea).
As i said this all came about with extra weight gain in the past few months.
Google/Android don't want AI bots spamming marketplaces with dodgy apps.
Tie in the app to a verified identity/individual and it makes the audit process easier as well as engagement with authorities from the user's country if required (e.g. app facilitating child abuse).
Though sometimes it is very interesting and might delay sleep a bit