Going headless with Shopify
Headless is a buzz word right now. But it's far from a new concept. Headless implies the decoupling of two or more web frameworks, one a backend, an API, the other, the front-end, the website itself that your users interact with.
According to Shopify's own whitepaper, the cost of a headless commerce system would be between $50,000 and $500,000 dollars. How did they come up with this figure?
A headless commerce system would typically be built from scratch by developers using whatever code base they chose (Node.js, React, Vue.js, Ruby On Rails, PHP). Shopify provides no boilerplate for this type of system, so how it works, what it does and why it does it would need to be part of a detailed system design process, and would typically be solely focussed on a clear set of end goals, goals that you and your dev team have decided are beyond the capabilities of a custom Shopify Theme. As a business, you're not going to be able to "sit with a freelancer developer" to achieve this type of end product.
Cons of going headless:
With headless, you are foregoing the simplicity of the native Shopify theme editor, which means:
- No WYSIWYG editing
- No theme live previewing
- No native customer accounts
- No access to navigation link lists
- No CMS sections functionality
- No version control via different themes
- No plug and play Shopify Apps
Pro of going headless:
- You get your web experience, on your terms with your custom features.
- Third party apps aren't ruining the party all over your beautiful UI.
- You can finally provide your users with a glorious customer interface, now they can even change their email address!
So how do you do all that stuff now you've gone headless? Typically a third party CMS could be used for this, either cloud hosted (eg. Prismic, Contentful, Storyblok) or self hosted (Wordpress, Craft). Whats that I hear you say, I need another CMS? Yep, your headless site no longer resides on Shopify but on a server somewhere, that might be as simple and cost effective as a static file server like Netlify, but depending on why you've gone headless in the first place, this probably means that your site is now hosted on a cloud server infrastructure (like Digital Ocean or AWS). What, I need a new server and a CMS now? Yep! Going headless is by no means a simple decision.
Thinking of going headless? Contact us to discuss why and how.