Vercel
Changelog7-point breakdown
"Vercel Flags now supports JSON values" states the specific shipped capability directly, not a vague label.
First sentence states the news immediately: "You can now store JSON values in Vercel Flags, extending the existing support for boolean, string, and number values."
Directly states the outcome: "This allows you to collapse what used to take several related flags into a single feature flag," followed by a concrete A/B model-switching example.
Short entry with no subheadings breaking up the explanation from the code example; relies on a single flowing block before the code sample.
Shows literal before ("used to take several related flags") vs after (single JSON flag) plus an actual code sample with Variant A and Variant B configurations.
No user quote, adoption number, or case study reference anywhere in the entry.
"Try it out or learn more about Vercel Flags" with direct links.
The entry states its news plainly in the headline and lead, and backs the claim with a concrete before/after code example rather than abstract description — the kind of structural clarity most changelogs lack. Its only real gap is the complete absence of any adoption signal or user validation, leaving the feature's real-world impact unstated.
You can now store JSON values in Vercel Flags, extending the existing support for boolean, string, and number values. This allows you to collapse what used to take several related flags into a single feature flag. For example, to A/B test how a different model performs, you can now define a single `model` flag. Use Vercel Flags to progressively route traffic to a new model, A/B test, or quickly switch models in case a provider is having issues.← Back to the Decision Friction Index