Scaffold a new Shopify app with the CLI today and count how long it takes to reach a .liquid file. You will not get there. You get a TypeScript project, a GraphQL codegen preset that generates typed operations from the Admin schema, and an extensions/ directory where discount logic compiles to WebAssembly. It reads like an application repository because that is what it is.
The shift was gradual enough that plenty of merchants missed it. Shopify reported $115.57 billion in gross merchandise volume for Q2 fiscal 2026, up 31.6% year over year, with merchant solutions revenue up 37%. The role many companies still advertise as “theme work” now sits closer to backend engineering than to web design.
Key takeaways
Shopify designated its REST Admin API legacy in October 2024; new public apps have required GraphQL since April 2025.
Shopify ships a dated stable API version quarterly, each supported for at least twelve months, making upgrades a scheduled cost.
Shopify Functions move discount, delivery, payment and validation logic server-side, compiled to WebAssembly from Rust or JavaScript.
Metafields and metaobjects are a real schema layer; treating them as loose key-value storage is a costly mistake.
Shopify reports 92% merchant retention above $1M annual GMV and 97% above $10M.
What is Shopify development in 2026?
Shopify development is the practice of building, extending and maintaining commerce systems on Shopify’s platform — themes, apps, server-side Functions, API integrations and custom data models — using the Shopify CLI, the Admin GraphQL API and the platform’s versioned extension frameworks. Liquid templating is one skill in that set, not the whole of it.
The useful test is what a task requires. Restyling a product page is front-end work. Encoding a wholesale customer’s contract pricing so it holds at checkout and reconciles against an ERP is application engineering.
Why did the Admin GraphQL API replace REST?
Because REST could not express what merchants were asking for without dozens of round trips. Shopify marked the REST Admin API legacy in October 2024 and required new public apps to use GraphQL from April 2025. One query can now fetch a product, its variants, inventory levels and metafields together, against a typed schema.
GraphQL rate limiting is also cost-based: each query is assigned points against a leaky bucket allowance rather than counted as one call, so a badly shaped query can throttle an integration a naive REST equivalent would have survived. Integration work now demands fluency in query cost, pagination cursors and the userErrors pattern that mutations return.
What are Shopify Functions, and what do they change?
Shopify Functions are small programs that execute inside Shopify’s own request path, replacing logic that once lived in scripts, third-party apps or fragile theme code. They cover discounts, cart transforms, delivery and payment customization, order routing and validation, written in Rust or JavaScript and compiled to WebAssembly.
They are constrained in ways front-end developers rarely encounter. A Function receives input through a declared GraphQL query, returns JSON, runs under instruction and memory budgets rather than a generous timeout, and has no outbound network access. The discipline is familiar from embedded work: decide what data you need up front and push asynchronous work to webhooks or Shopify Flow. Much practical eCommerce automation now lives here, as rules the platform executes rather than an app polling an endpoint.
Are metafields and metaobjects really a data modeling problem?
Yes, and it is the part most often underestimated. Metafields attach typed custom data to existing Shopify resources; metaobjects define new content types with their own fields and references. Together they let a merchant model size guides, ingredient panels, vehicle fitment or store locations natively, without a separate CMS.
The difficulty sits in the definitions. Namespaces, field types, validation rules, storefront access and cardinality are decided early and are painful to change once thousands of products carry the data.
Why is Shopify development harder to staff in-house than merchants expect?
Because the job spans four fairly distinct competencies — typed front-end work, GraphQL API integration, WebAssembly-targeted server logic and data modeling — plus a standing obligation to track quarterly platform releases. Merchants budget for one developer, then discover the work needs a team’s breadth.
Hiring signals moved accordingly. The productive interview question is no longer whether a candidate knows Liquid, but whether they can explain GraphQL query cost, describe a Function’s execution constraints, or defend a metaobject definition. Shopify’s reported retention — 92% above $1 million in annual GMV, rising to 97% above $10 million — partly reflects how much operating logic ends up encoded in this layer. Agencies competing on Shopify development now lead with certification and API integration work rather than design portfolios, because that is where the difficulty went.
Plenty of merchants need none of this; the threshold is roughly where business rules stop fitting inside app settings screens.
What maintenance cadence do versioned API releases force?
A quarterly one. Shopify publishes a dated stable API version every three months and supports each for at least twelve months, so every app and integration carries a hard expiry on the version it was written against. Teams that ignore this find out on a schedule someone else sets.
In practice that means a recurring upgrade slot: regenerate types against the new schema, read the changelog for removed fields, redeploy extensions. checkout.liquid customizations gave way to checkout UI extensions, and additional scripts to the Web Pixels API. Both were announced far ahead of their cutoffs, and both still stranded stores.
Does anyone still need a Liquid specialist?
Yes, but for narrower reasons. Liquid still renders the storefront, and Online Store 2.0 sections, JSON templates and theme app extensions all live in it. Performance tuning, Core Web Vitals and merchant-editable section architecture remain specialist skills. What changed is that Liquid is no longer where business logic belongs.
The healthier split is a theme developer owning rendering and the merchant editing experience, alongside someone in TypeScript and GraphQL owning Functions, apps and integrations. Shopify app development joins the two, and is the harder half to hire for.
Frequently asked questions
Do I need to learn TypeScript for Shopify development? For theme work, not strictly: Liquid, CSS and JavaScript cover most of it. For apps, Functions and Admin API integrations, yes in practice, because the official templates and codegen tooling assume it.
Is the REST Admin API still usable? Existing apps can still call it, but it is legacy and gets no new functionality. New public apps must use GraphQL, and anything built on REST accrues migration debt.
How often do Shopify apps and integrations need updating? Plan one review per quarter to pick up the new API version, plus checks after major platform releases. Integrations untouched for a year are the ones that break without warning.
Figures cited are drawn from Shopify Inc.’s Q2 fiscal 2026 earnings disclosures and Shopify’s published API versioning and deprecation documentation.
