01
Brand file
Provide the app name, logo files, colour palette, icon and required language list.
White-label mobile access app
White-Label Mobile Access App for Smart Access
Use one application identity across selected video intercom, smart-lock and access-control models. Set the device mix, brand files, language scope and target market before preparing the release package.
Discuss white-label scope
OEM/private-label programme starts at 500 units
Your brandWhite-label app
White-label release review
Define the application scope before release.
Brand files, device programme, language deliverables and order plan are reviewed together so each party works from the same release record.
02
Identity record
List the screens, notifications and store listings that carry your brand, so no part of the release ships with mixed branding.
03
Device programme
Confirm the models, product lines and destination market included in the order brief.
04
Release package
Receive the confirmed scope record and release materials for the reviewed order.
Release control record
Control brand scope before order release.
This record keeps brand files, language deliverables, selected device models and handover materials tied to the same programme.
Brand identityApproved app name, logo, colour palette, app icon and visual-use guidance.
Language deliverablesInterface labels and language content reviewed for the named destination market.
Device programmeSelected video intercom, smart lock and access-control models covered by the application scope.
Release fileConfirmed device list, brand-scope summary and delivery materials for the reviewed order.
One app · selected devices
One branded entry point for selected access devices.
The application may cover a reviewed mix of video intercom, smart locks and access control. Device inclusion follows the agreed programme, not a catalogue-wide assumption.
Video Intercom
Include selected video-intercom models and their app-facing functions in the reviewed programme.
Smart Locks
Include selected smart-lock models where their approved app functions are in scope for the order.
Access Control
Include selected reader, controller or access-control products according to the reviewed device list.
Ownership and support
Settle who owns the app before release.
A branded app keeps running after the hardware ships. Agree these points in the order brief so store publishing, data handling and end-user support each have a named owner.
Publisher accountWhich developer account publishes the app on the App Store and Google Play, and who holds the account login and signing keys.
Platforms and functionsWhich phone platforms the order covers, and which functions each selected model exposes in the app, such as call answering, door release and credential management.
Cloud and dataWhich cloud service the app connects to, where account and access-log data is hosted, and who acts as data controller for end users in the destination market.
Updates and supportWho releases app updates after launch, for how long the branded version is maintained, and who answers end-user support requests.
Privacy and store listingWho writes and hosts the privacy policy, terms of use and store listing text that the app stores require.
White-label application review
Prepare a release brief that can be assessed.
A focused brief allows the product, branding and language scope to be assessed against the intended order.
Send white-label briefWhich app elements are reviewed?
App name, logo, icon, colour palette and language deliverables are reviewed against the selected device programme.
Which product lines can be included?
A programme may combine selected video intercom, smart lock and access-control models for the named market.
What should a white-label brief include?
State the target market, selected product categories, brand assets, language requirements and planned order quantity.
What is the minimum order quantity?
White-label application orders start at 500 units. Final device selection and release materials are confirmed with the order brief.