Really interested in how to turn the flags function to static mode, found the docs for this part to be rather confusing. Thanks for the video, super helpful!
I feel like you could just create an admin dashboard in your project and use vercel/ky (basically redis) to store the feature flag state which lets you have the option to either use redis CLI or some frontend/dashboard you create to toggle the feature flag. I think this was made as barebones as possible for just that thing
Hey Jack, great video! I do want to see how we can make this static. I build a lot of marketing pages and static is important so hearing I can use feature flags and still have the page be static has me intrigued!
Yeah, I am new to NextJS but from logical point of view if you need two users to have different content at the same URL it cannot be fully static. I could imagine a PPR page but not fully static. Having said that, the only situation where it could be static is when you always render with given static values and then you can change them and redeploy the page or via that special UI if you need to test things. I am Next noob though and many things in this framework surprised me already It is also possible I am not understanding some terminology.
@@Jacur1980 if only PPR was prod-ready... it would solve quite a few of those dilemmas, because then you can prerender the whole page except what's dynamic through a flag.
cool! How impactful this is on response times? I guess this is considered as an additional request on all routes that need these flag checking so it would add up to the response time of that route/api right? and if hosted en s3 aws its a separate service that is billed on usage right?
You can store the flags in Edge Config which has minimal latency. When hosted on Vercel we optimise it so the reads happen without going over the network and achieve
Unable to understand what this has to do with this feature flag api? Can't we simply make an API request and based on return value, render our screen??
Yes, that could totally be seen as using a flag too. In the original article I go as far as saying "you can just use a boolean and call that a flag" :) By using the Flags SDK you get stuff on top, like being able too see and override your flags in the toolbar, and being able to precompute flags to generate static variations. The Flags SDK also encodes best practices, like not being able to pass arguments to a flag from the call side to force the state of a flag to be the same across the whole application. The context is instead established from within the decide() function by calling headers(). This also allows deleting the flag without having to do a bunch of cleanup, or switching the implementation without having to touch the call sides.
It's hard, they replicate worst then cockroaches. The main fault is with TH-cam, but they simply don't care, because where will content creators move to?
@@jherr my best guess. these are used for making youtube think that its an original account and not bot. then they are sold as (i can get 10k views, likes, subscribes on your youtube if you pay me so and so)
@@harshitgupta2803 I fell for that scam very early on. They could vend exactly 1,000 views in just a few seconds. The promise was that it was all organic and they were doing it with real marketing and promotions. The reality was, in my case, that it was all referrals from XXX sites. There are LOTS of scams in the YT space.
No. Flags are orthagonal to that. Feature flags control whether or not the feature is available at all. RBAC controls whether it's enabled/disabled for this particular user and is usually administrable by the tenant admin.
It's unstable now as an indication that the API may change before it's first official release. Marking pre-release APIs as unstable is an industry best practice.
oh this is cool to see and hits home. i implemented feature flags from scratch at work haha. we use them everywhere now
Really interested in how to turn the flags function to static mode, found the docs for this part to be rather confusing. Thanks for the video, super helpful!
Thank you, great walkthrough, as always
Thanks a lot for the interesting overview!
Wish Vercel did a dashboard so you could fetch the flags from them
vercel? you mean aws + 400% of cost? build a dashboard
We have that at my job. Fairy easy to make
nice work Jack
I feel like you could just create an admin dashboard in your project and use vercel/ky (basically redis) to store the feature flag state which lets you have the option to either use redis CLI or some frontend/dashboard you create to toggle the feature flag. I think this was made as barebones as possible for just that thing
Yeah, there are lots of different ways to store/manage feature flags. I chose a simple route here just for demonstration purposes.
Hey Jack, great video! I do want to see how we can make this static. I build a lot of marketing pages and static is important so hearing I can use feature flags and still have the page be static has me intrigued!
Yeah, I am new to NextJS but from logical point of view if you need two users to have different content at the same URL it cannot be fully static.
I could imagine a PPR page but not fully static.
Having said that, the only situation where it could be static is when you always render with given static values and then you can change them and redeploy the page or via that special UI if you need to test things.
I am Next noob though and many things in this framework surprised me already It is also possible I am not understanding some terminology.
@@Jacur1980 if only PPR was prod-ready... it would solve quite a few of those dilemmas, because then you can prerender the whole page except what's dynamic through a flag.
Very interested to see ISR with a/b and feature flags :)
cool! How impactful this is on response times? I guess this is considered as an additional request on all routes that need these flag checking so it would add up to the response time of that route/api right? and if hosted en s3 aws its a separate service that is billed on usage right?
You can do a HEAD. Or put an SLA on it. Or from it with a CDN.
You can store the flags in Edge Config which has minimal latency. When hosted on Vercel we optimise it so the reads happen without going over the network and achieve
Thanks for the video. In a multi tenant application would it work too?
Unable to understand what this has to do with this feature flag api? Can't we simply make an API request and based on return value, render our screen??
Yes, that could totally be seen as using a flag too. In the original article I go as far as saying "you can just use a boolean and call that a flag" :)
By using the Flags SDK you get stuff on top, like being able too see and override your flags in the toolbar, and being able to precompute flags to generate static variations.
The Flags SDK also encodes best practices, like not being able to pass arguments to a flag from the call side to force the state of a flag to be the same across the whole application. The context is instead established from within the decide() function by calling headers(). This also allows deleting the flag without having to do a bunch of cleanup, or switching the implementation without having to touch the call sides.
Feature flags are great, but not unstable flags. I just use Payload as a headless to set my feature flags with Nextjs. Much more manageable.
Hi Jack, I need that NextJs course, like pronto, please hurry.
Any best alternative beside of vercel to apply feature flags for nextjs app ?
Yeah it’s called flipt
Hi jack, please get ride of those comments 😅. I think those are spam and spicy 😂.
Yeah they've been around for years and google just ease with it.
It's hard, they replicate worst then cockroaches. The main fault is with TH-cam, but they simply don't care, because where will content creators move to?
Wow. It's usually just two. Today I got five! Super exciting! Sigh. I'm not even sure what these comments do for these scammers.
@@jherr my best guess. these are used for making youtube think that its an original account and not bot. then they are sold as (i can get 10k views, likes, subscribes on your youtube if you pay me so and so)
@@harshitgupta2803 I fell for that scam very early on. They could vend exactly 1,000 views in just a few seconds. The promise was that it was all organic and they were doing it with real marketing and promotions. The reality was, in my case, that it was all referrals from XXX sites. There are LOTS of scams in the YT space.
❤❤
this work with page routes?
Uncle Jack, isn't feature flags work similarly to role base permission control?
No. Flags are orthagonal to that. Feature flags control whether or not the feature is available at all. RBAC controls whether it's enabled/disabled for this particular user and is usually administrable by the tenant admin.
@@jherr thank uncle for clarifying
hey how do you show the node version and react version on the terminal
That's a feature from a theme like powerlevel9k
Another unstable feature from vercel, great!
It's unstable now as an indication that the API may change before it's first official release. Marking pre-release APIs as unstable is an industry best practice.
Anyone know a good tool for implementing feature flags in React Native?
why not only use true/false to show a feature from database?
This is working only if deployed to Vercel?
No. The static stuff, yes, probably. But the basic flags stuff doesn't require Vercel. The toolbar does.
do u guys know what font Jack is using ?
you can find it in the video description ;)
okay Ron, so you saying NextJs is in Hogwarts curriculum.
you don't need "force-dynamic" when you are accessing headers and cookies
Yeah, that's true. That was from the example code provided by Vercel. I should have pulled that out?
Vecellllll (el)) not vercle
Thanks for video, love u
Yeah, I flip it all the time.
My favorite pasta is vercelli