There’s plenty of “should I go headless?” hand-wringing on this board, but not enough of the opposite: concrete examples of what Hydrogen actually unlocks when it’s the right call.
So, for those of you running Hydrogen storefronts in production: what did you build that a theme genuinely couldn’t have delivered? The custom product configurator, the weird checkout-adjacent flow, the multi-brand architecture, the integration a theme’s structure would have choked on.
And to keep it honest and useful for people evaluating, two follow-ups:
- What surprised you in a bad way? The thing nobody warned you about - app replacements, content editing, maintenance load, whatever it was.
- Knowing what you know now, would you make the same call? Same store, same team, 2026 - Hydrogen again, or back to a theme?
I work in the Hydrogen ecosystem so I’ll admit self-interest in hearing the success stories but the “would you do it again: no” answers are honestly just as valuable for anyone reading this thread while deciding. Both welcome.
Hi @Weaverse
So far, we’ve done projects using classic Shopify themes as well as Hydrogen, and the main lesson learned is that Hydrogen is most useful in cases when there are complex requirements that go way beyond the capabilities of Online Store themes.
In one case, Hydrogen proved its value in a storefront that had an advanced product customization process as well as several external API integrations. Although a theme might have handled some part of the work, maintaining the performance and flexibility of the code base would become harder as the project scales. Hydrogen gave us more freedom regarding controlling the user experience and the logic of the application.
However, there are certain drawbacks that are not always obvious:
- Some Shopify apps won’t work on Hydrogen out of the box, meaning that you’ll need to create something similar from scratch.
- Content management may become more challenging because of more planning.
- Deployment and monitoring will require more developer time.
If we would start building the same application again today, we would choose Hydrogen again, but just for projects which have legitimate headless needs. In most cases, a Shopify store that is built on a solid theme will be quicker to deploy, less expensive to maintain, and faster to develop.
The decision for us depends on one single question: Are there any business requirements that can’t reasonably be satisfied by a Shopify theme? If not, we build a theme. If so, Hydrogen may become a good choice.
We’ve evaluated hudrogen for a few projects, and i think the biggest takeaway is that it’s not about making a storefront look better. It’s about enabling experiences that are difficult or impractical to build within the constraints of a traditional theme.
The strongest use cases I’ve seen are thinge like highly interactive product configurators, complex B2B portals, multi brand experiences sharing the sane backend, and integrations with externals systems that need more control over the storefront than Liquid typically provides.
That said, the trands off are real. One of the biggest surprises for many teams is how much of the Shopify app ecosystem assumes a theme-based storefront. Features that are “install and go” on a standard theme often require custom implementation in Hydrogen. Content editing can also become more developer=dependent unless you’ve invested in a solid CMS workflow.
Maintenance is another factor. With a theme, many merchants can handle day-to-day updates themselves. With Hydrogen, you generally need ongoing development resoursces for new features, upgrades, and integrations.
If the storefront requirements truly justify that flexibility and you have a team that can support it, I’d absolutely consider Hydrogen again. But for a typical Shopify store focused on merchandising and conversion, I’d still lean toward a well-built theme.The development overhead is significantly lower, and today’s themes are capable of much more than they were a few years ago.
I’m curious to hear from merchants who have been running Hydrogen in production for a year or more. It would be interesting to know which custom experiences have continued to deliver value versus which ones turned out to be more expensive to maintain than expected.