Until now I was very selective about onboarding new teams onto HappyKit. I gated the onboarding process through a manual step which required at least one interaction with me. Usually this would be an email, a Slack message or sometimes a friendly Zoom call.
New HappyKit landing page just dropped
I wanted to this 3d wrench for sooo long! After many iterations I finally ended up with something I liked last night. I'm over the moon with how it turned out.
Wobble the 🔧 yourself at https://t.co/KekJk8IKSF
This is a great intro "the edge"!
HappyKit's feature flags live at the edge, waiting to be consumed by your Edge Middleware & Edge API Routes application at low latency :)
Wrote about HappyKit evaluates feature flags
Worth a read if you haven't used feature flags before, since a lot of first-timers run into the same thing.
Hopefully one day it's solved through a better UI instead :) Just have to come up with one first
https://t.co/hhCfQXSltd
Wow, https://t.co/XZwNmXhjI9 crossed 400 stars on GitHub!
HappyKit is now resolving ~4 million feature flags daily.
I'm feeling grateful for all your trust and support
Resources to get you started with building Payments apps. I've built with all of them
- Happy Kit (feature/beta flags): if 3rd party APIs go down, use @happykitdev/@LaunchDarkly to switch to always be live!
- Multi-currency: Use https://t.co/k1TeOa46iY + https://t.co/AVlR5WA7ZY
Added a new Types section to HappyKit
The types in the snippet are auto-generated based on your feature flags.
You can paste this into your project's types.d.ts file to then later use it as useFlags<AppFlags>() for fully typed flags
More on this here: https://t.co/0ewGZGdqbp