Launching a branded smart lock app alongside private-label hardware requires coordinated product, software, testing and market requirements. This guide shows what to prepare and how to structure the project without assuming a fixed launch date.
The 90-Day Timeline
Phase 1: Contract & Requirements
Define hardware SKUs, OEM MOQ 500 units, feature list, integrations, target markets, data-handling requirements and branding assets. Confirm the delivery plan with Trudian before production.
Days 7–14: Brand Asset Collection
You provide: app name, app icon (1024×1024 px), splash screen, primary/secondary brand colours (hex codes), screenshots for App Store listing (6.5" iPhone, 12.9" iPad, and Pixel 6 sizes), App Store description text, privacy policy URL, and support contact details.
Days 14–28: App Configuration & Testing
Trudian configures the Tuya OEM app SDK with your brand assets, selects your feature set (BLE unlock, PIN code management, e-key sharing, access log, OTA, multi-device support), sets up your Tuya IoT project (data residency region, cloud region: EU/US/India/CN), and conducts internal QA testing across iOS 17+ and Android 13+ devices.
Phase 3: Store Submission
You create or provide access to your Apple Developer and Google Play accounts. Trudian prepares the build files and submission materials; review time depends on the store, account status and submitted scope.
Parallel: Hardware Production
Hardware production runs alongside app work after approval of the model, order quantity and artwork. Trudian confirms lead time, QC and shipping milestones for the selected order.
Days 42–90: Launch Preparation & Go-Live
App approved and live in stores. Hardware arrives at your warehouse. Pair test: scan lock QR code in app, confirm BLE pairing, confirm cloud registration. Prepare user manual with your brand (Trudian provides editable InDesign template). Launch marketing materials. Go-live.
What You Own vs What Tuya Owns
| Asset | You Own | Tuya Owns |
|---|---|---|
| App name & icon | ✓ | |
| App Store developer accounts | ✓ | |
| Customer data (with GDPR compliance setup) | ✓ | |
| Tuya SDK & app source code | ✓ | |
| Cloud infrastructure | ✓ | |
| Device firmware | ✓ (OTA updates managed by Tuya) |
Feature Checklist for Your App Configuration
- BLE unlock — direct Bluetooth unlock when phone is in range, no internet required
- Remote unlock — cloud-based unlock via internet (requires Wi-Fi or 4G at the lock)
- PIN code management — add/delete/schedule PIN codes remotely
- E-key sharing — share temporary or permanent digital keys via app invite
- Access log — timestamped entry history with user ID
- OTA firmware update — push firmware updates to all paired devices from the cloud
- Multi-device support — one account manages multiple locks across properties
- Auto-lock timer — configurable auto-relock after X seconds
- DND mode — silence door alerts during specific hours
- Voice assistant integration — Alexa/Google Home skill linkage via Tuya skill
Frequently Asked Questions: Private Label Smart Lock App
For private-label OEM planning, Trudian uses MOQ 500 units. Standard supply is MOQ 200 units and ODM is MOQ 1,000 units. Final quantities depend on the selected model, app scope, testing and target market.
Yes. To publish an app under your brand name in the App Store and Google Play, you must have your own developer accounts: Apple Developer Program ($99/year, requires Apple ID and business entity verification) and Google Play Developer ($25 one-time registration fee). The app is submitted under your accounts so it appears as your company's app in store listings, not the factory's. Allow 1–2 weeks for Apple account verification if you are registering for the first time. Trudian provides the compiled app builds (IPA for iOS, AAB for Android) for you to submit, or can submit on your behalf if you grant access.
Yes. Tuya IoT platform offers data residency region selection: EU (Frankfurt), US (Oregon), India, and China. For European deployments requiring GDPR compliance, specify EU region during the Tuya IoT project setup in Days 14–28 of the launch timeline. EU region ensures user data — device registration, access logs, account information — is stored on Tuya's AWS Frankfurt infrastructure within the EEA. This is a configuration choice made at project setup; changing data residency region after launch requires migrating all user accounts, which is operationally complex. Confirm your target region before signing the OEM agreement.
The Tuya OEM SDK allows configuration of: BLE unlock (tap-to-unlock via Bluetooth), PIN code management (add, delete, set time-limited PINs), e-key sharing (send temporary access to guests via app), access log (view door open/close history), OTA firmware updates (push firmware updates to locks), multi-device support (manage multiple locks from one account), and voice assistant integration (Alexa, Google Assistant). Features can be enabled or disabled per app configuration. Features not available for customization include the core BLE pairing protocol and Tuya cloud communication stack, which are fixed at the SDK level.
Required assets: app name (check availability in App Store and Google Play before finalizing), app icon at 1024×1024 px (PNG, no transparency for iOS), splash screen at multiple resolutions, primary and secondary brand colors in hex codes, App Store screenshots (6.5-inch iPhone, 12.9-inch iPad, and Pixel 6 sizes — minimum 3 per device type), App Store short description (80 characters) and full description (4,000 characters), privacy policy URL (mandatory for both stores — must be publicly accessible), and support contact email or URL. Prepare all assets before Day 7 to avoid delaying the 90-day timeline.
Custom integrations beyond a standard SDK — such as managed-property software webhooks or access-control panel connectivity — require separate technical scoping. Confirm supported interfaces, data handling, testing and delivery dependencies for the selected project.
Tuya SDK updates are mandatory for continued App Store compliance — Apple and Google require apps to update to current SDK versions within defined timelines (typically 12 months after a new iOS or Android release). Tuya manages backward compatibility for OEM apps, but major SDK version upgrades require resubmission to both app stores. Your OEM agreement should specify Tuya's SDK update support obligations and the process for resubmission. To reduce platform dependency risk: ensure your locks support offline credential methods (PIN, RFID) that function without the Tuya cloud, and maintain a backup access method that does not depend on the app.
Launch Your Private Label Smart Lock App
Trudian provides OEM hardware and white-label iOS/Android app planning for B2B projects. MOQ planning: Standard 200, OEM 500, ODM 1,000. Model-specific compliance and software deployment details are confirmed through WhatsApp or email.