Latest / Inside Commerce: Ecommerce Strategy, CX and Technology Podcast / EP222: Strategic View on Shopify's Hydrogen Headless Framework, with CommerceUI CTO Michal Klim
Transcript
- 0:02Hi everyone, Welcome back to the RE Platform podcast sponsored by
- 0:06Patchworks. It's just me today as James is
- 0:08busy with client work, but we've got a super interesting episode.
- 0:12I'm joined by Michael from Commerce UI who I'll let
- 0:15introduce himself in a second, but I essentially invited
- 0:19Michael on probably a few weeks ago now, but I've cancelled a
- 0:23number of times. I've moved it a number of times,
- 0:25but we've got her in the end to essentially talk about hydrogen
- 0:29and kind of I guess Shopify's general kind of approach to
- 0:32headless since they announced hydrogen and oxygen and what it
- 0:36means for merchants and also what it means in the context of
- 0:39everything that's going on at the moment with liquid and
- 0:42online store. So yeah, super excited to have
- 0:45you on just to set the scene a little bit more as well just
- 0:49before I do hand over. So I think it is an interesting
- 0:53time at the moment because I think when Hydrogen was first
- 0:57kind of announced and you know people started looking at it
- 1:01Headless was probably a little bit more at the kind of
- 1:05forefront of what Shopify were doing.
- 1:06Whereas it feels like it's maybe not talked about as much at the
- 1:10moment. You know as they've kind of
- 1:13moved towards more enterprise positioning rather than just
- 1:15components etcetera. But yeah, and it's also, it'll
- 1:19also be interesting to talk a bit about kind of where it sits
- 1:22in relation to maybe arguably some of the low code movements
- 1:26Shopify are making as they kind of introduce more visual editing
- 1:31and that kind of functionality into the theme customizer
- 1:34etcetera and sections. So we've spoke a lot about it.
- 1:38I know you've spoken to Liam a lot about it as well.
- 1:40So, yeah, thanks for joining. Welcome to the podcast.
- 1:43Maybe to start off with, you can just give us a bit of an
- 1:45introduction to you commerce UI. Yeah, in fact, just those two
- 1:50staff. Yeah.
- 1:51So, yeah, very nice to be here. Thank you for inviting me.
- 1:54So yeah, let me maybe start, you know, from from Commerce UI.
- 2:02So Commerce UI is you know the design tech agency solely focus
- 2:07on building e-commerce. We work with premium brands
- 2:12mainly from fashion tech and lifestyle industry.
- 2:17We we are also a small senior LED team and our strong side is
- 2:22you know combining aesthetics with technology.
- 2:25When it comes to me, I'm city at Commerce UI and I'm mainly
- 2:30responsible for the delivery and everything technological at
- 2:35Commerce UI. Definitely.
- 2:40And yeah, I was going to add a few examples to that, but I
- 2:44didn't bring your website up in types.
- 2:46But yeah, they've done some really good sites.
- 2:47We work together on Lyft, foils and I know there's a number of
- 2:50others that are very widely discussed from both the headless
- 2:54and general kind of, you know, quality at front end
- 2:57perspective. So first question, in fact maybe
- 3:01not even question, but initially just for the kind of audience
- 3:04and maybe listeners that don't know the insurance.
- 3:06And out of hydrogen, can you just talk us through exactly
- 3:11what hydrogen and oxygen are in layman's terms?
- 3:14And also just give us a view of what you think Shopify's overall
- 3:17objectives were when they introduced them to the market?
- 3:21Yes. So Simply put, Hydrogen is
- 3:26Shopify native solution for building headless storefronts.
- 3:31The same goes almost the same goes from for hot oxygen.
- 3:36It's a native Shopify solution for hosting those headless
- 3:40storefronts. So I think we'll also talk about
- 3:48this most likely later on, but Hydrogen is only a front face of
- 3:54a bigger architectural shift on a Shopify, and the biggest value
- 4:02probe of Hydrogen and oxygen at this point is that it reduces
- 4:07the entry of barrier to headless significantly.
- 4:12It does it by by offering a very solid starter and standardizing
- 4:20the headless development which is have historically a biggest
- 4:24pain when when it comes to to headless there is so much
- 4:28decision to make that it's very easy to make a bad decision and
- 4:33when you start with somehow a standardized approach it's it
- 4:37reduces the risk of the project by by a mark.
- 4:42Great. And I guess like what do you
- 4:44think like when Shopify introduced it, because actually
- 4:47Shopify was already fairly mature when it came to headless.
- 4:51And I think probably more so than a lot of people realized.
- 4:54And you know, a lot of the even the composable platforms out
- 4:57there don't kind of have this more kind of opinionated
- 5:02approach to the front end framework and tech stack.
- 5:05And to what do you think Shopify's objectives?
- 5:07Why do you think they did it? Yes, I I I honestly think there
- 5:12is. There is a couple of reasons
- 5:15there. One thing is that I think the
- 5:21most of this one is that Shopify shifts focus towards enterprise
- 5:26and enterprise it's where headless is is very, very well
- 5:32received and most likely enterprise clients has already
- 5:37some technical capabilities to use headless.
- 5:39There are used to headless so to some extent they they had to
- 5:43have an answer for that. Another thing is that there are
- 5:50other contenders rising like centre for example which offers
- 5:55also headless approach and they they also wanted to to be in
- 6:02that space. Another thing could be the
- 6:07overall shift in in how do you, how you build e-commerce sites
- 6:13right now. So back in the days you you you
- 6:17had to build a homepage, PDPPLP cards and that's it and you had
- 6:24your e-commerce and right now it's much more competitive.
- 6:28You build the whole story storytelling.
- 6:31You have this 360 experience and this unbranded experience in
- 6:36your e-commerce. Brands invest much more into
- 6:40into storytelling and for those brands liquid may just not be
- 6:48enough. So they they wanted to to also
- 6:52be in that in in that space. Yeah, absolutely.
- 6:56I think we can come on to it later on, but I think it'd be
- 6:58good to understand like I guess some of the benefits to Shopify
- 7:02of developers like Commerce UI kind of playing within their
- 7:06ecosystem as well that what that kind of allows them to do.
- 7:10And then I think we can also talk a bit more around kind of
- 7:14obviously Shopify has Iraq ecosystem, but what that could
- 7:17look like in the future, but we can come on to that And the
- 7:20original topic for this episode was to talk with your client nor
- 7:25hammer which which was going to be kind of a jumble discussion
- 7:28as to why they went down the hydrogen route and also then how
- 7:33you kind of build the site. But we decided to switch it up
- 7:36just because you know, we have a lot of discussions with brands
- 7:39and I think it'd probably be more interesting for us to get
- 7:42into the detail a little bit and a bit of an open Q&A.
- 7:46So Norama is a super, you know, strong sight.
- 7:50Again, it's been like widely praised by people in the
- 7:53industry, but they're obviously a luxury brand with relatively
- 7:58small team. I would imagine what made them
- 8:01go down the hydrogen route? What was it that kind of, yeah,
- 8:03drove the decision? Yes.
- 8:05So I'd like to, I like the fact that we we made this decision
- 8:12very own together and they they listen to to to our conditions
- 8:17right from the beginning of our partnership.
- 8:20And you know Nora Mora is this kind of a specific brand and at
- 8:27the first glance it may not seem fit for Headless.
- 8:32So we started because we started our research around them and we
- 8:38we were considering liquid approach.
- 8:42But then we we looked closer how they manage the previous side
- 8:48and what pain points they had. And one thing that cuts our
- 8:53eyes, our eye at the beginning was that they are not benefiting
- 8:57much from the app ecosystem. So their their site was bloated,
- 9:04they weren't happy around it and basically major pickpoints
- 9:07revolves around how does how does integrations work or don't
- 9:14work. So and this is a very common
- 9:19case for for those premium fashion brands which cares more
- 9:24about you know this bespoke experience, this on brand
- 9:27experience and they are not interested in this typical say
- 9:32Booster e-commerce sales or say Booster integrations.
- 9:36So they just don't work for them.
- 9:38They care more about this you know, feeling of prestige luxury
- 9:46movie. But so that that that was one
- 9:51point for for us. Another thing that that cut our
- 9:55attention was that they have very strong focus on editorial
- 10:00and they have very, very a lot of very custom ideas how they
- 10:04want to tell the story and they don't have a dedicated editorial
- 10:11team. So we knew that this this part
- 10:15will be most like the bottleneck and we knew that the editorial
- 10:20experience play a huge role in this project and has to be
- 10:24explicit and easy and allowed them to build those custom
- 10:29custom storytelling. Another thing is that they
- 10:34really really care about this UI excellence.
- 10:38How how the site looks and feels, how you go through the
- 10:42whole flows, how all all of the widgets interact and cave and
- 10:48how they fit into the site. So and to be honest, normal is
- 10:56this kind of a borderline case from a technical technological
- 11:02point of view. So and seamlessly, small things
- 11:07tip the scare if we should go headless or not.
- 11:11And without hydrogen I think honestly that this decision
- 11:16would be harder. But with hydrogen we knew.
- 11:23We knew that generally we knew that the headless is is a good
- 11:27way to go for what they want to achieve now and in the future.
- 11:32And it all boils down to the cost.
- 11:36If it's if it if it's applicable in this case.
- 11:40So with hydrogen we knew that we could create the bespoke
- 11:45experience, but at the same time not making the project
- 11:49unnecessarily complex. Patchworks the world's most
- 11:52modern integration platform. We can connect any key ecommerce
- 11:56system from storefronts to marketplaces and Erps to
- 11:58fulfillment solutions. This allows retailers and
- 12:01partners alike to simplify their tech stack integration and do
- 12:03away with point to point vendor specific apps.
- 12:06We can automate and streamline the flow of data across your
- 12:08entire e-commerce business. Find out more at We Are
- 12:10patchworks.com. That makes sense and an
- 12:15interesting like I guess it's more of a discussion than a
- 12:18question. But yeah, we we're working with
- 12:21a brand at the moment and very high end I'd say premium fashion
- 12:25brand more so than luxury. But it's interesting because
- 12:30they they have aspirations to be quite agile and you know build a
- 12:33really solid, I guess kind of road map in terms of new
- 12:38features. And you know they want to kind
- 12:40of build more an optimization culture, which I think might be
- 12:43for the type of team they've got easier to achieve in Liquid.
- 12:47But they also won like, you know, the, like you say, like
- 12:51that perfect rendering experience.
- 12:53They want everything to be, you know, every little interaction,
- 12:57every little kind of bit of animation to be perfect.
- 12:59And then they have massive, you know, imagery like loads of
- 13:02video. You know they're insisting on
- 13:05certain pieces of functionality that clearly slow down the kind
- 13:10of existing Liquid theme and also kind of blow the side.
- 13:14And actually when we first looked at, I don't think I saw
- 13:18the agency would have wanted to go down the hydrogen route, but
- 13:22I actually do think they could be and they probably could be a
- 13:25really good fit. And I guess like do you do you
- 13:30see any like you build on both now so you you build on Liquid
- 13:35as well like like what's your view on, do you think it's
- 13:39possible to achieve that same kind of perfect like like you
- 13:43say kind of UI and rendering experience like you look at kind
- 13:47of an on running or some of the headless sites that you've built
- 13:50that you think it's possible to achieve that in in Liquid?
- 13:55Yes and no. It's it always depends when you
- 13:58put that you know point of excellence of of UII generally
- 14:03think that Liquid will take you very very far when it comes to
- 14:09to UI or UX excellence. Let's say you know like 85 maybe
- 14:14even 90% of the way. But if you if you are the kind
- 14:21of a brand that cares about this last 10%, headless solutions
- 14:27will typically be a better suited for for the task.
- 14:31It it all boils down to the fact that there is a wider toolkit
- 14:36when it comes to when it comes to creating bespoke UI widgets.
- 14:46And also the fact that if we look at the front end as an
- 14:51industry on itself, the the top voices of this industry are very
- 14:59much invested in in headless space.
- 15:02They they are all talking headless and the the biggest
- 15:08progress in the industry is happening in this space.
- 15:13As it happens, one of those top voices is is the creator of
- 15:17remix, which is basically Hydrogen right now, says Shopify
- 15:23invested in the remix and build Hydrogen on top of the remix.
- 15:31Another thing that that allows you to to create to achieve this
- 15:36excellence is the fact that you you're in control.
- 15:40Of course with with this control becomes much greater
- 15:46responsibility. You can break much more things
- 15:48but you control on one hand the routing, how you, how the Euro
- 15:56structure looks like, how you load the site, how you present
- 16:01the data, what part of the data should be presented right at the
- 16:06beginning, what what kind of data should be loaded later on
- 16:10and so on and so on. So that's a big part of of
- 16:15creating those experiences. Another thing is that you you
- 16:21control the integrations and you control the data flow from from
- 16:26a first party services and you you obtain the data and you
- 16:32decide how it should be presented to to the to the great
- 16:37extent. So and it depends always where
- 16:42you sit. It may be worth the cost, it may
- 16:46not. So so yeah.
- 16:50And I think so one question that I guess I think a lot of people
- 16:55think that maybe doesn't get asked that much and there's some
- 16:58really good, I guess like pre hydrogen, there are some great
- 17:02headless experiences on Shopify and for a long time like a lot
- 17:06of the strongest sites in or on and around Shopify have been
- 17:12headless. What are the tangible benefits
- 17:16like I guess like you've you've obviously been building headless
- 17:19pre hydrogen like that beyond the fact that right now beyond
- 17:25the fact that like you say it's kind of better connected to
- 17:28Shopify and there's a lower barrier to entry, maybe less
- 17:31cost. Like what are the other benefits
- 17:35to using hydrogen over, you know, the text app that you
- 17:38might have used pre hydrogen and oxygen?
- 17:43Yes. So for me the biggest tangible
- 17:46benefit is linked being able to use external CMS.
- 17:52So a well managed external CMS is a powerful could be a
- 17:56powerful tool in in in your basically in your full
- 18:03e-commerce. So not only in building site, it
- 18:06could also adapt to your business flows.
- 18:09Just to stop you there like might edit this bit out but I'm
- 18:13asking I've changed the questions like though it's it's
- 18:17actually so I've changed it if you don't mind to hydrogen
- 18:22versus like another headless stat.
- 18:25So if you were building before so you could still use a
- 18:27headless CMS. So you might use like contempt
- 18:30for as part of the environment, but I guess I just want to
- 18:34understand like how much benefit there is to hydrogen over white
- 18:41stack you might have used two years ago, if you see what I
- 18:44mean. Does that make sense?
- 18:45Yes. Sure, sure.
- 18:47Sorry I I just looked at the at the previous version of the
- 18:50question. So yeah, but yeah, sure thing.
- 18:53OK, perfect. So I'm going to edit this out.
- 18:57OK. And then I guess like a bit of a
- 18:59sub question like you 2-3 years ago were building headless sites
- 19:05on top of Shopify and a lot of the stronger Shopify all like
- 19:09size around the shop focus system out there were very you
- 19:12know were headless build hydrogen like in terms of kind
- 19:17of tangible benefits to you as an agency or the merchant like
- 19:23beyond kind of saving time and potentially reducing cost and
- 19:27you know being within Shopify's ecosystem long term like what
- 19:32other benefits are there of hydrogen over you know that
- 19:35stack you might have used two years ago?
- 19:38Yes. So I generally think there if we
- 19:44compare Hydrogen from a technical point of view to other
- 19:48frameworks, I think we'll go into re academic discussion.
- 19:54As I as I mentioned Hydrogen is built on a matured bottle tested
- 20:00framework remix and and there is of course there is a competition
- 20:06with other frameworks but there are no no clear winners there I
- 20:11would say. But what Hydrogen does really
- 20:16really well is that. It makes historically complex
- 20:24features. It solves those complete
- 20:29historically complex features for you.
- 20:31And by those I mean for example Shopify analytics or
- 20:38authorizations and so on. Another thing is that you
- 20:45starting with this team that shows you how to approach, how
- 20:53to approach common e-commerce flows like you know adding two
- 20:58cards or loading more products on a PDPLP side and it offers
- 21:07set of standards that that you can use.
- 21:10So there is much less risk, much less risk of making bad decision
- 21:15there, because that's where I really like your The thing that
- 21:22you're saying very often with great flexibility comes great
- 21:25responsibility and you can still, you still can be
- 21:30flexible, but hydrogen reduces the overhead of making those
- 21:35decisions upfront significantly. So that's one thing.
- 21:40Another thing is oxygen on itself.
- 21:43So a lot of complexities when it comes to build headless sides.
- 21:49It comes to the way you, you post it.
- 21:51There are great services out there that doing really great
- 21:55job and simplifies things. But the fact that you are still
- 21:59inside the Shopify and you don't, you just don't have to
- 22:03worry about it. It just works out-of-the-box.
- 22:06It plays a huge role in in the hydrogen development, yeah.
- 22:15Right. Yeah, actually that's really
- 22:16useful context and this is an interesting one.
- 22:21So I think when people, because there is obviously there are
- 22:23negative connotations in the industry around headless in
- 22:27places and a lot of that comes from when someone has selected
- 22:32or like decided to go down the headless route and they probably
- 22:34shouldn't have done or if you know it's a badge fit, etcetera.
- 22:37Whereas I think James and I always say like there's
- 22:40definitely a place for headless. It's just a case of aligning it
- 22:44with the business case and also the team and just making sure
- 22:49people kind of understand the pros and cons.
- 22:51But a lot, most people would say one of the big cons for headless
- 22:56is that you don't have that same level of access to the app
- 23:00ecosystem. But a couple of things that you
- 23:02said in the notes ahead of the episode made me kind of think a
- 23:06bit more about the negative side of the app ecosystem I guess.
- 23:12And you know some of those kind of pre built widgets and you
- 23:15know JavaScript heavy widgets, I guess what could you just talk
- 23:22us through that I guess and like yeah maybe some of the pros to
- 23:25not using the app ecosystem? Yeah, Yeah.
- 23:30So at the beginning I just just want to address the thing that
- 23:37you still can benefit from the app ecosystem when when when
- 23:41you're headless mostly those that that leverages or
- 23:49orchestrate the the, the Shopify back end, you of course most
- 23:55like you won't be able to use ready ready made widget.
- 23:58That's not always the true. I think a good example is Clavio
- 24:03there that you can just use almost out-of-the-box and not
- 24:08use any of the capabilities there.
- 24:10You can still build your pop ups in Clavio and show them on the
- 24:14headless side, but what are the concept of this app ecosystem?
- 24:20So this prebuilt connectors will only get you this far.
- 24:24So there they will always be generic.
- 24:28They will also assume, they will always assume or will be
- 24:34targeted or wider wider e-commerce flows, wider used
- 24:39e-commerce flows and most often merchant.
- 24:46You don't want out-of-the-box experience those those widgets
- 24:51offer. So on one hand you you benefit
- 24:58from one click install but then you have to build on top of it
- 25:02and there is no robust and most often there is no robust way of
- 25:08doing that. So what you do is you basically
- 25:12hack around those those widgets, and by that I mean you for
- 25:19example, you apply a custom styling, custom styling to those
- 25:23widgets to feed them more into your site.
- 25:28And if they don't offer a managed way of doing that, you
- 25:35basically try to find a way around the system and it and in
- 25:42time, it's in time it will change.
- 25:45We saw those cases very, very often that there is a widget,
- 25:52rhythmic widget. Some developer applied the
- 25:55styling on it and the developer on the of the application of the
- 26:02app decided that OK, it's time to update the app, it's time to
- 26:07to to to to change something. And those changes, those custom
- 26:11changes to styling no longer applied to and it break the
- 26:16side. And there is no way of knowing
- 26:18that upfront and there is no way of mitigating that.
- 26:23So more more often they're not those those apps will work
- 26:33out-of-the-box only if you use them exactly as they were
- 26:40intended to and that's typically that's where what what merchants
- 26:44want and then you you lose the value proposition of those well
- 26:50one one click install hubs. So the reliability of them and
- 26:55and and reducing the overheads when it comes to maintain those.
- 27:03That makes sense. I think 1 interesting point that
- 27:05I took from that, that I guess again, you probably don't hear
- 27:09talk about too often. And our average kind similarly
- 27:12to you is a premium fashion brand.
- 27:14And I think I guess there is a benefit to like forcing you to
- 27:19think about how you want the front end to be styled for all
- 27:23of those kind of different apps or third parties.
- 27:28So you kind of almost calm, just layer Soleil and stool like a
- 27:32Yachto widget and stick with the base styling.
- 27:35So, yeah, I think that's interesting, particularly what
- 27:37you're trying to create a very unique kind of brand experience.
- 27:42And that's that's only on the you know on the front end part.
- 27:45But what what if you would like to adjust the flow of such of
- 27:53such ready made integration and the rent is that you either
- 27:58cannot and you have to compromise there or going around
- 28:02is a very complex solution 1-2 to initially create and two to
- 28:08maintain and most likely we'll have to integrate third parties
- 28:14just to go around those third parties and so on.
- 28:17So essentially you you are in the same same space of
- 28:25complexity as you could be with Catalyst, but you've you can't
- 28:30do it in a managed way and you cannot control it, you cannot
- 28:36monitor it. That's that's where the.
- 28:41So I would even say that those apps are more targeted towards
- 28:49smaller margins that experiment and still looking for their way
- 28:55of doing things, but they are, they're not mature technical
- 29:04solutions that that could be extended in a reliable way.
- 29:10Yeah, that is that is interesting And the way that
- 29:13Riverside that we're using to record this podcast works.
- 29:16I don't know if you've noticed this Michael, but essentially it
- 29:20like pauses sometimes, I can't always hear what you're saying
- 29:23all the way through, but when it then when it's uploaded it's all
- 29:26kind of recorded locally it's it's perfect.
- 29:28So I might have missed some points, but one thing that that
- 29:32actually reminded me of as well is that a lot of the bigger
- 29:35merchants that we've worked with the been on Shopify actually
- 29:39haven't used any of those front end or many of the front end
- 29:43widgets anyway. They've like built their own
- 29:47kind of widgets of in theme and if you choose the API so like a
- 29:50yacht, PO, whatever else and like kind of like what you're
- 29:53alluding to that gives you a lot more control and yacht PO in
- 29:56particular or reviews in particular, then you've got more
- 29:59ability to do like server side rendering etcetera.
- 30:02So yeah, totally get that. And I guess this is the
- 30:06interesting question that kind of you know, always comes up
- 30:09when you talk about headless. So realistically you know if you
- 30:14were £10 million fashion brand, £20 million fashion brand and
- 30:19you are comparing apples for apples, liquid will allow you to
- 30:25do things faster because you've got you know a number of kind of
- 30:28people, all of these third parties got prebuilt connectors,
- 30:31you know they're probably easier to support, the environments are
- 30:34going to be really similar etcetera.
- 30:36But how big a difference do you think there is in terms of like
- 30:40the time it might take to introduce, you know, something
- 30:42like a Nosto or anything else that's going to be quite front
- 30:46end orientated? I think honestly there is no no
- 30:52clear answer to to that question and it's always was done.
- 30:57Yes, there is a lot of variables and it all boils down to to
- 31:01nuances. I I think it's also worth
- 31:05setting up a baseline when it comes to to headless
- 31:09implementations like so. So you know if we're not talking
- 31:15about very custom site wide integration or multi level
- 31:23integrations with services, we just want to consume some data
- 31:28from a service and show it. It's typically not a big, big
- 31:33development task. It could, it's rather days of
- 31:36development than than weeks. So yes those integrations, those
- 31:44integrations will be much faster when it comes to installing
- 31:49them. You can just basically install
- 31:52them from from the Shopify back office and and you should be
- 31:57good to go. But if you would like to adjust
- 32:04those, it may, it may be the case that it will take longer
- 32:11and the result will be worse than writing it from the scratch
- 32:16using API and so. So I think it's very much case
- 32:22by case and it's very hard to do to have like a generic rule for
- 32:27that, but it it can also be the case.
- 32:31I think the biggest difference there is not when you initially
- 32:37create such experience either through one pre built connector
- 32:42or or you you do it custom. I think the biggest difference
- 32:47there is when you thinking about maintaining it.
- 32:53So what headless ecosystem offers you is, is a way of the
- 33:03maintaining those. Those integrations will be could
- 33:11be more robust or more reliable. In a headless headless
- 33:16architecture it boils down to to wider toolkit when it comes to
- 33:21you know, automatic tests of your code or testing your sites
- 33:27or monitoring your site if it works or not.
- 33:32It also boils down to when and of course I'm assuming
- 33:36optimistic scenario there. But if you initially if you're
- 33:40initially connected through the API to to some kind of a third
- 33:45party and you've done it right, maintaining it will most likely
- 33:53cost less and extending those functionality because it one
- 33:59you're in the control, two you wrote it in a minuteable way and
- 34:10there is usually a wider set of toolkits for for those.
- 34:15Another thing is that those APIs, especially if we are, if
- 34:21we are talking about established services like you know you've
- 34:24mentioned yottpil for example, those APIs are mature, they
- 34:30don't change often. If they change, they have a
- 34:33deprecated period. They you you know about when,
- 34:38when it stopped working, when it will stop working.
- 34:41You have time to adjust and those changes aren't critical.
- 34:46So they if you are talking about mature solutions like that, they
- 34:51are very, very developer friendly and they're thinking
- 34:54about upwards compatibility a lot.
- 34:59And so that makes sense. And I guess the big question for
- 35:02me that I've always wondered and I think you, I know you and Liam
- 35:05have talked about this at length is like what do you think the
- 35:09long term play for hydrogen is? Because the way that I look at
- 35:13it is, I think that you're going to end up with online store
- 35:18going more low code, no code, getting a lot more control
- 35:22within sections, a lot more visual editing etcetera.
- 35:25And essentially the complexity around that coming down.
- 35:28And I guess then hydrogen then represents the more flexible
- 35:34side for more enterprise merchants as you say.
- 35:37But do you see it being more connected to some of the third
- 35:41parties that are like key, Sorry, we can leave.
- 35:47Yeah. So do you see it being more
- 35:50connected? Like do you see people building
- 35:51out like connectors for hydrogen?
- 35:54Like how do you think Shopify wants it to look in like 2 years
- 35:57time? Yes.
- 35:59So I have a couple of thoughts around it.
- 36:02So I think to be honest, it's already pretty, pretty well
- 36:07connected. More on that in a second.
- 36:12Second photo is that it's a typical, you know, chicken and
- 36:16egg problem. More people have to start using
- 36:20so, so more people will will start using it.
- 36:24But with hydrogen, I think hydrogen is a very good, is in a
- 36:30very good position for that. It boils down to the fact that
- 36:37we we already spoke about that, but Hydrogen is just a front
- 36:40face of a bigger architectural change.
- 36:42So writing a Hydrogen starfront means that you know how to write
- 36:49checkout extensions. It also means that that that you
- 36:53know how to write a custom app for Shopify or you know a panel
- 36:58for custom discount that you brought using Shopify functions.
- 37:03So in a way this set of capabilities needed for building
- 37:09Hydrogen, Hydrogen solution is also needed for much wider in
- 37:19the Shopify ecosystem. So and most likely tech partners
- 37:24or agencies will be familiar with this technological stack.
- 37:28So so it's it's a rather clever clever idea.
- 37:33There also what Shopify done in recent years with this
- 37:39architectural change is that they modularized and open up
- 37:44their their own APIs, their own systems.
- 37:49So historically Apps if you would let if you wanted to to
- 37:55create more custom flow and you installed the app.
- 37:59Most likely this app took the data that it could from the
- 38:03Shopify, does some business logic on on its own and then
- 38:08maybe came put the data back into the Shopify.
- 38:13Right now those apps are much, much lighter and they're just
- 38:20orchestrating the internal Shopify systems and Shopify
- 38:26recreated their architecture so there is much more communication
- 38:31through the APIs and so on. So at the same time Shopify app
- 38:37developers are also more acquainted with you know,
- 38:41Hydrogen with API, first bids and so on.
- 38:46So and on that matter, Shopify apart from creating Hydrogen,
- 38:55creating Hydrogen is also investing a lot in into external
- 38:59solution. A good example is sanity which
- 39:02is like by by by Shopify. It's a headless CMS and they've
- 39:09also built this prebuilt connector that allows you to put
- 39:14your product catalogue and collections inside the inside
- 39:18the sanity and you can extend this e-commerce data with
- 39:22editorial data. So from what I see Shopify is is
- 39:29turning into that direction not only by creating Hydrogen but in
- 39:35more general way and there is also an outside of the Shopify,
- 39:45outside the fact outside of the Shopify that a lot of developers
- 39:50and a lot of talent around the front end is invested into the
- 39:55headless space and even outside of the e-commerce.
- 40:01I think e-commerce is a is a bit of a special case in development
- 40:06world. So outside of e-commerce are
- 40:11very we think about non headless solutions very very rarely.
- 40:16So I would say headless solutions are quite standard
- 40:20approach to how you build things, you know using Remix,
- 40:24Hydrogen Remix or XS or React and so on.
- 40:31And a lot of talent is already familiarized with that
- 40:37technologies. So yeah, I think it will only
- 40:43grow. They of course there is a risk
- 40:47and it has to be accepted by the by the Shopify ecosystem and by
- 40:53that I mean app developers but also businesses.
- 40:58There has to be more messaging around it and more clear
- 41:02communication around it, better best practices and so on.
- 41:08But generally thinking they're they are in very good path
- 41:13there, yeah. One one thing that reminded me
- 41:19of that, again I've spoken to a few people about in the past, I
- 41:23feel like with the new architecture, there's such big
- 41:26opportunity for agencies to build more IP and kind of build
- 41:30out more accelerators like you see in Salesforce and Adobe
- 41:33world. Yeah, because particularly you
- 41:36know functions, checkout extensions but also hydrogen
- 41:39like it just feels like there's such an opportunity to like
- 41:41productize more and kind of like you say around hydrogen
- 41:46generally like reduce the barrier to entry a bit.
- 41:49So I think kind of almost last question, so two are kind of,
- 41:52the last two are kind of connected.
- 41:54That's another thing that I've always not enjoyed of headless
- 41:58and this is more pre hydrogen, but it feels like because of the
- 42:05flexible nature of headless you can be a lot more kind of
- 42:08opinionated and there's a lot more room to build bespokenness
- 42:11into that kind of front end stack.
- 42:15And as a result, often there's like an element of age of
- 42:18Sirlofkin and it's a lot harder to leave an agency and also
- 42:24another agency may not even be kind of the right fit to take on
- 42:28that codebase. What's your view on this?
- 42:31Like, do you think this exists around hydrogen and how do you
- 42:35how would you suggest that could be avoided?
- 42:39Yes. So it's it's a bit connected to
- 42:45to to everything we we already talked about.
- 42:48So if you go with hydrogen you have to make a ton of decisions
- 42:55about basically everything about what kind of technology you use
- 42:59for styling, what kind of technology you use for ACMS, how
- 43:05you fetch the data and so on. There's ton, ton of different
- 43:09decisions and you have to have a really responsible, really
- 43:16experienced partner for those decisions to be right.
- 43:21And the the the amount of points where you can make bad decisions
- 43:26is much bigger than than liquid for example.
- 43:30So what Shopify I think is doing is that together with Hydrogen,
- 43:40but also with all of those other decisions, they are introducing
- 43:45a set of standards or a set of or like a standard e-commerce
- 43:50composable stack. So on one hand you have Oxygen
- 43:55for hosting. That's one decision not to make.
- 43:58On another hand you have Hydrogen.
- 44:03Hydrogen also offers a toolkit how to fetch the data, how to,
- 44:09how to load the data, how you should handle the
- 44:14internalization and so on. Then you have sanity which is
- 44:19big solution there and it will only only grow.
- 44:26The same goes and it's also wider set of things like there
- 44:31are standard approaches to things in Shopify.
- 44:34Warp like table is an industry standard solution.
- 44:38Then you have, then you have Yep, for example Nos and so on.
- 44:46They're they're very popular solutions there and it's
- 44:50reducing the overhead of that those decisions.
- 44:53So it will also be much harder for agencies to came up with
- 44:58their own solution when you because you have to you have to
- 45:05have a reasons to to to go outside of the proposed solution
- 45:09by the shopping Shopify way. Historically that that wasn't
- 45:15the case. Everything has to be done custom
- 45:18and basically you you rely on the agency and there were there
- 45:23were reasons for that like even two years ago you weren't to do,
- 45:30you weren't able to do a proper filtering using Shopify and you
- 45:35have to and you have to make it custom.
- 45:38So and that's not the case today.
- 45:41So apart from that we have to also take into account that a
- 45:48lot of standard e-commerce functionalities are now done by
- 45:54Shopify. I think good example is search
- 45:58and discovery. So not so long ago if you were
- 46:03headless and you wanted to to create a good search experience,
- 46:07you had to choose a third party solution for that like let's say
- 46:12Al Golian and so on which could be overhead.
- 46:18Right now you you have more and more native solutions from
- 46:22Shopify and you don't have to make that decision.
- 46:24So yes I I am going to repeating myself.
- 46:30I think Shopify is not only offering you the Hydrogen as
- 46:36just the front end framework, it just offers you a set of
- 46:40solution for or set of best practices for building or
- 46:45composable converse. That makes sense.
- 46:48I think one other trend that I've seen recently is a lot more
- 46:51third parties are building out documentation around integrating
- 46:56with hydrogen and I've seen that even with the smaller ones as
- 46:59well. And it's something that all of
- 47:01the kind of tech partners are thinking about.
- 47:04So I think that will help. And then the last point, so
- 47:07again your notes ahead of this episode, you talked about the
- 47:11need for more of kind of a base theme I guess within the
- 47:15hydrogen arena or environment, let's in the same way that Dawn
- 47:21is with Liquid, I guess like do you think this is something
- 47:25that's going to happen and what what are like the main reasons
- 47:28you think this isn't it? Yes.
- 47:31So more often they're not those very important decisions are
- 47:38made through seamlessly small small things and a big part of I
- 47:48think or a standard flow of of creating the the site on Liquid
- 47:55is starting from a Dawn team Every everyone is doing that and
- 48:03we are this bug that outside of the Shopify, the developers are
- 48:07very well acquainted to handle us.
- 48:09But the big challenge for Shopify nowadays is that there
- 48:14are a lot of developers that are strictly invested into the
- 48:17Shopify ecosystem and that means Liquid and they have to, they
- 48:23have to make it easier for them or easy for them to to switch to
- 48:28this new technology or to get familiar with this new
- 48:30technology. And the starter team plays a
- 48:35huge role in that like. So it's a completely different
- 48:41start if from day one you already have a functioning
- 48:45e-commerce in a basic in a basic way like you can show the
- 48:50products on PDP, you can show the the each product on PDP, you
- 48:55can add the card and go to checkout and that's what you get
- 48:58from day one. It's a great learning resource
- 49:02and you can just build on top of it.
- 49:05So it it reduces unwanted and dismantle overhead you have to
- 49:12do you that that comes with you know learning here things but it
- 49:19also reduces the stress and the risk that that those developers
- 49:24may may feel about this new technology And in in a lot of
- 49:32cases this those decisions are developers has have a very big
- 49:40impact on those decisions. It's not only a business
- 49:44decision, more often they're not it.
- 49:46It it also very much a development or technological
- 49:50decision there. Great.
- 49:54And that, that concludes the episode.
- 49:55So I think we've covered a huge amount in this episode.
- 49:58And thanks so much for agreeing to come on.
- 50:01Yeah, I've always been super impressed with you guys and I
- 50:03don't think many people have done more than you have with
- 50:06hydrogen. And I think, yeah, your work
- 50:08definitely speaks for itself. Magda Butcher.
- 50:11And what's the other side? I was trying to remember
- 50:13earlier, by the way. And so final question, I guess
- 50:17like if people wanted to reach out to you and talk about kind
- 50:19of hydrogen and headless or even discuss a project or anything,
- 50:23how could they get in touch with you?
- 50:25Yes, so please, please visit oursitecommerceui.com.
- 50:31We and you can contact us really easily from there.
- 50:36We are also very close to to actually publish a site around
- 50:40the hydrogen on itself that will demystify a couple of things
- 50:46around it and we'll also, and we are more than happy to, to do
- 50:52our consultations around it and discuss it more in depth.
- 50:56Lovely. Perfect.
- 50:57Well, yeah. Thanks everyone, for listening.
- 50:59As always, we really appreciate any kind of likes or follows all
- 51:02of that kind of stuff. James usually ends the episodes,
- 51:06but yeah, thanks for listening. And we'll release another
- 51:08episode next week. For more information on this
- 51:19topic, head over to Replatform dot FM for our audio podcasts to
- 51:23discuss a project, or if you'd like to chat about any of the
- 51:25topics covered in this episode in more detail, please reach out
- 51:28to myself, James Kurd, or my Co host Paul Rogers via LinkedIn
- 51:31and Twitter. Thanks again for listening and
- 51:33keep your ears peeled for the next episode.