2 ms·
The first thing I did was to pop up inspector and see if the author's blog is using this new molasses service. It does not -- but I guess this is ok, it is just
by theamk 6y ago
The first thing I did was to pop up inspector and see if the author's blog is using this new molasses service. It does not -- but I guess this is ok, it is just a blog after all.
The next thing to check was to head www.molasses.app and see if it uses it's own services -- turns out it does not!
docs.molasses.app ? nope
www.molasses.app/signin ? ah, here it is, finally! Here are some examples of the feature flags they have, for the curious:
"Code clean up" / "Enables the code clean up functionality on the feature screen" / active: false
"New login experience" / "a login experience that includes google sign in" / active: true
"test headline" / "Tests the headline" / active: true
I love this kind of openness, and I wish more websites would expose this info to their users!
- securingsincity 6y agoThanks for looking! my personal blog is not a place I was planning on implementing them just because it's not somewhere I do a lot of development. The landing page does use feature flags but they are handled on the server. Honestly one of the next features I have on the roadmap is to hide certain feature flags from the UI. There are a lot of teams that would like to keep even the name of a feature private.