
App choice defines gateway hardware, firmware updates, integration options and platform risk for years; this FAQ answers the questions buyers ask before standardizing a range.
The app is the part of a smart lock customers touch daily, yet brand owners often choose it last. This FAQ covers Tuya versus TTLock versus a proprietary factory app, cloud versus offline unlock logic, which locks need a gateway, Wi-Fi, Bluetooth, Zigbee and Sub-GHz radio trade-offs, how firmware updates reach installed locks, the white-label app process, managing hundreds of doors from one console, API and access-control integration, and what happens if a platform changes terms or sunsets. Features vary by SKU and firmware generation; the supported platform, gateway model, integration scope, update policy and data-handling details are confirmed in writing per RFQ, and current MOQ policy, sample terms and lead time are confirmed per quotation.
Tuya offers a very broad device ecosystem, mature tooling and a white-label app pipeline, which suits brands selling a wider smart-home catalog; costs and certification steps follow its program. TTLock is deeply focused on locks and access management, with strong passcode, eKey and multi-property workflows popular with rental and apartment operators. A proprietary factory app gives more control and differentiation but requires the factory to maintain cloud, servers, security updates and app-store compliance for years. The decision depends on your market, desired integrations and willingness to accept platform dependence. Which platforms each quoted SKU supports, white-label terms and roadmap commitments are confirmed in writing per RFQ.
A cloud lock verifies credentials and executes remote commands through a server: remote unlock anywhere, live audit logs and instant revocation, at the cost of a working internet path and dependence on the platform. An offline lock makes decisions at the door from a credential or a seeded passcode, continuing to work during internet or server outages, with audits retrieved over Bluetooth or cards. Most modern locks blend the two: local authentication always works, while remote features run online and offline temporary codes fill the gaps. For rental and apartment use, offline code generation is often the feature that prevents guest lockouts. The exact offline capability and code-generation logic per SKU are confirmed in writing.
Yes, generally. The phone talks to the lock directly over Bluetooth when nearby, which handles setup, nearby unlock and audit download with low power use. To issue a passcode remotely, unlock the door from another city or receive door-status alerts, a gateway bridges Bluetooth to the home or office Wi-Fi and the cloud; one gateway often covers several nearby locks depending on walls and range. Some models integrate Wi-Fi directly and need no separate hub, at the cost of higher battery drain. Gateway model, number of locks per gateway, pairing mode and coverage guidance for the quoted system are confirmed in writing, and gateway placement should be tested on site before rollout.
Bluetooth gives low power and direct phone control but needs a gateway for remote features; direct Wi-Fi removes the gateway but draws significantly more battery and suits locks with rechargeable packs or hardwire backup; Zigbee integrates with smart-home and alarm ecosystems through its own hub and offers efficient mesh networking; Sub-GHz radios suit long-range, low-data access systems in buildings. Rental and apartment deployments overwhelmingly use Bluetooth plus gateway or Wi-Fi with offline codes; hotels lean on dedicated online or offline architectures. Radio choice should follow the building, battery strategy and integrations, not a spec sheet. Supported radios and modules per SKU, including regional certifications, are confirmed per RFQ.
With a well-designed lock, yes: local credentials — fingerprint, card, keypad passcode or mechanical key — are validated in the lock itself and keep working without any network. Dated and offline passcodes generated from a seed can be issued ahead of a booking and typed at the keypad even if the building has no connectivity at arrival. What stops working offline is real-time remote unlock, instant revocation and live log upload, which resume when the connection returns. A mechanical override or emergency-power contacts remain the final fallback. Confirm the offline credential types, offline-code limits and emergency entry path for the named SKU in writing, and test them during sampling rather than discovering them in an outage.
Platform continuity is a legitimate diligence question. Locks using a major public ecosystem benefit from scale but remain subject to that company's terms, pricing and service changes; a platform winding down typically gives notice and may offer migration tools, but long-term guarantees are rare. Locally authenticated credentials continue to work regardless of cloud status, while remote and app features degrade. Mitigations include choosing a platform with a large active install base, requiring a documented data-export and unlock fallback, keeping offline code and mechanical override paths, and preferring firmware that can be reflashed where contractually offered. Platform-risk terms, continuity commitments and any firmware migration option are confirmed in writing per RFQ rather than assumed.
Yes — at the platform tier designed for it. Consumer apps handle a handful of family locks; operator and multi-property tiers add grouped locations, role-based permissions for staff, timed and recurring passcodes, eKey issuance, audit search, batch provisioning, low-battery alerts and integration with channel or property software. Gateways must be planned per building for coverage. Hotels and enterprises typically use dedicated PMS-linked or access-control platforms rather than rental-style apps. Before standardizing, trial the console with your real workflow: cleaner windows, staff turnover and multi-site reporting. Multi-lock capacity, roles, gateway requirements and integration scope for the quoted platform are confirmed in writing per RFQ.
Depending on the SKU and platform. Tuya-based locks can expose supported devices to Google and Alexa voice assistance and, where certified, Apple Home through the relevant integrations; TTLock's integrations focus on its own ecosystem and selected smart-home and hospitality channels; Matter support is appearing on newer modules and changes by firmware. Voice assistants usually cover lock-status queries and, where security policy permits, locking — unlock by voice is often disabled for safety. Apple Home Key requires specific NFC/UWB hardware and certification and cannot be added by app update alone. Claimed ecosystem support must be verified on the sample with your account region; supported integrations per model are confirmed in writing per RFQ.
Connected locks receive over-the-air (OTA) updates through the app or gateway, usually staged by the manufacturer; Bluetooth-only locks update from an authorized phone nearby. A safe updater verifies the firmware signature, keeps backup power checks and either preserves the existing firmware for rollback or refuses the update under low battery. Updates may add features, patch security issues or fix radio bugs, but a failed update on a deployed lock is a serious event, so mature platforms use staged rollouts and release notes. Ask whether updates are automatic or admin-approved, who develops them for the platform SKU, how long security patches continue, and what bricking recovery exists. Update policy and maintenance window per model are confirmed in writing.
Yes, on both major managed platforms and on some proprietary stacks. White label typically means your logo, app name, color theme and accounts under your developer-account presence; it requires app-store developer membership, privacy-policy and support infrastructure, and on some platforms a certification or fee. Setup takes roughly several weeks of configuration and store review cycles, and app updates then follow the platform's release calendar. A fully bespoke app with custom features is an NRE project with ongoing hosting and maintenance. Brand scope, store ownership, costs, update cadence, region availability and minimum order conditions are confirmed in writing per RFQ; begin app work in parallel with tooling so both finish together.
Data flows between lock, phone, gateway and the platform's cloud, hosted in the provider's server regions; the exact regions, retention and account-deletion process follow the platform's terms and configuration of the white-label tenant. Credential safety depends more on architecture than location: most quality locks store fingerprint templates as mathematical minutiae, not reversible images, inside the lock's secure element, and transmissions use standard encryption in transit. Passcodes and audit logs on servers are the operator's responsibility under the applicable privacy law — GDPR in Europe, UK GDPR and other national regimes. Data regions, template storage, encryption, sub-processor and export terms for your app tenant are confirmed in writing, not inferred from marketing copy.
Yes, on platforms that expose one, but scope varies widely: common endpoints issue and revoke passcodes or eKeys, list locks, fetch battery and lock status, and pull audit events; authentication uses standard tokens or OAuth-style flows, with rate limits and server regions to consider. Hotel integrations commonly run through PMS gateways, while enterprise systems use API or, for wired readers, Wiegand or OSDP links. API access may sit on a paid plan, require server-side integration work, and come with branding or certification rules. Ask for the actual API documentation, the environment for testing, who develops the integration, and uptime commitments before designing your software around it. Available endpoints, SLA and terms for the quoted platform are confirmed in writing.
Usually not seamlessly. The lock firmware is often built around one platform's module and cloud, so moving to another ecosystem can mean replacing radio modules, reflashing firmware where the supplier supports it, or swapping hardware; user accounts, passcodes and audit history belong to the platform's tenant and export options differ. Because of this, choosing a platform is a multi-year architecture decision: evaluate ecosystem size, API access, data-export rights, white-label terms and the factory's history across product generations before standardizing. Multi-protocol hardware and contracts that address end-of-life data export reduce the risk. Migration feasibility, module replacement cost and export rights for the exact SKU are confirmed in writing per RFQ.
The platform operator publishes terms of service and, on commercial tiers, service-level commitments; the factory passes those through rather than underwriting a third-party cloud itself. Practical reliability is generally high for major ecosystems, but outages happen, which is exactly why local credentials and offline passcodes matter. For service-level promises in your own contracts, mirror only what you hold in writing and add fallback language for scheduled maintenance and force majeure. Projects with strict uptime requirements often use offline-capable or locally hosted access-control architectures. The platform terms, any commercial SLA, maintenance windows and the offline fallback for the quoted SKU should be requested as documents per RFQ and confirmed in writing.
A platform app — such as those built on Tuya or TTLock — runs on infrastructure the platform company maintains, with its accounts, servers, feature roadmap and update cadence; the factory's role is producing compatible hardware, and your white-label app is a tenant of that ecosystem. A factory proprietary app runs on the manufacturer's own servers and firmware stack, which can allow custom features and direct API cooperation but concentrates platform, hosting and maintenance risk on that supplier. Both models can be excellent; the diligence differs. Ask to see the app under load, the admin console, release history, privacy documentation and the entity responsible for cloud operation. App ownership, hosting entity and roadmap for each quoted SKU are confirmed in writing.
Online, the phone or gateway delivers the command through the cloud and the lock confirms execution. Offline, two mechanisms dominate: seeded offline passcodes, where lock and app share a secret algorithm so a code generated for a future date works even with no network; and Bluetooth eKeys delivered when a manager's phone comes near the lock, commonly used for staff routes. Some systems also let the lock sync queued commands when any authorized phone reconnects. Each has limits on code count and duration, and audit logs upload on reconnection. Rental operators should verify the guest journey on a basement door with zero signal during sampling. Offline code type, capacity, delivery and sync behavior per SKU are confirmed in writing per RFQ.
Share your market and integration plans. We confirm app platform, gateway model, offline behavior, API scope, white-label process and current MOQ policy, sample terms and lead time in writing per quotation.
Ask Our EngineersRequest a QuoteLast updated: November 1, 2026 · Answers reviewed by the Smart Lock Factory engineering team