01
Customer app layer
Use Tuya App SDK when onboarding, device control, accounts, and daily use need to match the product.
Explore App SDK Tuya-first product development
Tuya app development shaped around the whole product.
Plan and build the customer app, Cloud API backend, and integrations around what the smart home product actually needs.
Product layers
Start with the layer the product actually needs.
02
Business backend layer
Use Tuya Cloud API when operations, automations, dashboards, or business systems need device data outside the app.
Explore Cloud API03
Architecture path
Assess AWS IoT, Matter, or a custom cloud only when ownership or interoperability requires a different layer.
Review the architecture OEM vs SDK
Control is the reason to move.
OEM is a strong launch shortcut. App SDK becomes the next step when the customer experience needs more control; backend and device-cloud decisions stay separate.
Brand & visual identity
OEM
Template only SDK
Fully custom App store presence
OEM
Shared listing SDK
Your own listing UX & navigation control
OEM
Fixed structure SDK
Fully flexible Device flow customization
OEM
Limited SDK
Full control Time to first release
OEM
Fast SDK
Phased Long-term scalability
OEM
Limited SDK
Built to grow Integration flexibility
OEM
Tuya ecosystem only SDK
App + API dependent | Feature | Tuya OEM App | Tuya SDK App |
|---|---|---|
| Brand & visual identity | Template only | Fully custom |
| App store presence | Shared listing | Your own listing |
| UX & navigation control | Fixed structure | Fully flexible |
| Device flow customization | Limited | Full control |
| Time to first release | Fast | Phased |
| Long-term scalability | Limited | Built to grow |
| Integration flexibility | Tuya ecosystem only | App + API dependent |
When the scope changes
Signals the current setup needs another layer.
The next step may be App SDK, Cloud API plus a backend, or an architecture review — not always a rebuild.
Plan your Tuya app The OEM app no longer fits the product experience
Support needs device visibility across users or sites
Device data must reach CRM, warranty, or operations
The team is unsure which layer should change first
Delivery model
A phased approach, not an all-at-once rebuild.
Phase 01
Map the current product
Audit the app, devices, Tuya setup, business systems, and ownership constraints.
App Devices Cloud
Phase 02
Choose the next layer
Decide whether the first release needs app changes, backend workflows, or both.
Scope Architecture Roadmap
Phase 03
Build the scoped release
Implement the required app flows, Cloud API services, and integrations without expanding the infrastructure unnecessarily.
App Backend Integrations
Phase 04
Expand with evidence
Add automation, analytics, AWS IoT, or Matter only when the product data and roadmap justify them.
Automation AWS IoT Matter
Service paths
Build the next layer without rebuilding everything.
Start with the customer app. Add Cloud API and a business backend when data or workflows must leave the app. Assess AWS IoT or Matter only when the device architecture requires it. Building an access product? See our smart lock app solution.
Customer app Layer 01
Cloud API Layer 02
Business backend Layer 03
AWS IoT / Matter As needed
Related thinking
Useful reads for teams comparing paths.
1–4 of 7
01
Tuya OEM app or Tuya App SDK?
How to choose when OEM starts to feel too limiting.
Read article
02
What shapes pricing, cost, and scope?
A practical look at what usually drives effort in OEM-to-SDK app work.
Read article
03
When does a Tuya app upgrade make sense?
What usually changes when the app needs to support the product more seriously.
Read article
04
What should a custom Tuya app define first?
A practical requirements checklist before SDK, Cloud API, or product-specific flows.
Read article
05
What actually carries over from OEM to SDK?
A continuity-first guide to accounts, devices, store identity, and the app experience that must be rebuilt.
Read article
06
What does a production Tuya Cloud API setup require?
Pricing, account configuration, real-time events, and the backend decisions beyond a test API call.
Read article
07
When does a Tuya app need a business backend?
How support dashboards, device alerts, and after-sales workflows change the Cloud API decision.
Read article Start with the product
Not sure which layer should change first?
Show us the current app, devices, Tuya setup, and business workflows. We will separate the first release from later architecture decisions.