Latest / Inside Commerce: Ecommerce Strategy, CX and Technology Podcast / EP179: Front Commerce On How Ecommerce Teams Are Using Its PWA Front-End, with CTO & Co-founder Pierre Martin
Transcript
- 0:03Thanks Allison three platform podcast sponsored by tractor
- 0:05hypersonics. I hosted by me James guard and
- 0:07Mike OS, Rogers and a warm welcome, if it's your first time
- 0:10and thanks for regular service that we both lot of effort into
- 0:12creating this content and bring it to you completely free of
- 0:14charge. Help us keep it that way you
- 0:17know share the episode post it on the social media profiles.
- 0:21Tell other people in your network about it you think might
- 0:23be interested. Please help us get as many
- 0:26listeners as possible and also we'd love a rating on a Apple
- 0:30Spotify YouTube or wherever you listen or watch.
- 0:32It helps boost visibilities that helps bring new people cause so
- 0:35thanks to me. Hope you enjoy the latest
- 0:36episode. So, let me quickly set up for
- 0:38introducing our guests. Our topic today is on front
- 0:41Converses. PW a front end for e-commerce,
- 0:43looking at Market fit. And the reason for this, is I
- 0:47businesses as a grappling with the relevance and impact of
- 0:50evolving technology Stacks to deliver greater flexibility
- 0:53faster speed to Market, get rid of efficiency rather than
- 0:57waiting on, you know standard long.
- 1:00Times you get on Legacy systems. Hey, listen, composable,
- 1:03dominate marketing speak. They're everywhere.
- 1:06There's a lot of interesting and positive speak about it.
- 1:09There's also a lot of information out there which kind
- 1:12of clouds matter. So what we're trying to do is
- 1:14have episodes that help you better understand, we're tipping
- 1:16technology, fits in a type of business it suit because with
- 1:20great flexibility comes great responsibility and through going
- 1:24fully headless, pretty composer with doesn't suit every business
- 1:27and you sometimes need to change your business.
- 1:29This model in order to seek those Technologies.
- 1:32So today, we've got a really, really interesting guests, and
- 1:35we're speaking to a front-end specialist.
- 1:37What we're going to cover is what is front Commerce is front
- 1:40end solution for e-commerce or type of business.
- 1:43Is a headless man in suit and why going to some of the product
- 1:46features roadmap and Integrations.
- 1:48So first it warm welcome to to Christian who is a strategic
- 1:51Partnerships development manager.
- 1:52I Christian Hui, they're doing great bags, thanks for the
- 1:57invitation. So yeah.
- 2:00I'm Android of partnership here at Funko else.
- 2:02Somewhere role is to help the agencies with whom we work to
- 2:05deliver the best possible front end, but they're ecomp
- 2:09customers. And I'm here with care, RC Co
- 2:14and the co-founder Yeah, hi. Nice to meet you.
- 2:20So I'm here in charge of everything technical regarding
- 2:23all this Tech aspect. So the whole text talk about or
- 2:28from gross product and our Cloud also deployment platform and
- 2:34also of course of the product. So like which I could answer
- 2:38some of the questions about the roadmap and how it feeds also
- 2:42for our existing customers and things like that.
- 2:47All right. And I'll ask the first question
- 2:50and so Christian. The first questions T it.
- 2:53And can we just start by talking about your kind of Market
- 2:56positioning? And if you can just summarize
- 2:58kind of swap from commerce's, I guess and the kind of scope that
- 3:01it typically fills for an e-commerce project.
- 3:05Well, yeah, for repairs. So, we're software editor editor
- 3:10over front end as a service, which is a solution dedicated
- 3:14for pecan B2B and b2c. What we do is, we provide
- 3:19foundations, to build Agnostic, Front End.
- 3:24So agnostic from the backend e-comm engine, and you can plug
- 3:28it into any Econ stack on the market, by allowing the benefit
- 3:33like a modern and innovative. Eight of offering to craft your
- 3:37online customer experience. So it's really kind of a new
- 3:43market or very Innovative offering and What Makes Us
- 3:48unique right now in this market of a front end as a service, 23
- 3:53points. First, we will guarantee that
- 3:56all the backend features that are exposed in API, are
- 4:00connected with our solution. Even if this means ensuring
- 4:05updates or a solution, when the back end is being updated by its
- 4:10provider. Second point is our it seems
- 4:13will support our partner developers when it comes to web
- 4:18performance, best practices and code review regarding the front
- 4:24end. So really what is link to web
- 4:28performance? To ensure that our react and
- 4:33graphql developments are done in order to achieve the best
- 4:37possible results. So this means we're also going
- 4:40to provide support. Sorry to the developers are our
- 4:45partners that are putting in place our solution, and we will
- 4:49review, even the code that has been overlaid on our solution to
- 4:54ensure that we respect these best practices regarding web
- 4:57performance, and the languages that we use He reacts mmm, the
- 5:02third part is that we will guarantee that our customers are
- 5:08able to change their back ends whenever they want to, when the
- 5:13time is, right? And this is subject, a subject.
- 5:17We're going to go through a bit later on a dig into is what we
- 5:20call Progressive migration in a nutshell.
- 5:24It means that emergent can change his front end with our
- 5:28solution without touching the back end.
- 5:31And go on the path of composable Commerce.
- 5:34And at the end of The Journey, he can change his back end
- 5:39without too much impact on the front end, because we are
- 5:44agnostic of the back end solution.
- 5:46Well, I think we'll come back to that.
- 5:49So our solution allows Browns to go for composable Commerce, much
- 5:54faster than if they had to change all their econ stack.
- 6:00We just caught the head of the platform, the website and having
- 6:03them to go headless in 3 to 5 months and and the Headless is
- 6:08really the first step to composable Commerce. attract,
- 6:14you'll Complete product Discovery growth engine, create
- 6:17relevant shopping experiences that convert into sales and grow
- 6:20online Revenue with personalized, search
- 6:23merchandising, and recommendation Solutions powered
- 6:26by a I find out more at a tract.com Right.
- 6:31And I'm, I guess following on from that system of you,
- 6:34Christian say as James alluded to f'ing headless, and
- 6:38composable, nowadays is quite a bit, you know, broad area fairly
- 6:42vague. You know, lots of approaches a
- 6:45lot of the kind of vendors involved, have different Scopes
- 6:48and it sounds like your scope is quite broad overall.
- 6:51So can you just talk us through what a typical text at looks
- 6:55like when you're using Funk Commerce?
- 6:57So what other kind of solutions are involved be that?
- 7:01At CMS obviously complex form. Yeah.
- 7:04Any other kind of vendors that would be involved.
- 7:08Well sure, we're going to be kind of in the middle of all
- 7:13these solutions that allowed to provide the best possible hyper
- 7:18personalized service to the online customer.
- 7:23So indeed we are agnostic. We can potentially be guarded on
- 7:26any best of breed Tech solution out there or text stack which
- 7:34are sweets. Nevertheless, we are at
- 7:37Witnessing right now. Des Moines Don customers that
- 7:41have acquired Adobe Commerce sfcc or sap hybris.
- 7:48These customers are lacking flexibility and Agility.
- 7:52When it comes to connecting new channels to their econ stack.
- 7:57And when you know that headless, headless approach will increase
- 8:00your time to Market by an average of 80%.
- 8:04There's no wonder these brands are digging into the subject
- 8:06right now. So apart from these ecome engine
- 8:11Stacks, we could act indeed with major cms's such as content,
- 8:16full, or Prismatic more search services.
- 8:20Such as I'll go Lea, B2B Solutions, such as oral
- 8:25Commerce, for example, and we also support several payment
- 8:29providers, obviously like aliens, try PayPal.
- 8:33There's so many out there we believe that the most mature
- 8:37Sure solution, when it comes to going headless in the past
- 8:44years, we've seen a lot of them all magenta and Adobe customers.
- 8:48And yell, as I mentioned right now, we're seeing an increase
- 8:51and abound on these, what we call Knowledge solutions that
- 8:56are well-known such as sfcc or sap hybris, And only the front a
- 9:08bit react PA. Could you talk us through it a
- 9:10bit more depth? What is the tech stack from the
- 9:12sits on? And and I guess the question
- 9:15most people are giving interesting is is why we built
- 9:17this. Very one of the benefits, the
- 9:19merchants of having this time in terms of like almond speed
- 9:23etcetera. As Christian mentioned, that
- 9:26many of you weird head of headless Commerce, and we've
- 9:30build a platform for front-end developers to build a front end.
- 9:34That's the only entry point into these composable Commerce
- 9:38best-of-breed Solutions. So naturally we chose the
- 9:43JavaScript ecosystem for that because that was what, front-end
- 9:46developers knew more about. And we felt it was more natural.
- 9:51So we went with a react as a or front-end library for building
- 9:58component, based, you is, which is a 10 from Commerce is A react
- 10:03single page application, that's also server-side rendered.
- 10:07So for that we have a node.js server and all the data goes
- 10:11through a unified graphql server, which medically will be
- 10:17composed of every defense Solutions in the back end.
- 10:22And we'll have a unified access to the data for a standard
- 10:27e-commerce application. That means that the front
- 10:29cameras application is a JavaScript Application, which
- 10:33from Commerce, as a dependency, more on that later.
- 10:37But we are currently in the process of delivering a new
- 10:42version of Franco is based on remyxx the remyxx JavaScript
- 10:46framework. So basically, this is a standard
- 10:49application and from Commerce is a dependency.
- 10:52Then you register from Commerce extensions in your application
- 10:56based on the services that you want.
- 10:58So for instance, if you are if you have a Be Commerce, be to be
- 11:04back end that you want to expose and use as a headless
- 11:09application. You will enable our Adobe
- 11:11Commerce B2B extension that we maintain.
- 11:14And we provide over time, then you will mix with the
- 11:18algorithmic search extension, or the priest, Mick and extension,
- 11:22and then you have front and that is able to display on the same
- 11:27page data from Adobe algorri & Precinct and All of that will
- 11:34really seamlessly for the front-end developers because
- 11:38they're creating react components, interacting a single
- 11:43graph of all these data, no matter where the data comes
- 11:46through, that's how we can also do re-platforming in the future.
- 11:51So we do have all those extension.
- 11:53Also, for agent payment, for instance, if you use that, we
- 11:57get analytics for tracking and you have a fully Ation that you
- 12:02can start customizing. As I mentioned, we do provide
- 12:08react component, and even more than that we, when you start
- 12:11from a project, you have a fully working theme and e-commerce
- 12:15theme. That is based on the atomic
- 12:17design principle. So from all of that, you start
- 12:20from a starting point and you start customizing, depending on
- 12:23your custom filters. Exid exactly.
- 12:29Did the point you made about the connectors?
- 12:31We've got a close right, the end the route roadmap where you're
- 12:33headed, we'll come back to that because that's quite an
- 12:35interesting thing. So there are a lot, a lot of the
- 12:37merchants I work with the thing they most Keen about when
- 12:40they're looking to re-platforming is I'll you know,
- 12:42they have two or three solutions.
- 12:44They don't want to change and having I know native connectors
- 12:47on the be all end all, but they do help people trying to fill a
- 12:50bit more reassured. But so of course, you're coming
- 12:54back to you at sheet and we we talked about this before we
- 12:56start the recording, the In the SME space specifically
- 13:00non-enterprise like the prospect of white headless and composable
- 13:03just scares people off because they did sounds impossible but
- 13:07headless as well can be offerings.
- 13:08People think it's just too much, technical complexity, escalating
- 13:12course, I they can't do it if they don't have a big
- 13:14engineering team. So all the love, you can you
- 13:16explain to people? I walked height size type of
- 13:18business fits best with your solution.
- 13:21You know, is it about Revenue size is about technical in-house
- 13:26capability. Yeah, sure.
- 13:30Well we have like three birds gold right now, retail luxury,
- 13:35Brad will be to be generally. The starting point for our what
- 13:40we call our ICP ideal customer project but be sorry, around 5
- 13:48million online GMB. What we're looking at is brands
- 13:54that actually already have an econ business, we also have
- 13:59exceptions because we all see also see Industries and B2B that
- 14:02just launching their econ strategy with a lot of
- 14:05investment and a high high goals to achieve online.
- 14:10So they want to have the best possible e-comm stat from the
- 14:16beginning and they're not yet doing anything online but the
- 14:20majority are Tumors are generally have a GM V online
- 14:24around 5 million. Home and this meaning that they
- 14:30want to go like an extra step. When it comes to flexibility for
- 14:35their business teams, in order to test and learn for their
- 14:41online, customer experiences, we're kinda no in a worldwide
- 14:46now where we have to adapt quickly surprise, online,
- 14:51customers with exceptional, emotions, good, emotions, Good
- 14:55Vibes in Out to not frustrate them.
- 14:59And this is what we're going to be able to achieve with the
- 15:02solution that is dedicated to web performance and a faster
- 15:07time to Market in order to test and learn business ideas.
- 15:13I would say so no specific ready sector.
- 15:19I would say more gmv minimum online right now because and we
- 15:25might come back to this. Slater, we have economic model
- 15:29where we invoice a license to the final customer, and he has
- 15:35the help of course of his agency. 95% of our customers
- 15:40have an agency, a partner with whom, they work that actually
- 15:44build the front end with the customer and will maintain it
- 15:48over time. And met me, bring best-of-breed
- 15:51breaks in this composable approach as you mention the
- 15:56first Step 4 composable. That can be a bit scary is the
- 16:01head nurse approached separating the front, from the back, in
- 16:06order to separate. Everything actually becomes.
- 16:11We can separate the teams that are working on.
- 16:13Both subjects, we can separate the timeline of the projects.
- 16:17We can separate the it language between the two subjects back in
- 16:22front because everything is a big tin ABI.
- 16:26So indeed composable isn't for everybody out there.
- 16:33Um nevertheless we're actually working on different features
- 16:38that will be able to retrieve complexity on the subject of
- 16:46composable. One of the examples is the fact
- 16:50of having multiple service multiple providers for your
- 16:53e-comm stack, might bring complexity and analyzing if one
- 16:58of them isn't respecting Heather that a for example as we're in
- 17:04the middle of all this because we take all the information from
- 17:07the back end. We take all the Three points.
- 17:11We have features that will able to monitor actually each
- 17:18solution that is in the back end to understand.
- 17:20If one is not working as it should be.
- 17:24So yeah, we're moving forward on this part to ensure the final
- 17:29customers that they will have a solution that will not bring
- 17:34more doubts or fear. In order to adopt this
- 17:42best-of-breed composable approach for their econ stack.
- 17:49We might also add in that the fact that brands that come to us
- 17:53also Brands and that are willing to have multiple websites,
- 17:59multiple front ends with only one back-end solution.
- 18:04So, it's kind of a Kind of a machine to build multiple front
- 18:10ends. And also, for companies that are
- 18:14in B, to B, we have an example, we just saw in one recent
- 18:16customer, that's during around 200 million online and he has a
- 18:20multi Market distribution model. So yeah, we can be a good choice
- 18:29in that kind of configuration. Also when you're really Global
- 18:34and you have may be dedicated Front ends per country, for
- 18:38example. Hypersonics helps e-commerce
- 18:42companies make more profit every day.
- 18:46This AI driven platform delivers recommendations for pricing and
- 18:49inventory that lead to bigger profits.
- 18:53Visit hypersonics, dot AI forward, slash podcast to get a
- 18:57free trial. And a nun.
- 19:02One thing I was just going to comment on his arse in
- 19:04background while you were talking.
- 19:05I was just looking at your website and I noticed you were a
- 19:08dvla, which is a brand that I worked with years ago.
- 19:11And I said Gee PMD and I just going to call it out.
- 19:14That's a really nice implementation where you've got
- 19:17its rapid, but there's like loads and loads of Rich content
- 19:21which seems to be managed really well.
- 19:22So, yeah, I thought I'd call that out quickly.
- 19:27And so on to the next question. And so you have a nasal Native
- 19:31beam which presumably is designed to speed up deployment
- 19:35and you know get people operating on from Commerce
- 19:37Buster. Can you just summarize what's
- 19:40included within that? In terms of the core templates?
- 19:42Then also things like the native checkout, filtering, all of that
- 19:46kind of stuff. Yeah, sure.
- 19:49Indeed the main goal of front Commerce and this is our value
- 19:53proposition to vote to developers and to Merchants is
- 19:56that we do provide all the native features available on
- 20:01each platform. So if you choose for instance,
- 20:05Adobe Commerce, be to be because you want to you you want to run
- 20:09your B2B business with that and you want, I don't know.
- 20:13I'll go there because you really want to provide I'd a
- 20:18personalized search with good insights and good suggestions to
- 20:22your customers. Then in front Commerce, you will
- 20:25have that by default and basically our theme reflects
- 20:31that, that means that in our theme, you will have, of course,
- 20:35PLP pdb code page, which least B2B company management.
- 20:41For instance, could check out with the best way to integrate.
- 20:47Payment method. So for instance, if you have
- 20:49some white Edge payments, you will be able to have that when
- 20:53you use our age and connector, you know, all those features for
- 20:57each platform, really, we do that by default.
- 21:00So that means that when you start your front a project, you
- 21:03will customize what existing based on exactly the experience
- 21:12that you want to build and to end with.
- 21:15So, if you want to have a full LED friends, user Journey.
- 21:19You will be able to override every page is but still reuse
- 21:23internal components. So we do have UI components that
- 21:28are that could be reused almost everywhere.
- 21:32But we do have all those base template which is a standard
- 21:36Commerce application that you yeah, that you can see almost
- 21:41everywhere and then by customizing what really makes
- 21:46sense for your Projects, and adding those extra features that
- 21:52is specific to the way this Merchant sales to is customer.
- 21:56Then that's how we aim at accelerating projects because
- 22:01you will only focus on what's needed.
- 22:04And you won't have to redevelop the password forgotten process,
- 22:07for instance, and still benefit from everything that you have in
- 22:12your platform. Because most of the time
- 22:14existing Solutions, only cover the main Teachers or the common
- 22:18features of each platform and if you want to to use a very
- 22:23specific configuration that be Commerce has and notes Adobe for
- 22:27instance, then you will have to do it yourself and it's the
- 22:30agency that we live to maintain it over time and also additional
- 22:35costs for the merchants. So that's why we really take
- 22:38care of all these these basic features or integrators And I
- 22:46think correct question that I always come up against from when
- 22:49businesses have on using like headless setups and on used to
- 22:53this the approach. It is what war interracial
- 22:57started with development skills. Do we need rather than from the
- 23:00providing no more than agent. I'd love to hear.
- 23:03Be a like can you talk straight? My understanding is you don't
- 23:06you won't need a full stack developer because you're
- 23:09handling all of the backend API integration work and with all
- 23:12the third parties. So What will your
- 23:16recommendations I walk resources should an e-commerce business
- 23:19have inhales to make working with front Commerce, the most
- 23:23positive and productive experience.
- 23:25Yeah, again here it really depends on the context of
- 23:29existing teams for the merchant or agencies.
- 23:33And also the solutions that you choose because for instance, if
- 23:37you are using the e-commerce or adobe with a custom development,
- 23:42you will like in become Murs, you will not be able to add
- 23:47additional apis, why in Adobe you will have to do that.
- 23:50So depending on that, the team's sometimes will have back and
- 23:54devil girls that could remain at exposing apis.
- 23:58But then you need to build the team that work on the front end
- 24:01of your headless. And for that, as I mentioned, we
- 24:05really try to to be JavaScript Focus because we want to address
- 24:11front-end developers so mostly teams building front rumors
- 24:14project. Franco will be front-end
- 24:17developers. So for that, we, we are based on
- 24:22react. So, obviously, it's a must have
- 24:25to know our react and how to build JavaScript front-end
- 24:29component-based. We use plain CSS with SAS for
- 24:33The Styling. So basically, all the the web
- 24:39developer stack usual stack is needed and will allows you to
- 24:44create date and to customize this front end Theme but then
- 24:49there is the other part that I mentioned earlier about how to
- 24:53access the data, no matter where they come and from different
- 24:57systems. So, for that, we have a single
- 24:59back-end for front-end, which uses graphql and the GS again,
- 25:05it's JavaScript. So, what we've seen is that for
- 25:08querying those data and tweaking them, front end.
- 25:12Developers are skilled enough to do.
- 25:15That and there is a small, maybe entry cost of discovering
- 25:22graphql for instance, if you don't know that, but it's quite
- 25:27quite easy to learn. However, if you really want to
- 25:33mix and match data into this graph ql schema, then this is
- 25:36where you have more of a back-end mindset to have.
- 25:42Because here will deal. We're dealing with Fetching data
- 25:46from API with authentication, Sation caching and things like
- 25:50that, but you will never have to create a database.
- 25:55So front end developers, what we what we saw from experience is
- 25:58that the team to run a project? Balu is from Commerce.
- 26:03Can be composer threaten their Wilbur's.
- 26:05That knows how to deal with API and to do this this cold, but
- 26:11sometimes you may need some back-end Developers for the
- 26:15Initial beads and they will be mostly focused on the graph
- 26:18credit card and that's where also you can have an agency or a
- 26:22team of specialized in Judy's kind of projects to help you
- 26:27deliver faster. If it's new for your business
- 26:30and that's a good accelerator and then you can maintain it on
- 26:34track over time, I need to have any clients where they don't
- 26:39have any in-house development at all when it's all done by the
- 26:42agency then. So there, let's never tell any
- 26:44agency. Maintain from.
- 26:47Yeah, we do have very different kind of contexts so for
- 26:52instance, we do have teams, you mentioned the valid but medic
- 26:56they had front-end developers in the house and they have an
- 26:59agency that handles the Magento back-end.
- 27:04And in between some time they help with these graphical Parts,
- 27:07but initially they made most of that and now they're mostly
- 27:12autonomous. But there are other teams that
- 27:15only Have indeed agencies that can also provide more work
- 27:21regarding ux or UI developments also and that can also provide
- 27:28some guidance regarding composable comers.
- 27:30And at some point you also need like Merchants needs also to be
- 27:37helped and 22 other advices regarding where to put each
- 27:42information. Like do I have these He's in my
- 27:46Bigcommerce application, or should I use it in in content
- 27:50fool or should you should I use algo de to save everything and
- 27:54fetch everything from Mongolia for instance?
- 27:56So, it really depends on the context and, and having a team
- 28:00and that that has these, these full view can really help.
- 28:05So, it really depends again on the project and the timeline
- 28:07also, because there is the initial build and the ramp after
- 28:11that. But Christina mentioned earlier
- 28:15by Progressive migration and it's something that I say more
- 28:19and more important in the phase-in of projects where
- 28:22people have Legacy Stacks, which are going to take time to
- 28:25unblock, all they might have a dependency on the e-commerce
- 28:29platform with another project like an Erp and therefore they
- 28:32can't do everything at once. But they have a business
- 28:36limitation in terms of like Yak speed to Market or content
- 28:39management tool in and the business wants to accelerate
- 28:42that part of the project. Can you talk people through
- 28:45about about, I guess? For those who haven't come
- 28:47across it before, what Progressive, migration means.
- 28:51But also how you're seen people adopt this approach when working
- 28:55with front Mmm, you wouldn't yet to put it briefly just in the
- 29:03old days when you had an e-commerce stack.
- 29:07You built your front end either in custom really with a template
- 29:12one. But our customers generally went
- 29:14for custom front ends, you build it works well and then
- 29:20throughout the years, you're going to add custom developments
- 29:23because you're adding a add features are going to do
- 29:26Evolution on your e-comm stack and you do not accumulate
- 29:32technical debt. This technical debt after 57
- 29:37years maybe is totally going to block your business and
- 29:40marketing teams. Because when you're going to
- 29:42want to do something new in terms of customer experience or
- 29:46you acts. Well, most generally, your Dev
- 29:52teens are will say, well, this is actually too complicated with
- 29:55already want to touch what's in there because we don't really
- 29:58know what the impact is actually going to be if we touch this,
- 30:02but we can do it maybe for the in three.
- 30:05And it will take maybe 10 days to do it.
- 30:08And that, that is kind of an issue with time-to-market
- 30:13requested right now, and all the evolution and change.
- 30:16We've had on the past years in terms of customer expectation.
- 30:21So, this is the limitation of Legacy system when confronted
- 30:26confronted to business and marketing issues, And this is
- 30:32the old way of doing it. You had your e-comm sensor.
- 30:34What did you do? Well, after 57 years, when you
- 30:36changed everything and you put in a new modern style, may be
- 30:39built a new custom front end this fist as a new error now,
- 30:44which is actually what we call Progressive, migration, meaning
- 30:50you can now go for a change in your econ stat.
- 30:55Bit by bit Parts by Parts in order to mitigate risk in order
- 31:01to to have kind of an agile approach in the change of your
- 31:07econ stack. Hmm.
- 31:09So what we're seeing right now is Liga, see customers that are
- 31:16lacking flexibility. There will say, okay, well first
- 31:21step is actually to chop the head.
- 31:24So take off the website, the e-commerce website and put in a
- 31:28solution that is really dedicated to Performance and
- 31:32time to Market. When we say web performance, we
- 31:36mean obviously will speak but also traffic, bounce rate
- 31:41conversion rate. Everything that is actually
- 31:44linked to customer experience some business kpi.
- 31:48I've so first step is to change the front, you put in a new
- 31:53front end, that is agnostic that has an API layer and that will
- 31:57allow to connect best-of-breed Solutions so fast, step you
- 32:01Change the front end, this will probably take between three to
- 32:04five months are with a solution such as ours.
- 32:08Once you've done that and what we see with the customers that
- 32:13take up part is they will generally change the search
- 32:17solution after having changed the front and having a new
- 32:21customer experience in terms of hyper personalization.
- 32:26So then they'll change the search engine.
- 32:29We have great traction right now on On a Gaya.
- 32:32For example, ands the Second Step will probably be to change
- 32:36the CMS and bring in a best of breed CMS, Bailey contentful.
- 32:45And this is how you go step by step on microprojects on
- 32:50dedicated functional parameters. And this is how you actually
- 32:55secure your migration to a new modern stack.
- 32:59Because if we, if we rewind on the first step, which was
- 33:04chopping the head and putting a best-of-breed front-end dance,
- 33:07that takes three to five months will impact positively your
- 33:11business. We mentioned, do get it.
- 33:15We have three kpis for the vad. We have the traffic that
- 33:20increase by 25% and the conversion rate that doubles in
- 33:2816 weeks. That was the timeline of the
- 33:30project of changing. The front end 16 week and a much
- 33:35better scores on a tool from Google which is like house that
- 33:40will analyze their web performance of your website in
- 33:42terms of speed. So yeah, that's what we're
- 33:47seeing right now and obviously it's that stress that's risk
- 33:53less Workforce and having an impact very quickly on your
- 33:59business instead of waiting 18, 24 months and I you know,
- 34:07investing a lot of money to change your Holcombe e-comm
- 34:11stack. The cool part about it is that
- 34:15once you've changed your front, maybe put in a best of breed
- 34:18search. So that CMS, as I mentioned, you
- 34:22can actually change your back end if you want to.
- 34:26You don't have to. And we have both cases with our
- 34:29customers. We have ones that keep their
- 34:31legacy back in another's. That will go for really a 100%
- 34:36e-comm headless stack with Solutions on the back end that A
- 34:42bit more modern, make it big Commerce, Commerce tools, maybe
- 34:48Shopify, these kind of solution. That makes sense.
- 34:53I think James, I talking about that in the background.
- 34:56I think I've definitely seen this trend, but I think where
- 35:01I've mostly seen it is businesses with big teams, lots
- 35:06of stakeholders want to achieve a number of things.
- 35:11And then quite often, they might address a redesign with a goal
- 35:15of achieving, some of their kpis completely overhaul, the front
- 35:20and maybe move to Had left front and stack.
- 35:24And then now come back to the back end because that's a bit
- 35:26more political. More change, you know all of the
- 35:30Integrations. Everything cast.
- 35:31Yeah. Especially when he or peas are
- 35:33involved and the codependency between like the Erp and
- 35:37downstream systems like WMS with the e-commerce.
- 35:40And I'm picking that Phase 1 launch and you suddenly see the
- 35:43operation of people just cry at the thought of.
- 35:47Yeah. Exactly.
- 35:49It also is a change in terms of Of culture inside companies.
- 35:54So having these Progressive migration color, also, help
- 36:00going into and adopting this new culture.
- 36:04And sometimes like when you have any channel experiences, you
- 36:09need also to. Yeah to to have the buy-in from
- 36:12the physical store, owners for instance, and there is all of
- 36:17that that that you need to change it and Technical solution
- 36:21isn't the only The only thing to drive in mind, we are taking our
- 36:25people, so we are talking about that but then that there are a
- 36:28lot of other changes and politics to indeed that might
- 36:32come into play here. Yeah, exactly.
- 36:34And what I find interesting about this approach is I've had
- 36:37conversation client so I said you're going to spend a bit more
- 36:39doing it this way but you come back to your point about
- 36:42de-risking. You've got a timeline where you
- 36:44need to be live because the business can execute against is
- 36:47go to market plans. You won't hit that if you wrap
- 36:50in all of the entire Project deliverables into that phase in.
- 36:54You just won't get there. So you accept that actually
- 36:58you're paying for the business efficiency with some extra spend
- 37:01to do that front and bit. First you'll have to come back
- 37:04and then when you move your Ecommerce back and you've got to
- 37:06then do that integration piece for that's fine you've got
- 37:09you've got more of the more the structure set up and the
- 37:12business already self-serving on the new icon, we have tomatoes
- 37:16in the background content management.
- 37:17See all the time, people can't do stuff because things are
- 37:20called coded or they've got the wrong tool.
- 37:22And therefore, they have to wait and use developer time.
- 37:25So actually, then, well, if we can unpack that I'll return on
- 37:28investment or our business cases that spend, that we won't have
- 37:31to make over the next 12 months will Court will cover the extra
- 37:35cost of dual and peace now. Yeah absolutely.
- 37:39And so now this is my next question.
- 37:42So some of the James mentioned and something that cited on your
- 37:44website is and I think you've touched on it as well.
- 37:47Is you've got a major project on where remix at the moment and
- 37:50the goal is to improve. Prove website Lighthouse scores
- 37:55and call Web vitals. And can you just talk us through
- 37:57that project and what the kind of benefit is to your customers?
- 38:02Yeah, so did this project is basically replacing our core.
- 38:10Some core features that we've developed over time.
- 38:14We are Remick. So remix is a JavaScript
- 38:16framework that allows to Medicaid, take care of
- 38:21everything that we call the middle stack of an applications
- 38:24basically the the client and server communication.
- 38:28So whenever users come on the website, Remy We'll take care of
- 38:33serving HTML to them and then when the user will continue to
- 38:37navigate on the client, then it will take care of updating the
- 38:42react application Based on data fetch from Json API for the back
- 38:49end. Okay?
- 38:50So this is something that when we started from Commerce, eight
- 38:54years ago, nine years ago. Now we're getting old search
- 38:58framers didn't exist. So now there is an egg GS which
- 39:02is quite well-known. Also in the in the reacts and
- 39:06the JavaScript, ecosystem and Remick.
- 39:09So those are the main Frameworks out there and they now know how
- 39:15to do server-side rendering. Rooting, tooting also to build
- 39:20application for production in an optimized way and providing a
- 39:24good developer experience. So by replacing our own
- 39:31implementation of That's with this framework that will allow
- 39:34us to and for our customers to focus on our value proposal,
- 39:40being developing features, and ensuring that all of that is
- 39:43performant by default, and accessible by default.
- 39:47So why does it improve performance over time?
- 39:51We've tried to, of course, improve and keep a good
- 39:55performance, but we're building a front front end single page
- 40:01application. And that allows to provide a
- 40:03good user experience and user Journey, but it has the drawback
- 40:08of having a big JavaScript payload and in cold wet vitals.
- 40:14This is now our main bottleneck because JavaScript needs to be
- 40:20parsed by the brawl with her and I won't go much in depth but
- 40:24even though we do server-side rendering, we have optimized our
- 40:28bundle size and stuff. Now we are only limited by Or
- 40:32component into this JavaScript Bender.
- 40:34So what we're doing with this rewrite, I mean this this new
- 40:38version using remix is that the communication to get data from
- 40:44the unified graphql? Schema we know happened on the
- 40:48server. This is the main difference
- 40:50instead of doing it from the front end that will query the
- 40:53graphical schema. We are querying the native
- 40:57remyxx apis. And on the server, we are doing
- 41:00this graphical. Queries.
- 41:03It's a bit technical, so I won't go too much in depth, but
- 41:06basically that allows us to remove a full dependency, which
- 41:09is a graphical client from my word from the JavaScript that we
- 41:13ship to the user. And that means that it reduces
- 41:18our bundle size, which increases and improves the court.
- 41:22Vitals. Also, there are things that the
- 41:26remix team made, I think better than what we did in our core.
- 41:30So there are a lot of Because we're using again, the best of
- 41:35breed tools for each each step. We have a lot of other
- 41:38improvements. I won't detail all of them now
- 41:42and Nessa. You want to discuss it, but I
- 41:44could discuss it for hours but another fundamental changes from
- 41:49this. This new version is that remyxx
- 41:53is embracing web standards. So standards web API that right
- 41:59now are supported by most. Of the, the existing browsers,
- 42:05and they're providing some apis on top of that, that, that want
- 42:11to promote Progressive and then spins.
- 42:14And that means that for editors. Like, as we don't have also to
- 42:21to use several additional dependencies and we can just use
- 42:25the web as it was planned to do. Which again reduces the amount
- 42:30of JavaScript that we ship to the Wowser and for the other
- 42:33ones, we use the remix Primitives for that.
- 42:36So using the web also is a really nice trends that
- 42:40everybody is doing because when we started from covers, nine
- 42:44years ago, browser didn't have such reshape reach apis also.
- 42:49So that's also another part of this this new remix version that
- 42:55allows to have better performance.
- 42:57Right. And I'm next question.
- 43:00So one thing I really like when working with kind of tech
- 43:03Partners or vendors is when they have like a really strong
- 43:07service layer or kind of governance layer so that you
- 43:11could one get the most out the product and also just prevent I
- 43:15guess technical issues or poor implementation Etc.
- 43:19And I always use a cuvette. As a really good example of this
- 43:22narrow Magento hosting company, but they essentially kind of
- 43:25govern deployments. And, you know, all of The code
- 43:28that's been written excetera and it sounds like you have a very
- 43:31similar thing. Can you explain how you do this
- 43:35and then how your team operates? Yeah, of course, as I mentioned,
- 43:40Franco Bruce is only aimed at enabling a teams to build a does
- 43:46Endless Commerce projects. So we really see us as the
- 43:52technique the technical part of Commerce project.
- 43:58But on top of that, there are agencies of developers that we
- 44:01work to develop features that the merchant needs based on what
- 44:05they know from their users. So everyone here As its
- 44:08responsibilities and our is to help with the technical aspects
- 44:13like you mentioned. So we try to do that with an
- 44:15initial training for the developers and the teams to show
- 44:19all the ways they can extend from Commerce to achieve
- 44:22whatever they want. Then we do, should we provide
- 44:26supports. Also with a dedicated slack
- 44:29Channel when you build the project and we can do some
- 44:32meetings and screen sharing to really ensure that.
- 44:37Again, they spend time on their specific features and not on
- 44:45debugging things in JavaScript or in front cover.
- 44:48So really that, that happens all all like that during the
- 44:52project. But of course, every projects
- 44:54have deadlines, Merchants have budget.
- 44:57So you need to prioritize features Barracks or a deadlines
- 45:02also. So what we really want to do is
- 45:05before the project goes live, the Shall be love that project
- 45:09is that we run a no Deeds under the whole website to ensure that
- 45:13first, the project we don't have any issues regarding performance
- 45:20and each will be able to eundel all the traffic that the
- 45:24merchant expect. Because that's the main of
- 45:28pulls, the main goal of any project because if it's
- 45:30beautiful, if it has all the features, but you can, you can't
- 45:34have Androids customer on black. Friday or thousands customers at
- 45:40that time then it doesn't mean anything.
- 45:43So this is the first point and then we are also starting to
- 45:46look into how customization and extensions have been made into
- 45:53the project to ensure that it's maintainable over time and on
- 45:57the long run because as we mentioned, investing in a new
- 46:01front, end means that then you can start additional projects
- 46:04for the rest of you stack and what we want.
- 46:07That Bronco bombers project will Outlast your different back-end.
- 46:11So then from this initial build, you will do some iterations over
- 46:16time with new features Improvement.
- 46:19And basically these audits is exactly that we provide a list
- 46:22of the most priority and most important points that needs to
- 46:28be really tackled before going live and then all the other nice
- 46:32to have things that can be then scheduled during iterations
- 46:36after the initial Go life. And our goal here is also with
- 46:41our Cloud offering to provide automated tools to kind of do
- 46:45that regularly, because, of course, we want to prune
- 46:51iterative development. So an initial bodies is only
- 46:54valid for a few months and we need to do that ideally every,
- 46:58every year, or every few months to ensure that the project is
- 47:03best and delivers the best quality of there.
- 47:07Crochet. Go question via a ramp on the
- 47:09commercial side else, could we talked about this as well?
- 47:12Quite interesting that that there's so many so many changes
- 47:15going on in the front and Landscape the e-commerce.
- 47:19And I know you're working with Commerce tools, but Commerce
- 47:22tools, or from tastic to have like a, a, a version of a front
- 47:26end for I guess the mid-market a lot to know why, why does from
- 47:30Commerce see an opportunity in the Commerce tools ecosystem.
- 47:38Sure. I think it's it's the fact of
- 47:41having a ready best of breed of software editor on the front-end
- 47:46aspect with modern and Innovative back ends or
- 47:52composable back them. Stacks, that makes sense.
- 47:57We have, we have committed stools.
- 47:59That has water solution dedicated for front-end.
- 48:03Nevertheless hopeful from what I know, No, that's this solution.
- 48:07Today is only compatible with Commerce tools.
- 48:11So we're not really going to agnostic solution.
- 48:15We have the same kind of model with our sales force, that
- 48:20launched their storefront composable solution.
- 48:24We have maybe pwa Studio that has been built by for Magento.
- 48:31Adobe so, proud of all these niggas.
- 48:34See absence Apart from Congress tools.
- 48:38Have their own solution out there putting up for the front
- 48:42end. We, we can say quite objective
- 48:48me that this is not really a headless approach.
- 48:51When you have a front that is not agnostic from the back and
- 48:56maybe not allowing you to go for this Progressive.
- 48:59Migration because if you change for the front end of a specific
- 49:02provider on the back, it might be complicated to change for
- 49:08another provider on your back. So you're not, you're kind of
- 49:11going to be Tangled a bit. L.
- 49:13And we like to believe that we have probably the most mature
- 49:17solution out there when it comes to administer 30.
- 49:22And, and the goals were aiming for with our solution, meaning
- 49:29that the best possible front-end experience and flexibility
- 49:33provided. So the merchants are with whom
- 49:35we work. And actually this is kind of
- 49:39also in our model or licensing model we're ready a
- 49:42best-of-breed provider for front end Solutions.
- 49:47So our aim is with performance and we actually have three kind
- 49:52of customers in our vision. We have Developers for whom, we
- 49:57have to allow them to gain time and have a smile.
- 50:01When they're actually working on a solution.
- 50:04We have the final customer that is on the line.
- 50:07Has to have no friction seamless experience and be surprised
- 50:12actually with the capabilities that can be offered by this
- 50:15technology when building hyper personalized, our journey.
- 50:21And we finally have obviously the merchants that has business
- 50:25goals and business. Haines for this.
- 50:28So everything was we do is actually servicing these three
- 50:32kind of customers for example in or model or a column.
- 50:37Ah, Mick model, everything that serves these customers is
- 50:43included in our license. So we will have a hosted
- 50:47solution. It's also scales we can bring in
- 50:51see Ed CDN, if necessary. I'll all these are architecture,
- 50:57it aspects that are at the service of web performance,
- 51:02although we will also ensure that when there is upgrades from
- 51:06the backend, these upgrades will be done Allure solution,
- 51:10allowing the developers of our customers agencies, not to have
- 51:17to discover this and Andre Bill staff because the upgrades are
- 51:22insured by from colors. And this also allows us to
- 51:26guarantee and to engage and to be accountable are for the
- 51:31result. Of the perception you have when
- 51:35going through the front end of our customers.
- 51:39And so it links with the audit we do when, once we did the
- 51:41build and it links also with the fact that we weren't asked the
- 51:46agencies with whom we work for with to actually develop
- 51:53anything. When there is upgrade of the
- 51:55backend solution they're using. Great.
- 51:58And then on, I guess last question from May so Pierre, I
- 52:04guess what else do you have coming over the next 6 to 12
- 52:06months, like to plan to kind of build out the ecosystem around
- 52:09front Commerce. You know, they're more kind of
- 52:12things you've learned into the service layer, more things
- 52:14you're building into the product whilst you have coming.
- 52:18Yeah, of course, a lot of things.
- 52:20We're also start up. So we're adapting fast also to
- 52:25our ecosystem right now, as I mentioned, we're like this is
- 52:30really this year. Major goal for us is this
- 52:36remixed version that will be focused on web birth and
- 52:41developer experience. So we are really here trying to
- 52:44improve by changing this. Just slower than stack by
- 52:49improve the web performance for our merchants and the developer
- 52:53experience for people working with foreign Commerce on a daily
- 52:56basis. So our goal here is to ensure
- 52:59not just that we ship this version because we've already
- 53:02made most of the work here but we want also to provide a good
- 53:06migration experience to our customers because that's also
- 53:10may be a difference between like tools that are front end that
- 53:16that are now. Headed into existing back-end
- 53:19Solutions, is that we do have plans for long-term future.
- 53:23It's not just from your sister, gesture starter that you start
- 53:27with and then you have to maintain over time, we do
- 53:30provide migration for all of that.
- 53:33So our first customers that went live in, in 2018 will be able to
- 53:38migrate to this new remix version and benefit from those
- 53:41web performance things. So we have a lot of tools called
- 53:45modes, documentation and things too.
- 53:47Do here. After dad's.
- 53:52And in the meantime we are also working on nice features for
- 53:58improving the contribution experience in a comfortable
- 54:01Commerce approach because when every data is stored on
- 54:05different Services, when you contribute content we were
- 54:09talking about the culture shift here, you need to kind of have a
- 54:14picture of where the information that you see on the page is
- 54:19managed. And who is responsible for this
- 54:22data. So we do have nice features that
- 54:27allows to streamline this process of contributing, new
- 54:30content and customizing the the customer experience on that.
- 54:35Also as we mentioned we will have a new connect or that not
- 54:41yet fully decided yet and because we're adapting to also
- 54:47our market and what's Merchants. We want It will really depends
- 54:51on on the next next month is and the projects that and yeah, and
- 54:58the merchants that will come to us.
- 54:59But this is definitely plan. And also in the process of
- 55:05improving performance for the merchants, we want with our
- 55:11Cloud front, most Cloud platform that basically allows you to
- 55:15operate from commercial projects in production.
- 55:18We want to support this. Moments culture.
- 55:21So for that we will create new tools for monitoring the
- 55:27website. This Commerce website, when it
- 55:30slide by knowing, which are the services, which are slow, where
- 55:34you have performance issues. And also we want to provide
- 55:40insights about what to tackle next to really improve the user.
- 55:45The end user experience to ensure that teams can focus.
- 55:50On what really matters and with a given with restricted budgets
- 55:55or time frame, they could step-by-step improve
- 55:58continuously their front end. And finally it is also something
- 56:03that we're really looking into. As you saw a I came a few months
- 56:11ago and really is disrupting our ecosystem.
- 56:14So we're really paying attention to that.
- 56:17And for now we are We're aware about AI disrupting the
- 56:24developer experience. When we both all software and we
- 56:27build software we supplied from like s like they used to be a
- 56:31lot of no code applications but right now with judgy and all
- 56:35those new AI assistance coming into the game in your IDE, it's
- 56:41way more easier to just write code and generate it and adapt
- 56:45and iterate from that. So we are also going to embrace
- 56:49this change. And so what, right now, we are
- 56:53exploring that and we'll definitely have some things in
- 56:58the next six to 12 months. He's run that for now.
- 57:02Yeah, maybe also about like, just one thing that's not yet
- 57:07decided, but this is really like to show the vision of a
- 57:11front-end solution like us, is that for now we're providing
- 57:16mobile friendly and Performance front end for users to purchase
- 57:24online. Okay.
- 57:25But going headless mean that if tomorrow users check out
- 57:30differently and they consume online in a different manner
- 57:35with a different user experience from Commerce will allow to
- 57:39bring Merchants there. So if tomorrow, I don't know,
- 57:41people will only place order from a chat gpg plug-in.
- 57:46Then from Commerce will provide the apis, allow you to turn your
- 57:50Front into a child's ability, Plug-In or application.
- 57:53This is also the kind of things that we're going to explore, but
- 57:56right now, the Mark, I mean, we are, we are, awaiting beads
- 57:59about the market to stabilize with that.
- 58:02But we're definitely doing a lot of watch on that main pulldown
- 58:06exist. We are chat.
- 58:07Gbt generated bots, so we don't real humans.
- 58:11The yet the yeah, I'm fascinated by the chat.
- 58:15Gbt they the moment. There's there's definitely an
- 58:18image Evangelical obsessive element that The industry that
- 58:21are trying to push it as the solutions everything but but
- 58:23everyone has to look at where it might go.
- 58:26Don't they know? That's the reality, we've got to
- 58:28understand what the long-term implications will be.
- 58:30But a Christian. Thanks so much for joining us,
- 58:34really enjoyed it. We got a lot of information.
- 58:38I'm it was good to hear you. Talking about merits of
- 58:41progressive migration, I think it's an approach going to see
- 58:43more and more mid-market business.
- 58:44I know Enterprise that this approach with with bigger
- 58:47project management teams, has been there for a while but I
- 58:50think more and more smes are going to actually understand the
- 58:53benefits of taking any more phase approach but and also
- 58:57thanks everyone for listening. I hope you enjoyed it.
- 58:59Do reach out to Christen your Pierre.
- 59:01If you've got more questions or if you want to talk to me more
- 59:03depth around, how front Commerce could work in a particular
- 59:06project, I keep an ear out for a next episode.
- 59:09We drop what every Tuesday so thanks for watching.
- 59:11Enjoy the rest of your day. More information on this topic,
- 59:21head over to re-platform dot. F m, for our audio podcasts to
- 59:25discuss a project or if you'd like to chat about any of the
- 59:27topics covered in this episode in more detail.
- 59:29Please reach out to myself, James guard and my co-host Paul
- 59:32Rodgers via LinkedIn and Twitter.
- 59:33Thanks again for listening and keep your ears peeled for the
- 59:36next episode.