Yesterday, Webflow announced that they will be halting further development on Memberships and Logic, and that these subsystems will be released to production soon ( to all users, with no more BETA label ) with the current feature set.
This news means that we likely won’t see a few key features the community has been eagerly awaiting, most notably-
Element-level conditional visibility, by access-group.
Internally, Sygnal has been using a makeshift solution that provides this capability, but we’ve avoided adding it into the Sygnal Attributes library because it looked likely that Webflow’s element-level access group functionality would drop any day.
Also, our makeshift solution is a total hack.
Even with Webflow’s declaration that they have halted feature development on Memberships, I’m hesitant to add this feature to our library for two main reasons;
It’s slow, meaning it adds a second or two for us to compile access group data after login. This is on top of the current performance costs of obtaining custom user fields, so I’m not enthusiastic about potentially adding seconds to that login-time delay.
It’s insecure. Gated elements will be shown and hidden using script, rather than server-side the way Webflow gates elements in its login-state conditional visibility feature. Client-side gating is insecure, and although it is the way other platforms like Memberstack work on top of Webflow, it’s simply not suitable for secure content.
and of course…
- It requires polishing, testing, and setup docs which will cost a couple days of dev / test time.
So, I thought the best way to decide this is to open the discussion to our awesome users.
- Do you need this?
- Are you going to stick with Memberships?
- What are your use cases?
- Will the performance delay ( just after login ) and the lack of element-content security be workable for your use cases?
Let me know.
And, if you vote yes, please consider contributing something to help cover our dev costs.