Beyond Hydrogen: How Shopify Fits in the Framework Wars
Introduction
The JavaScript framework landscape is crowded: Next.js, Remix, Angular, Vue, Svelte — and Shopify’s own Hydrogen. Each has its strengths, and merchants often ask: Why should we use Hydrogen instead of a “general-purpose” framework like Next.js?
This post examines Shopify’s position in the framework wars and how Hydrogen fits into the bigger picture.
Next.js vs Hydrogen
Next.js
- General-purpose framework, backed by Vercel.
- Strong ecosystem for SSR, ISR, and API routes.
- Widely adopted outside ecommerce.
Hydrogen
- Purpose-built for Shopify commerce.
- Tight integration with Storefront API, Cart API, and Oxygen edge.
- Commerce-first patterns (loaders, cart mutations, SEO helpers).
👉 Verdict: Next.js = broad platform, Hydrogen = verticalized commerce tool.
Remix vs Hydrogen
Remix
- Server-first rendering, streaming-friendly.
- Good fit for apps needing fine-grained loader/action control.
Hydrogen
- Remix under the hood → inherits streaming + loaders.
- But adds Shopify commerce context + built-in APIs.
👉 Verdict: Hydrogen is Remix with commerce batteries included.
Angular in Commerce
- Historically strong in enterprise dashboards.
- Heavy for ecommerce storefronts.
- Few merchants use Angular for Shopify → limited ecosystem.
👉 Angular may persist in enterprise back-office, but not storefronts.
Why Shopify Built Hydrogen
- To control the DX (developer experience) for commerce.
- To standardize headless best practices → loaders, streaming, API integration.
- To ensure Oxygen edge compatibility (something general frameworks can’t guarantee).
- To align Shopify’s roadmap with React’s future (Server Components, streaming).
Competitive Positioning
| Framework | Strengths | Weaknesses | Shopify Fit |
| Next.js | Broad ecosystem, Vercel | Not commerce-specific | Possible, but less native |
| Remix | SSR + streaming control | Generic, no commerce context | Core of Hydrogen |
| Angular | Enterprise dashboards | Heavy, limited commerce use | Back-office, not storefront |
| Hydrogen | Commerce-first, Shopify APIs | Smaller ecosystem outside Shopify | Best for Shopify merchants |
Case Example: Apparel Brand Decision
- Initially evaluated Next.js + Commerce.js.
- Switched to Hydrogen:
- Faster integration with Storefront API.
- Built-in cart + SEO helpers saved weeks of dev time.
- Oxygen hosting reduced latency globally.
- Outcome: 20% faster launch than planned.
Conclusion
Shopify isn’t competing with frameworks like Next.js or Angular directly — it’s carving out a verticalized niche. Hydrogen is Remix + Shopify DNA, deployed on Oxygen. For merchants, it means faster time-to-market, less glue code, and a future aligned with Shopify’s platform.
The framework wars are broad. Hydrogen wins by being focused.