Show HN: Frigade - React SDK for building quality onboarding & activation flows

Hey HN! Christian here, cofounder and CTO of Frigade (https://www.frigade.com https://www.frigade.com). Our tool helps product and engineering teams quickly build in-app experiences like getting started checklists, product tours, account upsells, and nps surveys. Basically all the little things that can help boost your product's activation and retention rates, but that you don't really want to spend the time building from scratch. We built React UI components such as <Tour />, <Checklist />, and <Announcement /> and combined them with a web app that you can use to control user targeting, content management, sequencing, and more. These components can help power experiences like onboarding forms, surveys, house ads, and feature announcements. About a year ago, we did our original Launch HN post (https://news.ycombinator.com/item?id=35246292 https://news.ycombinator.com/item?id=35246292) and we got a bunch of great feedback from HN. We also got grilled for having our product and documentation behind a waitlist – whoops! We fixed that, though. We’ve also built a ton of new functionality since then, and we’re dubbing it Frigade 2.0. This includes a free tier so you can check out the product without putting a credit card down, and we recently finished a complete rewrite of our SDK using Radix UI and a theming system built with Emotion. There are other tools in this space but they tend to be "no-code", which sounds good until you realize that they actually inject bloated scripts that slow your product down, and make it hard and annoying for you to customize. We believe that good old code, not "no-code", is the better fit for this space. It lets you unit test, it works with version control, it uses your design system, it rolls out with your CI pipeline, and so on. We solve this problem by: 1) allowing engineers to fully set up the guardrails for what non-technical teammates can do through a one time setup. 2) empowering non-technical team mates to build native experiences that drive better results while building confidence that they won’t mess up your production environment. Ironically, many companies that use our product have churned away from no-code solutions (such as Pendo) as they were too time consuming to manage, caused too many bugs in production, and simply weren’t effective enough. Of course, the upfront cost of setting up Frigade is a bit higher than dropping in a <script /> tag on your website, but once it's set up, non-technical team mates (such as marketers) have full control to create experiences within the guardrails that engineering has created. What do you think about belief and our approach? We’re especially curious to hear from those folks who have experience using these no-code tools or have had to build these kinds of experiences from scratch.