專用裝置總覽
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
Android 提供的 API 可用來管理用於特定用途的裝置。
本開發人員指南將介紹這些 API。如果您是企業行動管理服務 (EMM) 開發人員或解決方案整合商,請參閱本指南,瞭解如何開始使用。
可在何處使用專用裝置?
專用裝置 (原稱為公司擁有的單一用途,或 COSU) 是具有特定用途的全代管裝置。Android 提供的 API 可協助您建立符合員工和客戶特定需求的裝置:
- 員工面對:庫存管理、現場服務管理、運輸和物流
- 客戶端:資訊站、數位電子看板、餐旅服務登記
專用裝置功能
Android 提供的 API 可協助使用專屬裝置的使用者專注於工作。您通常會透過開發的自訂主畫面應用程式呼叫這些 API。您的自訂主畫面應用程式可以使用下列部分或所有 API:
- 以類似資訊站的方式執行系統 (沉浸式) 執行系統,其中裝置使用鎖定任務模式,鎖定在已加入許可清單的應用程式組合中。
- 管理臨時和次要使用者,以便與多位使用者 (例如輪班工作站或公開資訊站使用者) 共用裝置。
- 請快取應用程式套件,避免裝置為每位臨時使用者再次下載相同的應用程式。
- 凍結作業系統版本,在重要時段暫停無線更新 (OTA)。
如要呼叫這些 API,應用程式必須是全代管裝置的管理員 (下節說明)。
受管理的裝置
由於專用裝置可能會無人管理,或用於重要工作,因此您必須保護裝置。為避免濫用,專屬裝置會全代管並由「管理員元件」擁有 (一般管理員元件也會管理使用者)。全代管部署作業適用於公司擁有的裝置,僅供工作用途使用。如要進一步瞭解 Android 裝置管理,請參閱 Android Enterprise 總覽指南。
視解決方案需求和業務目標而定,您可以透過下列其中一種方式管理裝置:
測試
如果您計劃支援第三方 EMM,請使用 EMM 的解決方案製定端對端測試計畫。
我們也提供以下資源,協助您建立自己的開發或測試環境:
在開發期間,您可以使用 Android Debug Bridge (ADB),將應用程式設為全代管裝置的管理員。
佈建專用裝置
解決方案開發完成後,您就可以佈建 Android 裝置,或設定要管理的裝置。如要佈建裝置,請完成下列步驟:
- 將裝置恢復原廠設定。
註冊裝置。建議您使用包含裝置佈建設定的 QR code。然後,IT 管理員就可以掃描程式碼來佈建裝置。
如果無法使用 QR code,您可以透過其他方式註冊裝置,例如 NFC 資料傳輸或輸入 ID。
說明文件
其他資源
如要進一步瞭解如何開始使用專用裝置,請參閱下列文件:
這個頁面中的內容和程式碼範例均受《內容授權》中的授權所規範。Java 與 OpenJDK 是 Oracle 和/或其關係企業的商標或註冊商標。
上次更新時間:2025-07-26 (世界標準時間)。
[null,null,["上次更新時間:2025-07-26 (世界標準時間)。"],[],[],null,["# Dedicated devices overview\n\nAndroid includes APIs to manage devices that are dedicated to a specific purpose.\nThis developer's guide introduces these APIs. If you're an enterprise mobility\nmanagement (EMM) developer or solution integrator, read this guide to get\nstarted.\n\nWhere are dedicated devices used?\n---------------------------------\n\n*Dedicated devices* (formerly called corporate-owned single-use, or COSU) are\nfully managed devices that serve a specific purpose. Android provides APIs that\ncan help you create devices that cater to employee- and customer-specific needs:\n\n- **Employee-facing:** Inventory management, field service management, transport and logistics\n- **Customer-facing:** Kiosks, digital signage, hospitality check-in\n\nDedicated device features\n-------------------------\n\nAndroid includes APIs to help people using dedicated devices focus\non their tasks. You typically call these APIs from a custom home app that you\ndevelop. Your custom home app can use some, or all, of the following APIs:\n\n- Run the system in an immersive, kiosk-like fashion where devices are locked to an allowlisted set of apps using [lock task\n mode](/work/dpc/dedicated-devices/lock-task-mode).\n- Share a device between multiple users (such as shift workers or public-kiosk users) by [managing ephemeral and secondary\n users](/work/dpc/dedicated-devices/multiple-users).\n- Avoid devices downloading the same app again for each temporary user by [caching app packages](/work/dpc/dedicated-devices/cookbook#cache-apps).\n- Suspend over-the-air (OTA) system updates over critical periods by [freezing\n the operating system version](/work/dpc/system-updates#freeze-periods).\n\nTo call these APIs, apps need to be the admin of a fully managed\ndevice---explained in the following section.\n\nManaged devices\n---------------\n\nBecause dedicated devices might be left unattended or used in critical tasks,\nyou need to secure the device. To prevent misuse, dedicated devices are *fully\nmanaged* and owned by an [admin component](/reference/android/app/admin/DeviceAdminReceiver) (the admin component typically\nmanages the users too). Fully managed deployments are for company-owned devices\nthat are used exclusively for work purposes. To learn more about Android device\nmanagement, read the Android Enterprise [Overview](https://developers.google.com/android/work/overview) guide.\n\nDepending on your solution's needs and your business goals, you can manage the\ndevice in one of the following ways:\n\n- [Develop your own device policy controller (DPC)](/work/dpc/build-dpc), combining it with a [custom home app](#features).\n- Use the [Android Management\n API](https://developers.google.com/android/management/) to manage the device and any custom apps.\n- Use a [third-party EMM\n solution](https://androidenterprisepartners.withgoogle.com/emm/) that supports lock task mode and other dedicated device features.\n\nTesting\n-------\n\nIf you're planning to support a third-party EMM, develop an end-to-end testing\nplan using the EMM's solution.\n\nWe also provide the following resources, which you can\nuse to create your own development or test environment:\n\n- [Test DPC](https://play.google.com/store/search?q=testdpc) app on Google Play\n- [Dedicated device source\n code](https://github.com/googlesamples/android-testdpc/tree/master/src/main/java/com/afwsamples/testdpc/cosu) (Test DPC) on GitHub\n\nWhile you're still developing, you can [set your app as the\nadmin](/work/dpc/dedicated-devices/cookbook#dev-setup) of a fully managed device\nusing the Android Debug Bridge (ADB).\n\nProvision dedicated devices\n---------------------------\n\nWhen you've finished developing your solution, you're ready to *provision*\nAndroid devices, or set up the devices for management. To provision a device,\ncomplete the following steps:\n\n1. Factory reset the device.\n2. Enroll the device. We recommend [using a QR\n code](https://developers.google.com/android/work/prov-devices#qr_code_method)\n that contains a provisioning config for device. An IT admin can then scan the\n code to provision the device.\n\n If you cannot use a QR code, you can enroll devices through [other\n methods](https://developers.google.com/android/work/overview#device_and_work_profile_provisioning),\n such as NFC bumping or by entering an identifier.\n\nDocumentation\n-------------\n\nAdditional resources\n--------------------\n\nTo learn more about getting started with dedicated devices, read the following\ndocuments:\n\n- [Android Enterprise\n overview](https://developers.google.com/android/work/overview) that introduces device management.\n- [Build a device policy controller](/work/dpc/build-dpc) explains how to develop a DPC.\n- [Dedicated devices cookbook](/work/dpc/dedicated-devices/cookbook) gives examples for features typical of dedicated devices."]]