Shopify Development Roadmap: 6 Phases, 48 Weeks
10 min read ยท 2026-10-31
A practical shopify development roadmap starts with web basics: HTML, CSS, JavaScript and Git. Next come Liquid and Online Store 2.0 themes. From there you branch into apps or headless Hydrogen builds, and each phase ends with a project someone can review. If you study part time, plan for roughly 9 to 12 months from zero to your first paid Shopify work. It can take much less if you already build websites.
This Shopify developer roadmap has six phases. Each one has a week estimate, concrete steps and a milestone you can check. You will also learn how to choose between the theme, app and headless paths, which official tools to set up on day one, and what Shopify's script tag deprecation means for app work. The last part is a store project plan, phase by phase, for managers and consultants who plan Shopify work for a team or a client.
The roadmap at a glance
Goal: Go from no Shopify experience to shipping merchant-editable themes and a working app on development stores, then landing paid work. Duration: 9 to 12 months part time (about 48 weeks)
Choose Your Path and Set Up (Weeks 1-2)
Decide what kind of Shopify work you want and get your tools working before you learn anything else.
- Pick a main track: themes, apps, headless or integrations (see the decision guide below).
- Create a Shopify Partners account and open your first development store.
- Install Shopify CLI, Git and a code editor, then connect a test theme to a GitHub repository.
- Write down the three projects you want in your portfolio by week 48.
Milestone: A development store running a theme you can preview locally with Shopify CLI and push from Git.
Web Foundations (Weeks 3-10)
Build the HTML, CSS and JavaScript skills every Shopify storefront depends on.
- Write semantic HTML for a product page, a collection grid and a navigation menu.
- Build responsive layouts with Flexbox, CSS Grid and mobile-first media queries.
- Learn modern JavaScript: DOM events, fetch, promises and async/await.
- Commit every exercise to Git and use the command line daily.
- Rebuild a real product page from a screenshot with no framework.
Milestone: A static product page with a working image gallery and variant picker in plain JavaScript.
Liquid and Online Store 2.0 (Weeks 11-18)
Learn how Shopify themes turn store data into pages.
- Learn Liquid objects, tags and filters by reading the source of a free Shopify theme such as Dawn.
- Build sections and blocks with schema settings a merchant can change in the theme editor.
- Work with JSON templates, metafields and metaobjects to show custom content.
- Run Theme Check on every change and fix what it reports.
Milestone: Five merchant-editable sections that can be added to any template on your development store.
Theme Mastery and Performance (Weeks 19-26)
Ship a complete theme that is fast, accessible and easy for a merchant to run.
- Build a cart drawer with quantity updates using the Ajax Cart API.
- Add filtered collections and predictive search with the Section Rendering API.
- Measure Core Web Vitals and Lighthouse scores, then fix image, script and layout issues.
- Handle translations and multiple markets with locale files.
Milestone: A full custom theme for a fictional brand that passes Theme Check and keeps every text, image and toggle editable without code.
Apps and Extensions (Weeks 27-38)
Extend Shopify beyond the storefront with an app merchants can install.
- Scaffold an app with the current Shopify CLI app template.
- Read and write store data through the GraphQL Admin API, with pagination.
- Handle authentication, webhooks and API rate limits.
- Add a theme app extension (an app block or app embed block) so merchants can place your feature without editing theme code.
Milestone: An app installed on a development store that reads products, writes metafields and shows a block in the theme editor.
Headless and Portfolio (Weeks 39-48)
Add the advanced skills larger brands pay for, then turn your work into proof.
- Build a small Hydrogen storefront on the Storefront API with listing, product and cart pages.
- Write three case studies: the merchant problem, what you built, and how the merchant edits it.
- Clean up your repos with READMEs, setup steps and screenshots.
- Apply to agencies and in-house ecommerce teams, or pitch one fixed-scope job to a merchant.
Milestone: Three published case studies and one paid project, trial task or job interview in progress.
Pick Your Path First: Themes, Apps or Headless
Most Shopify developer guides list skills in one long line. In practice, Shopify work splits into tracks, and the right first track depends on the work you want. Choosing early saves months, because you can stretch or shorten the phases above to fit your track.
Use this quick decision guide:
- Themes (Liquid): pick this if you want client work soon. Almost every merchant needs storefront changes, and theme skills feed every other track.
- Apps: pick this if you already write backend or full-stack code and want to build a product many merchants install.
- Headless (Hydrogen and React): pick this if you know React well and want to work with brands that need a fully custom frontend.
- Integrations: pick this if you like connecting systems, such as syncing orders to an ERP or stock levels to a warehouse tool.
Why the Theme Phases Come First
Even if apps or headless are your goal, do the theme phases first. They teach you how Shopify models products, variants, collections, metafields and carts. Your apps and headless builds will use that same data model.
The Tools to Set Up Before Writing Code
Shopify's own documentation describes themes as built with Liquid, HTML, CSS, JavaScript and JSON. Your toolset should match. The official tools are Shopify CLI, which lets you set up, preview, test and share a theme locally; Theme Check, which flags errors and best practice issues; and the GitHub integration in the Shopify admin, which connects a theme to a repository.
Add a Shopify Partners account so you can create free development stores, and treat each store like a client sandbox. Keep one store for experiments and one clean store for portfolio demos. That way a reviewer never lands on half-finished code.
Shopify Development Roadmap for Apps: The End of Script Tags
If an app needs to change what shoppers see on the storefront, Shopify asks developers to use theme app extensions, meaning app blocks or app embed blocks. The older script tag method is on its way out. In its developer changelog post on the online store script tags deprecation (shopify.dev), Shopify sets two dates. Since October 1, 2026, apps can no longer create or update script tags through the Admin API, although existing ones keep running. On March 1, 2027, Shopify will stop injecting script tags into storefronts.
The same post names the replacements: app embed blocks shipped in a theme app extension, or web pixels for scripts that only collect analytics or conversion data. Any tutorial built around script tags teaches a pattern you would have to rewrite.
This also matters for theme developers. Online Store 2.0 lets merchants add and remove sections on any template, and a theme built that way is ready for app blocks. A theme that hardcodes content in templates makes life harder for every app the merchant installs later. Build for sections and blocks from the start.
Performance and Core Web Vitals
Speed is one of the most common reasons merchants hire a Shopify developer, so make it a habit early. Check Core Web Vitals (loading, responsiveness and layout stability) and Lighthouse on every theme you build, before and after each change.
Focus on what you control:
- Serve correctly sized images, and lazy-load the ones below the fold.
- Load only the JavaScript a section actually needs.
- Reserve space for images and embeds so the layout does not jump.
- Review the scripts installed apps add, and remove what the store no longer uses.
Portfolio Projects With a Clear Done Test
Reviewers want proof that you can turn a design into something a merchant can edit, and keep it fast. Build projects that match real requests, and give each one a "done" test you can check.
Present each project as a short case study instead of a bare link. Include a password-protected development store link and a screen recording, since many reviewers will not set anything up locally.
- Metafield size guide: a modal driven by metafields, done when a merchant can change the content per product without touching code.
- Cart drawer with upsell block: done when quantity changes work without a page reload and the upsell product is set in the theme editor.
- Bulk tag editor app: done when it installs cleanly on a fresh development store and updates tags through the GraphQL Admin API.
A Shopify Roadmap for Teams and Clients
If you are an ecommerce manager, project manager, consultant or founder, you may need a Shopify roadmap for a store project rather than for your own learning. The same logic applies: phases, one owner per phase and a milestone anyone can check. Here is a five-phase store project plan you can copy as it is, then add your own dates.
Phase 1: Scope and Audit
Owner: Project lead (ecommerce manager, consultant or founder).
Milestone: A signed-off scope document listing every change, its owner and the approver.
- List the theme changes, apps to add or replace, and integrations such as ERP, stock or email tools.
- Audit installed apps and flag any that still rely on script tags.
- Decide whether headless is truly needed or a Liquid theme covers the brief.
- Agree on who approves each release.
Phase 2: Theme Build on a Preview Copy
Owner: Theme developer.
Milestone: A shareable preview link where the merchant can change texts and images in the theme editor without code.
- Duplicate the live theme or start from a clean theme, never editing the published one.
- Connect the theme to GitHub and work through Shopify CLI.
- Build new content as sections and blocks the merchant can edit.
Phase 3: Apps and Integrations
Owner: App or integration developer.
Milestone: Every app shows up in the theme editor or as a web pixel, and test orders reach every connected system.
- Replace script tag apps with versions that use app embed blocks or web pixels.
- Connect and test each integration on a development store with sample orders.
- Write down which app controls which part of the storefront.
Phase 4: QA and Performance
Owner: QA lead, with the theme developer.
Milestone: A QA checklist with every item marked passed, plus performance results attached to the release ticket.
- Test key journeys on mobile and desktop: search, product page, cart, checkout entry.
- Run Theme Check, Lighthouse and a Core Web Vitals review on the preview theme.
- Fix issues and record before and after results.
Phase 5: Launch and Handover
Owner: Project lead, with the merchant.
Milestone: The new theme is live, the merchant has approved it, and the previous theme is saved as a fallback.
One risk to plan for: Shopify's help center explains, in its guide on updating themes, that code edits are not always carried into a new theme version and may have to be copied over by hand. Keep custom code in Git and in sections, and list every edit so the next update is simple. For more on how this kind of plan differs from a task list, see our guide on roadmap vs project plan.
- Publish the theme at an agreed low-traffic moment, and keep the previous theme unpublished as a fallback.
- Train the merchant team on the theme editor and the new apps.
- Monitor errors and orders during the first days after launch.
Common mistakes to avoid
- Skipping JavaScript to rush into Liquid leaves you unable to build carts or filters, so finish the web foundations phase first.
- Editing the live theme in the admin code editor can break the store and makes theme updates harder, so work on an unpublished copy with Shopify CLI and Git.
- Hardcoding text and images into templates frustrates merchants, so expose them as section and block settings.
- Following old tutorials that inject features with script tags creates rework, so build theme app extensions instead.
- Ignoring speed until the end makes fixes harder, so measure Core Web Vitals in every theme phase.
- Showing only screenshots hides your skill, so share development store links, code and case studies.
Frequently asked questions
What is the roadmap to become a Shopify developer?
Learn HTML, CSS, JavaScript and Git first, then Liquid and Online Store 2.0 themes. After that, choose apps, headless or integrations as your next track. Finish each phase with a project you can show, and end with three case studies.
How long does it take to learn Shopify development?
From zero, plan for about 9 to 12 months part time to reach paid theme work and a basic app. If you already build websites, the theme phases can take a few weeks instead of months. Your pace depends on how many real projects you ship along the way.
Should I learn Liquid or React and Hydrogen first?
Start with Liquid. Most stores run on Liquid themes, and theme work teaches the Shopify data model that Hydrogen also uses. Move to Hydrogen once you are comfortable with React and have a client case that needs a custom frontend.
Do I need a Shopify Partners account to start?
It is the easiest way to begin, because it lets you create development stores to build and test on. Use one store for experiments and another for clean portfolio demos.
Where do I start to build a public Shopify app?
Scaffold an app with Shopify CLI, learn the GraphQL Admin API and authentication, then add a theme app extension for anything shown on the storefront. Test the install flow on a fresh development store before you share it.