Smart Lock APP Development Cost
Direct answer.Smart lock APP development cost is the documented per-scenario cost envelope the buyer's steering committee writes against — one of four scenarios scored head-to-head here: pre-built consumer-app binding on TTLock / Tuya / Doodle, white-label / re-skinned binding, semi-custom binding with bolt-on features, and fully custom bespoke APP — where every cost cell carries a named factor (binding choice, feature list length, number of languages, store-side publishing tier, cloud-hosting tier, re-branding depth, integration scope, release cadence, exit / switch-out envelope) and the exact figure for every cell routes to Request a quote against a dated per-SKU and per-batch quotation. The four scenarios are not interchangeable: a buyer who picks the wrong scenario does not pay more, the buyer pays for the wrong work — a fully-custom APP where a re-skin would have shipped in a fraction of the elapsed time, or a re-skin where the buyer's brand can never be made distinctive enough to compete on the shelf. The catalog binds consumer-app-connected locks to TTLock, Tuya, or Doodle, and the hotel line is managed through dedicated hotel PC software for card encoding and room assignment — those are the sanctioned APP-side anchors the four scenarios inherit. Cost is not a number; cost is a scenario × factor matrix with every per-model cell recorded in the model specification of the shortlist SKU before steering-committee sign-off.
This article sits inside the C16 cost / ROI / business cluster beside the OEM cost breakdown, the ODM cost breakdown, the product development cost, the software cost, the certification cost, and the testing cost. It is the APP-specific lane of that cost envelope, and it answers to the OEM APP requirements document — the requirements document owns the what the APP must do, this article owns the what each scenario costs to build. The APP scenario decision is also constrained by the OEM project cost structure, which is the per-category stack the four scenarios are slices of.
The Scoring Protocol: 0–5 per Round, No Ties in Writing
Every round below uses the same 0–5 protocol so a buyer can read a single scenario's row and know the score does not depend on who is sitting in the steering committee. The protocol is intentionally strict:
| Score | Meaning |
|---|---|
| 0 | Scenario cannot serve this round — the requirement is structurally outside the scenario's design envelope. |
| 1 | Scenario can serve the round but with a manual workaround the buyer's operations team owns after go-live. |
| 2 | Scenario can serve the round with a configuration the supplier owns but does not guarantee in writing. |
| 3 | Scenario can serve the round inside the standard published envelope of the binding. |
| 4 | Scenario can serve the round with a documented customization the supplier quotes against a worksheet. |
| 5 | Scenario can serve the round as a first-class feature of the binding's own published roadmap. |
Three protocol rules inherit from the table:
- No ties are reported as ties. A 3–3 across scenarios reads "all three can do this, the round does not separate them"; a 5–1 reads "one scenario owns this round decisively."
- The running scoreboard is the buyer's reading, not the supplier's. The score reflects what the buyer's operations team will face after the project ships, not what the supplier's sales engineer will promise in the demo.
- A scenario that scores 0 in a round is a structural no-go for that buyer profile, not a "we'll figure it out later" lane. A buyer profile that needs round-R and the chosen scenario scores 0 in round-R has picked the wrong recipe before signing the steering-committee minutes.
The four scenarios in the ring are the same four recipes a buyer's APP steering committee picks among when the OEM APP requirements document (sibling 746) has been written but the cost envelope has not. They are not a marketing menu — they are an exhaustive set of the options the catalog's APP platforms can be delivered as.
The Four APP Scenarios in the Ring
The four scenarios are mutually exclusive at the steering-committee level: a buyer picks one, signs the per-scenario factor sheet against the dated product page, and the project plan hangs the APP milestone off the chosen scenario. They are not gradients on a single dial — picking between them is a structural choice the buyer's brand strategy owns, not a cost-only choice.
| # | Scenario | What it is | Where the binding lives |
|---|---|---|---|
| A | Pre-built consumer-app binding | The lock binds to the published TTLock, Tuya, or Doodle consumer APP with no brand re-skin, no custom feature scope, no custom store publishing, and no custom cloud. The buyer lists the lock on a published app store under a third-party APP publisher account. | Off-the-shelf platform APP, third-party store listing. |
| B | White-label / re-skin binding | The lock binds to a partner's APP shell that accepts a brand re-skin (logo, splash, palette, brand voice strings, app-store metadata). Feature scope stays inside the partner's published envelope. Store publishing may move to a buyer-owned or co-managed publisher account. | Re-skinned platform APP, buyer-controlled metadata. |
| C | Semi-custom with bolt-on features | The lock binds to a platform APP (TTLock / Tuya / Doodle / a partner shell) plus a project-specific extension — a custom feature module, an integration hook, a brand-locked UI surface, or a regional add-on — implemented as a configurable layer on top of the binding. | Platform APP with a documented extension layer. |
| D | Fully custom bespoke APP | A native or cross-platform APP built from the buyer's brand book, with the lock firmware, cloud, and APP contract designed in concert. The APP is not on a published platform binding; the lock-to-APP protocol is owned by the buyer's program. | Bespoke APP, bespoke lock-APP contract. |
Two protocol-level notes that shape every round below:
- Scenario A cannot escape the published platform's roadmap. If TTLock / Tuya / Doodle updates its published envelope, Scenario A updates. The buyer has roadmap influence only inside what the platform publishes.
- Scenario D is the only scenario where the buyer owns the lock-APP protocol. In scenarios A, B, and C the protocol is whatever the platform binding publishes; in scenario D the protocol is whatever the buyer's firmware team and the OEM's lock firmware team write into the OEM firmware requirements document.
The hotel-class line lives in a parallel lane the four scenarios do not displace: hotel-class locks are managed through dedicated hotel PC software for card encoding and room assignment, not through a consumer APP. A buyer whose roadmap is hotel-only should be reading the hotel lock category page and the hotel-software articles rather than this arena. The arena covers the consumer-residential, residential / multi-family, commercial-building, and short-term-rental lanes where a TTLock / Tuya / Doodle consumer APP is the day-to-day user surface.
Round 1 — Time-to-Market from Sign-Off to First Published Build
The first round the buyer's project manager cares about is the elapsed time between the steering-committee minutes and the first published build a guest or resident can download. The four scenarios are not equally fast.
| Scenario | Time-to-first-published-build (factor) | Score | Why |
|---|---|---|---|
| A — Pre-built binding | Lock-side configuration + brand-listed metadata only; the APP build already exists on the platform publisher's account. | 5 | The buyer is configuring, not building. |
| B — White-label / re-skin | Re-skin cycle on the partner shell + store-side metadata transfer; feature scope stays inside the partner's published envelope. | 4 | The buyer owns a re-skin cycle, not a build. |
| C — Semi-custom with bolt-on | Extension module design + brand re-skin + extension QA + store-side metadata cycle. | 3 | The bolt-on is a build the buyer must fund and validate. |
| D — Fully custom bespoke | Native iOS, native Android (or one cross-platform stack), cloud, lock-firmware contract, store publishing, end-to-end QA. | 0–1 | A custom APP at quality is a long production timeline even on a clean runway. |
Score reading: 5–4–3–0 across the four scenarios is the structural shape of this round. Scenario A wins; scenario D loses; scenarios B and C sit between them as a function of how much of the buyer roadmap lives inside vs outside the platform envelope. A buyer profile that needs round 1 as a 5 has constrained the brand roadmap to the platform envelope. A buyer profile that needs round 1 as a 3 has accepted a bolt-on scope and is treating the timeline as a build, not a configuration.
Running scoreboard after Round 1: A 5 · B 4 · C 3 · D 0–1.
Round 2 — Brand and Store-Side Control
The second round is brand control — what the buyer can put on the splash, the app-store screenshot, the in-app settings panel, and the support link without violating the platform binding's terms. The four scenarios differ sharply here.
| Scenario | Brand surface (factor) | Store-side control (factor) | Score | Why |
|---|---|---|---|---|
| A — Pre-built binding | Platform publisher's brand-mark dominates; buyer brand appears as a configured accessory. | Third-party publisher account owns store metadata. | 1 | The brand surface is structurally capped by the platform. |
| B — White-label / re-skin | Buyer brand-mark on splash, palette, settings, support link; partner's footprint may remain in places the re-skin envelope cannot reach. | Buyer-controlled metadata on a buyer or co-managed publisher account. | 4 | The re-skin envelope is the binding's whole purpose. |
| C — Semi-custom with bolt-on | Buyer brand plus a project-specific UI surface in the bolt-on module. | Buyer-controlled metadata plus a documented extension listing. | 4 | The bolt-on extends brand reach without breaking the envelope. |
| D — Fully custom bespoke | Full buyer brand book, full app-store screenshot, full in-app settings ownership. | Buyer-controlled store publishing on a buyer-owned account. | 5 | The brand is the binding. |
Score reading: A 1 · B 4 · C 4 · D 5. Scenario A's score is the structural cap a buyer profile that wants brand-distinctive shelf presence cannot tolerate; scenario D's score is the structural freedom that costs the buyer round 1. Scenarios B and C tie at 4 because the re-skin envelope and the bolt-on envelope both place the brand at the level the platform supports, and the deciding factor between B and C in this round is whether the buyer's brand-distinctive scope is a visible surface (B suffices) or a visible surface plus a feature (C is required).
Running scoreboard after Round 2: A 6 · B 8 · C 7 · D 5–6.
Round 3 — Per-Feature Acceptance Flexibility
The third round is per-feature flexibility — the buyer can ask the APP to behave a particular way on a specific SKU and have that behavior be the binding's contract. The four scenarios differ in whether the per-feature acceptance test (sibling 746's column structure) can be signed against the shipped build.
| Scenario | Per-feature test surface (factor) | Score | Why |
|---|---|---|---|
| A — Pre-built binding | Feature scope is whatever the platform binding publishes; per-feature acceptance is against the platform's published envelope. | 2 | The buyer can test only what the platform has published. |
| B — White-label / re-skin | Feature scope is the partner's published envelope; per-feature test reads the partner's acceptance matrix. | 2 | Re-skin is metadata, not feature scope. |
| C — Semi-custom with bolt-on | Feature scope is the partner's envelope plus the bolt-on module's acceptance matrix; per-feature test can be split across published-vs-custom rows. | 4 | The bolt-on is a documented acceptance surface. |
| D — Fully custom bespoke | Feature scope is whatever the buyer's APP requirements document names, against the buyer's own acceptance tester. | 5 | Every feature row is a contract. |
Score reading: A 2 · B 2 · C 4 · D 5. The A / B tie at 2 is the structural reason a buyer profile that needs per-feature acceptance flexibility should not pick A or B as the scenario — the acceptance test will be against the platform's published envelope, not the buyer's per-feature worksheet. A buyer profile that needs per-feature acceptance to follow the OEM APP requirements worksheet row-by-row will score 0 in this round if it picks A or B, because the worksheet rows that fall outside the platform envelope have no contract surface.
Running scoreboard after Round 3: A 8 · B 10 · C 11 · D 10–11.
Round 4 — Multi-Language and Multi-Region Rollout
The fourth round is localization and multi-region rollout — the buyer has to ship the APP in N languages across M regions, with regional payment rails, regional privacy postures, and regional store-side metadata. The four scenarios scale differently with N and M.
| Scenario | Localization posture (factor) | Score | Why |
|---|---|---|---|
| A — Pre-built binding | Languages supported by the platform binding; regional metadata is a configuration cycle. | 4 | The platform envelope covers common languages. |
| B — White-label / re-skin | Re-skin envelope covers brand strings; feature strings follow the partner's published language coverage. | 3 | Re-skin strings move; feature strings do not. |
| C — Semi-custom with bolt-on | Bolt-on strings are buyer-owned; platform strings follow the partner's published coverage. | 3 | The bolt-on is buyer-controlled; the platform strings are not. |
| D — Fully custom bespoke | All strings buyer-owned; languages and regional metadata are project deliverables. | 5 | Localization is the buyer's build. |
Score reading: A 4 · B 3 · C 3 · D 5. A buyer profile that has a 12-language rollout across three regions and is willing to live inside the platform's published language envelope will score 0 if it picks scenario D, because scenario D's localization cost dominates the project envelope when the platform already supports the languages. A buyer profile that needs a language the platform does not publish (RTL script variants, minority languages, regional SMS-only builds) scores 0 if it picks A, B, or C, because the platform envelope does not extend to that language without a custom build.
Running scoreboard after Round 4: A 12 · B 13 · C 14 · D 15–16.
Round 5 — Cloud-Hosting and Data-Residency Posture
The fifth round is cloud and data residency — where the lock-APP events live, who owns the data export, and what regional hosting tier the binding supports. This is the round that bites a buyer the moment a regional privacy regulator asks where the event log is stored.
| Scenario | Cloud / residency posture (factor) | Score | Why |
|---|---|---|---|
| A — Pre-built binding | Platform cloud, platform residency tier; the buyer does not select a region. | 1 | The buyer takes what the platform publishes. |
| B — White-label / re-skin | Platform cloud with the partner's region options; buyer-side configuration limited to published tier list. | 2 | The partner's region list is the menu. |
| C — Semi-custom with bolt-on | Platform cloud with a project-specific extension that can hold a regional adapter; buyer controls the extension's residency. | 3 | The extension is buyer-owned; the platform is not. |
| D — Fully custom bespoke | Buyer-selected cloud region and buyer-owned data-export contract; the buyer designs the residency posture. | 5 | Residency is a project deliverable. |
Score reading: A 1 · B 2 · C 3 · D 5. The A score of 1 is the structural reason a buyer profile with a strict regional data-residency posture cannot pick scenario A — the platform's region tier may not include the buyer's required jurisdiction, and there is no project-side knob to add one. Scenario C's score of 3 reflects that the bolt-on can host regional data but the platform-side events (unlock-logs, device-binding logs) remain on the platform's tier.
Running scoreboard after Round 5: A 13 · B 15 · C 17 · D 20–21.
Round 6 — Audit / Event-Log Depth and Lock-Cloud Integration
The sixth round is the depth of the audit and event log the APP can pull from the lock, and the depth of the lock-cloud integration the APP can drive (remote unlock, eKey issuance, temporary PIN generation, audit pull cadence, multi-door grouping). This round is where the OEM APP requirements per-feature worksheet meets the lock firmware.
| Scenario | Audit / integration depth (factor) | Score | Why |
|---|---|---|---|
| A — Pre-built binding | Whatever the platform publishes for the SKU; per-model specifics (record count, retrieval cadence, multi-door grouping) — check the model’s published specification. | 3 | The published envelope covers common APP-side operations. |
| B — White-label / re-skin | The partner's published envelope; per-model specifics — check the model’s published specification. | 3 | Re-skin is metadata, not integration depth. |
| C — Semi-custom with bolt-on | Platform envelope plus a project-specific audit-export extension; bolt-on can extend per-feature acceptance. | 4 | The extension can carry integration the envelope cannot. |
| D — Fully custom bespoke | Buyer-owned integration; APP-side behavior matches the OEM firmware contract. | 5 | Integration is a contract. |
The only first-party spec number cited anywhere in this arena is the product-page-documented SLK-9936S hotel lock anchor: door thickness 36–100 mm · RFID Mifare 1 @ 13.56 MHz · read distance 0–5 cm · read time <0.25 s · 4 × AA battery · battery operating cycles >15,000 · audit/event records up to 1,000 · 5-pin cylinder · 3-point latch · stainless steel + alloy body · multiple finish options · mechanical emergency access · multilingual management software · standalone or centralized database modes · positioned for 1–5 star hotels. The "audit/event records up to 1,000" line is invoked once as the documentation-granularity yardstick for what an APP-side audit-acceptance test must read against in writing, and it is scoped strictly to the SLK-9936S SKU — the per-feature depth on every other catalog SKU is a check the model’s published specification blank, not a carried figure.
Score reading: A 3 · B 3 · C 4 · D 5. The A / B tie at 3 reflects that re-skin does not change integration depth — only the brand surface changes. A buyer profile that needs an audit-pull cadence the platform binding does not publish will score 0 if it picks A or B; scenario C with a bolt-on export extension is the smallest scenario that can carry that contract; scenario D carries it natively.
Running scoreboard after Round 6: A 16 · B 18 · C 21 · D 25–26.
Round 7 — Ongoing Maintenance, Release Cadence, and Per-Year Operating Cost
The seventh round is what the APP costs to keep alive after go-live — the release cadence the binding supports, the per-year operating envelope (cloud spend, store-side fee, support hours, language drift, OS-version refresh). This is the round that determines whether the steering committee's signed year-one number is also the year-three number.
| Scenario | Ongoing maintenance posture (factor) | Score | Why |
|---|---|---|---|
| A — Pre-built binding | Platform-owned cadence; the buyer is on the platform's release train. | 4 | The platform carries the maintenance. |
| B — White-label / re-skin | Partner's cadence plus re-skin refresh cycles on brand drift, app-store screenshots, OS-version screenshots. | 3 | The re-skin envelope must be re-applied each release. |
| C — Semi-custom with bolt-on | Partner's cadence plus extension QA on every platform release; bolt-on is a recurring test surface. | 2 | The bolt-on is a per-release QA cost. |
| D — Fully custom bespoke | Buyer-owned cadence, buyer-owned QA, buyer-owned OS-version refresh, buyer-owned security patching. | 2 | The buyer carries the maintenance. |
Score reading: A 4 · B 3 · C 2 · D 2. The C / D tie at 2 is the structural reason a buyer profile that has a thin in-house QA team should not pick C or D — the per-release QA cost is a recurring line that the buyer's CFO will see every quarter. A buyer profile that needs round 7 as a 4 has accepted the platform's release cadence as the binding's release cadence; a buyer profile that needs round 7 as a 2 has accepted a recurring QA budget.
Running scoreboard after Round 7: A 20 · B 21 · C 23 · D 27–28.
Round 8 — Exit, Switch-Out, and Lock-In Risk
The eighth round is the friction to switch APP scenario after go-live — what it costs to leave scenario A for B, B for C, C for D, or any of them for a different supplier's binding. This is the round the buyer's general counsel cares about because it determines whether the OEM contract has an exit clause.
| Scenario | Exit / switch-out friction (factor) | Score | Why |
|---|---|---|---|
| A — Pre-built binding | Switching APP means re-binding every shipped lock to a different platform; lock-side firmware supports the published bindings, the buyer selects one. | 3 | The lock supports re-binding; the APP-stack does not migrate. |
| B — White-label / re-skin | Re-skin envelope and store-side metadata can move; the partner's lock-cloud contract does not migrate. | 3 | Brand moves; cloud contract stays. |
| C — Semi-custom with bolt-on | The bolt-on module must be re-built against the new platform's envelope; platform events re-migrate, extension events re-export. | 2 | The bolt-on is a per-platform asset. |
| D — Fully custom bespoke | The bespoke APP, cloud, and lock-firmware triad is buyer-owned; the buyer can move to a new OEM with the contract, but the lock-APP protocol must be re-validated on each new OEM. | 4 | The buyer owns the lock-in. |
Score reading: A 3 · B 3 · C 2 · D 4. The A / B tie at 3 reflects that exiting a platform binding is structurally bounded by the lock-side firmware's binding list — the buyer can re-bind a SKU that supports multiple bindings, but the historical event log does not migrate. Scenario D's score of 4 reflects that the buyer owns the lock-APP protocol and can move it to a new OEM, but each new OEM's lock firmware must re-validate the protocol under the OEM firmware requirements document.
Running scoreboard after Round 8: A 23 · B 24 · C 25 · D 31–32.
Cumulative Scoreboard
The cumulative scoreboard reads the eight rounds as a single decision stack. The shape of the scoreboard — not the exact totals — is the buyer's reading: scenarios A and B are clustered at the bottom of the scoreboard across the eight rounds, scenarios C and D are clustered at the top, and the spread between them is the structural cost of brand-and-integration freedom the buyer is paying for.
| Scenario | R1 | R2 | R3 | R4 | R5 | R6 | R7 | R8 | Total (out of 40) | Reading |
|---|---|---|---|---|---|---|---|---|---|---|
| A — Pre-built binding | 5 | 1 | 2 | 4 | 1 | 3 | 4 | 3 | 23 | Lowest envelope; lowest freedom. |
| B — White-label / re-skin | 4 | 4 | 2 | 3 | 2 | 3 | 3 | 3 | 24 | Brand-distinctive within the partner envelope. |
| C — Semi-custom with bolt-on | 3 | 4 | 4 | 3 | 3 | 4 | 2 | 2 | 25 | Bolt-on scope as the deciding factor. |
| D — Fully custom bespoke | 0–1 | 5 | 5 | 5 | 5 | 5 | 2 | 4 | 31–32 | Highest envelope; highest freedom. |
The scoreboard shape — a 23 / 24 / 25 / 31–32 spread — is the structural reason a buyer profile that is genuinely undecided between scenarios A, B, and C is choosing on round 6 (per-feature acceptance) and round 8 (exit), not on rounds 1, 2, or 4. The deciding rounds are the ones where the buyer profile has a non-negotiable, not the rounds where all three scenarios cluster.
A buyer profile that scores scenario D at 0–1 in round 1 is a profile that has accepted a long production timeline as the price of brand-and-integration freedom; a buyer profile that scores scenario A at 1 in round 2 is a profile that has accepted the platform's brand-mark dominance as the price of fast time-to-market. The scoreboard is a price-of-freedom table, not a quality table.
Verdict by Buyer Profile
The four scenarios are not a single-answer menu. A buyer profile picks the scenario that wins the rounds the buyer cannot compromise on, and accepts the rounds where the chosen scenario loses. The five buyer profiles below are the canonical lanes a steering committee fits itself within, and each carries a non-obvious note that buyers routing decisions into this arena will recognize.
| Buyer profile | Recommended scenario | Deciding round | What the profile is giving up | Link to adjacent arena |
|---|---|---|---|---|
| Private-label brand owner launching a residential lock line | B — White-label / re-skin | R2 (brand), R3 (per-feature on published envelope) | R1 (timeline is slightly longer than A), R7 (re-skin refresh cycles). | Private-label product selection. |
| Hotel chain with multi-property roll-out | A or hotel-PC lane | R1 (timeline), R8 (exit friction) | R2 (brand), R5 (residency) — unless the chain takes the hotel-PC parallel path. | Hotel PMS integration. |
| Distributor / wholesaler with a multi-country house brand | C — Semi-custom with bolt-on | R3 (per-feature worksheet), R5 (regional bolt-on residency) | R7 (bolt-on QA per release), R1 (longer than A / B). | Distributor product portfolio. |
| System integrator with a property-management platform to bind into | D — Fully custom bespoke | R3 (per-feature contract), R5 (residency), R6 (audit depth) | R1 (long timeline), R7 (recurring QA budget). | System-integrator procurement guide. |
| Importer / first-time brand with thin in-house QA | A — Pre-built binding | R1 (timeline), R7 (no per-release QA burden) | R2 (brand surface), R3 (per-feature acceptance surface), R5 (residency). | Smart lock importer guide. |
The verdict table is not a recommendation list. It is a price-of-freedom table — each profile's recommended scenario is the scenario that wins the rounds the profile will not compromise on, with the rounds it concedes listed in the "what the profile is giving up" column. A buyer profile that finds the "giving up" column unacceptable has picked the wrong recipe, not the wrong verdict.
The APP Cost-Category Stack Inside Each Scenario
The scoreboard above reads what each scenario costs the buyer in score shape — fast / slow, free / locked, surface / depth. The cost-category stack below reads what each scenario costs the buyer in factor shape — the named categories that move each cell of the scoreboard. Every cell is a factor; every exact figure routes to Request a quote against a dated quotation.
| Cost category | What it covers | Scenario A factor | Scenario B factor | Scenario C factor | Scenario D factor |
|---|---|---|---|---|---|
| Binding license / platform access | Per-device or per-year fee for the platform binding (TTLock / Tuya / Doodle / partner shell). | Published platform fee. | Partner envelope fee. | Partner envelope fee + bolt-on license. | Bespoke build, no platform fee. |
| Re-skinning / brand-mark artwork | Splash, palette, settings panel, brand voice strings, store screenshots. | Not applicable (third-party publisher). | Re-skin cycle per release. | Re-skin cycle per release + extension brand surface. | Buyer-owned brand book. |
| Per-feature acceptance surface | Per-row worksheet against sibling 746's column structure. | Published platform envelope only. | Partner envelope only. | Platform envelope + bolt-on acceptance matrix. | Buyer-owned APP requirements, per-row contract. |
| Store-side publishing tier | App-store publisher account, store metadata cycle, OS-version screenshots. | Third-party publisher owns. | Buyer or co-managed publisher owns. | Buyer-owned publisher + extension listing. | Buyer-owned publisher. |
| Cloud hosting / data-residency tier | Server spend, region tier, event-log retention, data-export contract. | Platform cloud, platform region tier. | Partner cloud, partner region tier. | Platform cloud + extension regional adapter. | Buyer-selected cloud, buyer-owned residency contract. |
| Multi-language localization | String count, regional screenshots, regional metadata. | Platform-published language coverage. | Partner-published language coverage + re-skin strings. | Partner coverage + extension strings (buyer-owned). | Buyer-owned language build. |
| Integration scope (PMS / channel manager / CRM / ERP) | API contract, integration testing, per-integration acceptance. | Platform-published integrations. | Partner-published integrations. | Platform + extension integration surface. | Buyer-owned integration contract. |
| Release cadence / per-year maintenance | Per-release QA, OS-version refresh, security patching, language drift. | Platform cadence, buyer is on the train. | Partner cadence + re-skin refresh. | Partner cadence + extension QA per release. | Buyer-owned cadence and QA budget. |
| Exit / switch-out envelope | Lock-in friction, lock-rebind cost, event-log migration. | Lock-side rebind cost, no event migration. | Partner exit terms, no event migration. | Extension re-build cost, extension events re-export. | Buyer-owned protocol, OEM-by-OEM re-validation. |
| Acceptance testing / QA labor | Per-build QA, per-region QA, per-language QA. | Minimal — platform's published envelope. | Light — re-skin strings. | Moderate — extension QA each release. | Heavy — buyer-owned QA budget. |
The category stack is not a quotation. It is the factor map the buyer's steering committee uses to read a per-scenario quotation when one arrives — every cell of the received quotation should fall into one of the ten categories, and any cell that does not is either a hidden category the supplier has bundled or an undocumented line the steering committee must ask the supplier to expand before signing.
The APP Cost-Category Worksheet: Fill From Your Own Quotation Packet
The factor map above is what a buyer reads against. The worksheet below is what a buyer fills from the per-scenario quotation packet the supplier delivers. Every row is a category; every column is a scenario; every cell is a blank the buyer fills against the dated quotation. The EXAMPLE row is a worked example a steering committee can use as a sanity check — not a figure to copy.
| Cost category | Scenario A (fill) | Scenario B (fill) | Scenario C (fill) | Scenario D (fill) | Notes |
|---|---|---|---|---|---|
| Binding license / platform access | ___ (EXAMPLE: per-device annual) | ___ (EXAMPLE: partner envelope tier) | ___ (EXAMPLE: partner + bolt-on license) | ___ (EXAMPLE: bespoke build, no platform fee) | Check the model’s published specification of the binding. |
| Re-skinning / brand-mark artwork | N/A | ___ (EXAMPLE: one-time + per-release refresh) | ___ (EXAMPLE: one-time + per-release + extension surface) | ___ (EXAMPLE: buyer-owned brand book) | Confirm the per-release refresh cycle. |
| Per-feature acceptance surface | ___ (EXAMPLE: published envelope only) | ___ (EXAMPLE: partner envelope only) | ___ (EXAMPLE: platform + bolt-on acceptance) | ___ (EXAMPLE: per-row contract) | Confirm against sibling 746's worksheet. |
| Store-side publishing tier | n/a (third-party) | ___ (EXAMPLE: buyer or co-managed account) | ___ (EXAMPLE: buyer-owned + extension listing) | ___ (EXAMPLE: buyer-owned account) | Confirm publisher-account ownership in writing. |
| Cloud hosting / data-residency | ___ (EXAMPLE: platform cloud, platform tier) | ___ (EXAMPLE: partner cloud, partner tier) | ___ (EXAMPLE: platform + extension adapter) | ___ (EXAMPLE: buyer-selected region tier) | Confirm regional tier coverage for the buyer's required jurisdiction. |
| Multi-language localization | ___ (EXAMPLE: platform-published languages) | ___ (EXAMPLE: partner-published + re-skin strings) | ___ (EXAMPLE: partner + extension strings) | ___ (EXAMPLE: buyer-owned language build) | Confirm language count per shipped build. |
| Integration scope | ___ (EXAMPLE: platform-published integrations) | ___ (EXAMPLE: partner-published integrations) | ___ (EXAMPLE: platform + extension integration) | ___ (EXAMPLE: buyer-owned integration contract) | Confirm integration partner list against buyer's roadmap. |
| Release cadence / per-year maintenance | ___ (EXAMPLE: platform cadence, buyer on train) | ___ (EXAMPLE: partner cadence + re-skin refresh) | ___ (EXAMPLE: partner cadence + extension QA) | ___ (EXAMPLE: buyer-owned cadence and QA budget) | Confirm per-release QA scope. |
| Exit / switch-out envelope | ___ (EXAMPLE: lock-rebind cost, no event migration) | ___ (EXAMPLE: partner exit terms) | ___ (EXAMPLE: extension re-build cost) | ___ (EXAMPLE: OEM-by-OEM re-validation) | Confirm exit terms in writing. |
| Acceptance testing / QA labor | ___ (EXAMPLE: minimal) | ___ (EXAMPLE: light) | ___ (EXAMPLE: moderate) | ___ (EXAMPLE: heavy) | Confirm QA hours per release. |
A row that arrives at the steering committee without a filled cell is a row that cannot be signed. A worksheet with even one blank row is a worksheet the buyer's CFO will not approve.
Illustrative Scenario: A 120-Room Hotel-Group Pilot With a House-Brand Residential Line
Consider a 120-room hotel group — call it the Pacific Crest Hospitality group — that is launching a house-brand residential smart-lock line for the 38 long-stay units it operates alongside its hotel rooms. The group has a thin in-house QA team (two engineers, no native mobile developer), a regional data-residency requirement (the hotel-class operations must host in-region; the residential line must host in-region; the binding must support both residency postures), and a brand-distinctive shelf presence goal (the residential line must look like a Pacific Crest product on the app-store screenshot, not a third-party accessory). The hotel-class line is managed through the hotel PC software for card encoding and room assignment — that lane is not in the four-scenario ring. The residential line is the lane the arena scores.
| Buyer-profile decision | Round-by-decision read | Scenario recommendation |
|---|---|---|
| Brand-distinctive shelf presence is a non-negotiable. | R2 (brand) cannot be ≤ 2. | Eliminates A. |
| Regional data residency is required for the residential line. | R5 (residency) cannot be ≤ 2. | Eliminates A; B is borderline because the partner's published region tier may not include the buyer's jurisdiction. |
| Per-feature acceptance must read row-by-row against the OEM APP requirements worksheet. | R3 (per-feature) cannot be ≤ 2. | Eliminates B unless the per-feature worksheet is inside the partner's published envelope. |
| Two-engineer in-house QA cannot carry a recurring per-release bolt-on QA budget. | R7 (maintenance) cannot be ≤ 2. | Eliminates C and D. |
The four decision points above leave a narrow recommendation: scenario B (white-label / re-skin) on a partner envelope that publishes regional tier coverage for the buyer's jurisdiction and a per-feature acceptance surface inside the partner's published envelope, with a contractual commitment that the re-skin refresh cycle on R7 is the partner's per-release responsibility rather than the buyer's. If the partner envelope does not meet the R5 residency or R3 per-feature requirements, scenario C is the fallback — at the cost of a recurring per-release bolt-on QA budget the buyer's two-engineer team must fund.
This is not a customer story. It is an illustrative scenario the buyer's steering committee can stress-test its own decision against — the four decision points are the canonical pressures a 120-room hotel-group-with-residential-line profile carries, and the scenario recommendation as scored honors all four. A buyer profile with different pressures will score differently; the worksheet above is the tool the steering committee uses to read its own profile against the four scenarios.
Demands-in-Writing Table: What to Ask the Supplier at Quote Stage
The demands below are the questions the buyer's steering committee writes into the RFQ packet at quote stage. Every demand is a question the supplier must answer in writing against a dated per-SKU and per-batch quotation; a supplier that cannot answer the demand in writing is a supplier the buyer's steering committee cannot sign against.
| # | Demand | Why it matters | Where it lands in the worksheet |
|---|---|---|---|
| 1 | State the binding name (TTLock / Tuya / Doodle / partner shell) the chosen SKU supports. | Every other row of the worksheet inherits this binding. | Row 1 (binding license). |
| 2 | State the per-feature scope the binding publishes for the chosen SKU. | Per-feature acceptance surface against sibling 746's worksheet. | Row 3 (per-feature acceptance). |
| 3 | State the cloud region tier the binding publishes for the buyer's required jurisdiction. | R5 (residency) cannot be ≤ 2 without this. | Row 5 (residency). |
| 4 | State the language count the binding publishes and the re-skin envelope covers. | R4 (localization) cannot be signed without this. | Row 6 (localization). |
| 5 | State the store-side publisher-account ownership (third-party / buyer / co-managed) the binding supports. | R2 (store control) and R7 (release cadence) inherit this. | Rows 2, 4 (re-skin, publishing). |
| 6 | State the per-release QA scope the binding carries vs the scope the buyer must fund. | R7 (maintenance) cannot be ≤ 2 without this. | Row 8 (release cadence), 10 (QA labor). |
| 7 | State the exit / switch-out terms — lock-rebind cost, event-log migration, partner-exit clause. | R8 (exit) cannot be ≤ 2 without this. | Row 9 (exit envelope). |
| 8 | State the integration list the binding publishes (PMS / channel manager / CRM / ERP) and the contract surface for any integration the buyer must add. | R3 (per-feature) and R6 (audit / integration) inherit this. | Row 7 (integration scope). |
| 9 | State the per-year operating spend (cloud, store fee, support hours, language drift) for the binding at the buyer's required fleet size. | Year-one / year-three parity depends on this. | Row 8 (release cadence). |
| 10 | State the audit / event-log depth the binding exposes to the APP on the chosen SKU — record count, retrieval cadence, multi-door grouping. | R6 (audit / integration) cannot be ≤ 2 without this; per-model specifics — check the model’s published specification. | Row 3 (per-feature acceptance). |
A demand that the supplier answers with "we'll figure it out at project stage" is a demand the supplier has not answered. The steering committee's RFQ packet is a list of demands with answers; a packet with unanswered demands is a packet that cannot move to the worksheet-fill stage.
The Out-of-Catalog Firewall
The APP scenario arena is bounded by what the catalog publishes. The four scenarios all assume the catalog APP platforms are TTLock, Tuya, or Doodle for consumer-app bindings, and the hotel line is managed through hotel PC software for card encoding and room assignment. Anything outside that firewall is not in this arena.
| Firewall | What stays outside | Why |
|---|---|---|
| Matter | Any Matter-APP binding assertion | Not in catalog. |
| Zigbee | Any Zigbee-APP binding assertion | Not in catalog. |
| Z-Wave | Any Z-Wave-APP binding assertion | Not in catalog. |
| Thread | Any Thread-APP binding assertion | Not in catalog. |
| Apple Home Key | Any Home Key wallet-credential assertion | Not in catalog. |
| UWB | Any Ultra-Wideband APP-binding assertion | Not in catalog. |
| Proprietary mesh | Any supplier-proprietary mesh APP-binding assertion | Not in catalog. |
A buyer profile whose roadmap requires any of the rows above is a buyer profile outside the catalog. The steering committee must either accept the catalog firewall and pick one of the four scenarios, or move to a non-catalog lane the factory does not publish — and a non-catalog lane is a lane the RFQ checklist and the OEM supply agreement considerations treat as a scope change, not a configuration.
The Catalog Coverage Reminder
The factory floor's APP posture is the catalog's APP posture. The 79 published models in the catalog carry the same APP-binding menu the four scenarios inherit — TTLock, Tuya, or Doodle for consumer-app locks, hotel PC software for hotel-class card-encoding workflows. The four scenarios do not invent new ones, and a supplier that promises a per-catalog-SKU custom APP binding without going through scenario D is a supplier the steering committee must ask to scope the work in writing under the OEM APP requirements document before the worksheet is signed.
The cluster-level first-party facts are the catalog's published scope: 79 models across the catalog, with 24 in the hotel line, 18 keypad, 10 outdoor, 9 RFID, 6 face recognition, 6 cabinet, 3 video camera, 3 glass. The four-scenario arena covers the consumer-residential, residential / multi-family, commercial-building, and short-term-rental lanes; the hotel line is the parallel hotel PC software lane. The cluster fact that 10+ years of smart-lock production have shipped into 80+ countries is the buyer's confidence anchor that the catalog's APP binding menu is a production menu, not a roadmap — the binding has shipped at scale.
Closing Hand-Off: Cost, Project, and Procurement
The APP development cost envelope is one slice of the OEM project cost envelope. The four scenarios above score how the slice moves under different pressures; the OEM project cost structure scores the other slices the buyer signs against — one-time setup and tooling, per-unit hardware and electronics, software and firmware customization, packaging artwork and tooling, certification, freight, customs, warranty, and spare-parts reserve. The APP scenario decision moves every one of those other slices because the binding choice drives the per-unit electronics, the integration scope, and the per-year operating envelope.
The buyer profile that signs the APP scenario worksheet signs the OEM APP requirements worksheet on the same date, signs the OEM project cost structure worksheet on the same date, and routes the signed envelope into the quotation comparison workbench to read against any other supplier's per-scenario quotation the steering committee is evaluating. The exact figures for every cell arrive from the supplier; the buyer's job is to write the demands, fill the cells against the dated product page, and sign the worksheet.
The four scenarios do not collapse into a single number. The four scenarios are a price-of-freedom table, and the buyer's steering committee signs the scenario whose price-of-freedom matches the brand's appetite for fast / slow, surface / depth, lock-in / portability. Every exact figure for every cell routes to Request a quote against a dated per-SKU and per-batch quotation, with a secondary route to Order samples for the lock-side SKU the binding hangs off, and a tertiary route to the bluetooth-lock category page for the catalog's APP-bound SKUs at the consumer / residential / commercial line.

