| | | |
|---|
| | Approach A | Approach B |
|---|
| Total cost of ownership | Lower - less reliance on developers, more efficient content launch times, unlocks value within Shopify. | Higher - generally requires a robust technical team, and longer content release cycles. May require additional solutions, i.e. a visual layer, to unlock the full value. |
|---|
| Top use case | Flexibility to build within Shopify ecosystem. | Flexibility to build outside of the Shopify ecosystem. |
|---|
| Time-to-market | Fast (small stores: 1-2 months, medium stores: 2-4 months, large stores: 4+ months) | Slower (3-12 months). |
|---|
| Site speed impact | Designed specifically to optimize for site speed. | Can have mixed results with site speed due to complexity of the system. |
|---|
| Future innovation | Focused on the Shopify ecosystem. | Focused outside of Shopify. |
|---|
| Where it shines | The best tool for managing a Hydrogen storefront that is built to optimize performance, gives you flexibility, and unlocks the full value of Shopify — without a high learning curve or lots of maintenance. | The best tool for pushing content to multiple channels outside of your website via APIs. Ideally supported by large technical teams. |
|---|
| CONTENT MANAGEMENT EXPERIENCE |
|---|
| Release cycles | Launch new content in minutes, no developer required. | Launch new content in hours / days, depending on the developers' backlog. |
|---|
| Content data management | Syncs directly with your Hydrogen storefront, product catalog, and metaobjects.
Built for brands whose main focus is their website. | Centralizes content data to push to multiple channels outside of your website (i.e. in-store kiosk). |
|---|
| Content models | Content models are pre-built and are specific to Shopify. | Content models are built around the CMSs' APIs, and need to be tailored to Shopify. |
|---|
| Visual editor | Content is accessible through a visual editor. See content appear as you type or code. Integrated with metaobjects. | Visual editor is generally not included, may lack real-time visual editing. Not integrated with metaobjects. |
|---|
| Developer support needed | Low. Developers mainly needed for setup and for building new features / custom components. | High. Developers needed to push any content change live on the site. |
|---|
| PLATFORM CAPABILITIES + SUPPORT |
|---|
| Backend compatibility | Built specifically for Shopify Hydrogen storefronts. | Supports any platform - including platforms outside of ecommerce. |
|---|
| Integrations | Focused on the Shopify ecosystem. | Integrations for apps outside the Shopify ecosystem. |
|---|
| Framework | Support for Shopify Remix or Nextjs. | Any framework (to be managed / maintained by developer). |
|---|
| Hosting | Netlify or Oxygen, integrations are pre-built and maintained. | Any hosting, but an integration must be built and maintained. |
|---|
| Preferred Asset Delivery | Connect with external CDN: Shopify CDN, Cloudinary, etc. (or other DAM) *lower bandwidth usage. | Deliver through CMS's CDN *higher bandwidth usage. |
|---|
| Codebase | Integrated into Hydrogen App (along with Hydrogen caching policies, etc.). | Separate codebase and managed by developer to determine integration. |
|---|
| Support | Support of platform, third-party integrations, maintained Hydrogen integration. | Core support on the CMS platform and APIs. |
|---|