Storefront architecture and platform choice

In short

How the storefront itself is built — headless versus themed, rendering strategy, framework choice — and what each of those decisions costs you later in performance and in maintenance.

4 pages

definitions

Four caches sit between your product page and the shopperBuild output, the edge, the browser and the in-page store. You can purge the first two on demand and only expire the other two — which is the rule every caching decision follows.definition7 min
The cart token: the one object a storefront can never serve from cacheThe cart token carries identity, not contents. Once you see it that way, cached cart fragments and merge rules that silently discard items stop being surprises.definition7 min
The public storefront token: what a shopper-side key can readA storefront credential is safe because of its scope, not its secrecy. It ships to the browser by design — so the only question that matters is what it can return.definition7 min

diagnostic

Your product page's largest element arrives last on mobileHalf the time the largest element on a product page is not the product shot at all. Identify it first, then the fix is either an image-pipeline change or a script-order change.diagnostic9 min

Working on something in this space?

Tell us where you are in a sentence or two. We'll tell you honestly whether we're the right team, and what a sensible first slice of the work looks like.

Start the conversation