/studio/engineering
Application engineering
Ruby on Rails, React and TypeScript. Owns the app core, the embedded Admin surface, and every Admin GraphQL call that touches merchant data.
- Rails
- React
- GraphQL
- Postgres
Shopify development studio · Shopify Partner · Vietnam, working worldwide
We build apps that merchants actually love.
A full product house for Shopify: engineering, storefront extensions, design, QA and merchant support under one roof. We publish our own apps, so we run the same standards we sell.
20+
Services delivered
10K+
Merchants served
6
Disciplines in-house
5.0
App Store rating
24h
Typical response time
Built on, and alongside
theoh.team / work
Featured project
One of our own products, still in daily use on thousands of storefronts.
Shopify app · Live since 2024
Breadcrumbs & Categories
A navigation system for Shopify stores: multi-level collection trees, automatic breadcrumb trails, and real-time sync with the storefront.
installs2K+ active
rating5.0 / 5.0
supportDirect, same team that builds it
"Excellent app with great support. The team is responsive and features work flawlessly."— Verified merchant, Shopify App Store
theoh.team / studio
Inside the studio
Six disciplines, one delivery pipeline. Nothing about your app gets outsourced to a stranger.
/studio/storefront
Storefront & extensions
Theme app extensions, Liquid blocks and checkout UI, tested against the themes merchants actually run rather than a clean demo store.
- Liquid
- Theme extensions
- Checkout UI
- Web Pixels
/studio/platform
Platform & infrastructure
Deploys, background jobs, caching, CDN and the monitoring that pages us before a merchant has a reason to open a ticket.
- Docker
- CI/CD
- Redis
- Monitoring
/studio/design
Product design
Polaris-native admin flows and storefront components built to inherit a merchant's theme instead of fighting it. Accessibility is part of the spec, not a later pass.
- Polaris
- Design systems
- WCAG AA
/studio/qa
QA & release
Every change is read by a second engineer and rehearsed on a staging store. Releases go out staged, with the rollback written down before the deploy.
- Automated tests
- Staging stores
- Staged rollout
/studio/support
Merchant support
Replies written by the people who own the code. No tiered script, no ticket bouncing, no account manager translating between you and an engineer.
- Shared Slack
- Screen-share
Roster
Seats, and what each one owns. We publish roles rather than headshots: cover is guaranteed by the seat, not by an individual who might be on leave the week you need them.
| ID | Role | Owns |
|---|---|---|
| ENG-01 | Lead application engineer | App core, billing, webhook integrity |
| ENG-02 | Senior backend engineer | Admin GraphQL, catalog sync pipeline |
| ENG-03 | Backend engineer | Background jobs, data model, migrations |
| ENG-04 | Frontend engineer | Embedded Admin surface, React and Polaris |
| SFR-01 | Lead storefront engineer | Theme app extensions, Liquid rendering |
| SFR-02 | Storefront engineer | Storefront blocks, theme compatibility matrix |
| PLT-01 | Platform engineer | CI/CD, deploys, caching, monitoring and alerts |
| DSN-01 | Product designer | Admin flows, storefront components, design system |
| QA-01 | QA lead | Release rehearsal, regression suite, sign-off |
| QA-02 | QA engineer | Theme and device matrix, edge-case catalogs |
| SUP-01 | Support lead | Merchant escalations, incident comms, docs |
| SUP-02 | Support engineer | First response, reproduction, bug triage |
Named contacts for your project are listed in the statement of work, along with the backup seat for each one.
Founded
2023 · Vietnam, working worldwide
Core hours
09:00–18:00 GMT+7, Mon–Fri
Overlap
Daily with EU · scheduled with US
Escalation
On-call for production incidents
theoh.team / services
What we do
Four ways to engage the studio, depending on where your app is today. Each one is scoped in writing before anyone writes code.
/dev/custom-apps
Custom app development
Bespoke Shopify applications built around how your business actually operates, not a generic template.
Discuss a build →/dev/extensions
App extensions
Theme blocks, checkout UI extensions, and integrations that plug into the storefronts you already have.
Discuss an extension →/ops/maintenance
Maintenance & support
Ongoing updates, monitoring, and performance work for apps already in production, including ones we didn't build.
Talk about support →/consulting/architecture
Technical consulting
Architecture reviews, technology choices, and a second opinion before you commit engineering time.
Book a consult →theoh.team / process
How work moves
The same pipeline runs for a client build and for our own apps. You can see where your project is at any point.
01
Scope
We turn the conversation into a written spec: what ships, what does not, and what it costs. You push back on the document, not on a half-built feature.
output Signed spec & estimate
02
Build
Work lands in small increments on a staging store you can open yourself. Weekly written progress, no silence between kickoff and delivery.
output Weekly demo build
03
Review
A second engineer reads every change, and QA runs it against real merchant themes and edge-case catalogs before it is called done.
output Review & QA sign-off
04
Release
Staged rollout with the rollback plan written before the deploy, plus handover docs so your own team is never dependent on ours.
output Release notes & handover
05
Watch
Monitoring, error budgets and platform-change tracking. When Shopify deprecates something, the fix is our job to raise, not yours to discover.
output Ongoing maintenance window
theoh.team / standards
What every engagement includes
Not upsells. These apply whether the project is two weeks or two years.
Two-person review. No change reaches a merchant on one person's judgement.
Staged releases. Rolled out in stages, with a documented rollback path.
Uptime & error monitoring. Alerting with on-call escalation for production incidents.
Least-privilege scopes. We request the Shopify access we need, and re-check it each release.
GDPR-aligned data handling. Mandatory Shopify privacy webhooks; merchant data deleted on uninstall.
Your code, your repo. Source handed over on request. No lock-in, no hostage code.
NDA, MSA and SOW. Paperwork available before kickoff, not after a dispute.
Written handover. Architecture notes and runbooks so another team could pick it up.
01 · who answers
The engineers who write the code answer your ticket. Support is a discipline here, not a call-centre layer bolted on top.
02 · how we scope
Every project starts as a written spec you can push back on, priced before a single line of code ships. No open-ended hourly drift.
03 · after launch
Shopify's platform changes constantly. Keeping what we built working is our job to track, and it is in the contract.
theoh.team / contact
Let's work together
Have a project in mind? Tell us about it, we'd love to hear it.
Send us a route.
Every message is read by an engineer, not a sales inbox. You will get a real technical answer, and a written scope if the fit is there.
Location
Vietnam
Response time
Within 24 hours, Mon–Fri
Paperwork
NDA, MSA and SOW available on request