Feature flag persistence without "always" profiles

[haritowa]

Problem Statement

Feature flags persistence requires "always" profiles

Solution Brainstorm

I am thinking about this enhancement. What if we attach our currently evaluated feature flags(from local device storage) to identify call? This way we can set the expected flag values during persona creation and can skip intermediate non-identified personas creation.

I can recreate this approach by setting custom props(flag1, flag2...) and then set feature flags to rollout based on these props. Yet I would love to see:

• an explanation why this approach is bad(and why you haven't implemented it yourself)
• if the approach is actually good -- let's make it available for everyone without sketchy "fixes"

[haritowa]

I can test my "hacky" solution first, if you want to

[ioannisj]

cc @PostHog/team-feature-flags for your input/thoughts here

[marandaneto]

@haritowa mind explaining what the problem is and the possible solution you came to? It's unclear to me what the problem is.
a few code snippets with examples would help, thanks.

[haritowa]

Haha I knew my description will not be good enough 😂

Ok I'll create a better one later

[haacked]

@haritowa Is the goal to create something like Sticky Flags into the SDKs?

[haritowa]

@haritowa Is the goal to create something like Sticky Flags into the SDKs?

Yes! This is exactly what I am talking about! Now I feel ashamed 😂

I'll read the guide closer, maybe I'll find answers to my questions in the guide. Or maybe you have some other gold-tier info to share?

[haritowa]

And with this PR #373 (also yours lol) -- this could work like a charm completely replacing feature flag persistence... or am I wrong?

[haacked]

Yes! This is exactly what I am talking about! Now I feel ashamed 😂

No need to feel ashamed!

And with this PR #373 (also yours lol) -- this could work like a charm completely replacing feature flag persistence... or am I wrong?

I'm not sure. I need more details on your scenario specifically to determine that.

[haritowa]

I'm not sure. I need more details on your scenario specifically to determine that.

@haacked
I want to replace feature flag persistence with sticky feature flags. This will allow me to disable "alway" profiles and get cheaper anon events until user signs in. With your PR feature flags resolution will be more stable during the props propagation on BE side, so it(sticky flags) looks like a good solution if I am not missing anything

TBH, I see no use case for feature flag persistence if sticky feature flags are implemented

[haritowa]

I think we will implement sticky flags, move from always profiles and let you know if everything worked as expected @haacked