> For the complete documentation index, see [llms.txt](https://docs.amltd.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.amltd.com/dc-works/suites-and-deployment/deploy-a-suite-to-an-android-device.md).
# Deploy a Suite to an Android Device
Learn how to install the DC Works Android application, display a Suite’s enrollment barcode, enroll a device, and verify the deployed Suite.
Deploying a Suite connects an Android device to the selected Suite and downloads the Suite, its Applets, and the related data required by the configuration.
### Before you begin
Confirm that:
* The Suite has been created, configured, and saved.
* The correct Applets are included.
* Each App Button opens the intended Applet.
* The Android device has a working network connection.
* The DC Works application is installed or available for installation.
* You can access the Suite’s enrollment barcode.
* The device has permission to use its scanner or camera if required.
The initial enrollment and download require connectivity to DC Works.
### Install the DC Works application
The DC Works application may already be installed on the Android device. If it is present, open it and proceed to enrollment.
If it is not installed, download the Android APK from DC Works.
#### Download the application
To obtain the APK:
1. Open **Get Mobile App** in DC Works.
2. Display the application-download barcode.
3. Scan the barcode with the Android device.
4. Download the DC Works APK.
5. Open the downloaded file.
6. Follow the Android installation prompts.
7. Open DC Works after installation.
Scan the Get Mobile App barcode to download and install the DC Works Android application.
Android may require permission to install an application from the source used to download the APK. Follow your organization’s device-security policies when enabling this permission.
{% hint style="info" %}
Supported AML devices may have the DC Works application preloaded. Check the device before downloading the APK.
{% endhint %}
### Locate the Suite enrollment barcode
Each Suite has its own enrollment barcode.
To display it:
1. Open **Suites** from the DC Works main navigation.
2. Locate the Suite.
3. Find the **Enrollment Barcode** column.
4. Select the eye icon.
The enrollment barcode appears on screen.
Select the eye icon to display the Suite’s enrollment barcode.
Use the download icon when the barcode must be saved or printed for enrollment at another location.
{% hint style="warning" %}
An enrollment barcode provides access to its associated Suite. Share it only with users or administrators authorized to enroll devices.
{% endhint %}
### Enroll the Android device
To enroll the device:
1. Open the DC Works application on the Android device.
2. Select the green **Enroll** button.
3. Display the Suite’s enrollment barcode on another screen or printed page.
4. Scan the barcode using the device’s hardware scanner or the blue **Scan** camera option.
5. Wait while DC Works processes the enrollment.
6. Allow the device to download and install the Suite, its Applets, and related data.
7. Confirm that the Suite opens on the device.
Select Enroll to begin connecting the device to a Suite.
Use the hardware scanner or blue Scan camera option to scan the enrollment barcode.
Keep the device connected until the initial download has completed.
### Understand what enrollment downloads
Enrollment associates the Android device with the selected Suite.
The device receives:
* The Suite launcher.
* The Applets included in the Suite.
* The Applets’ pages and fields.
* The applicable actions and conditions.
* The related data required by the Suite configuration.
After successful enrollment, the **# Devices Assigned** value in the Suites workspace reflects the device assignment.
The amount of time required depends on the Suite’s size, its Applets, its related data, and the network connection.
### Verify the deployed Suite
After enrollment, confirm that:
* The correct Suite opens.
* The Suite name and branding are correct.
* The background and logo display properly.
* All required App Buttons are present.
* Each App Button opens the correct Applet.
* Page navigation works.
* Fields fit the device screen.
* Text and button labels are readable.
* Scanner, camera, sound, and other device features work as intended.
* Data can be retrieved and saved correctly.
Test the same workflow that device users will perform.
### Test barcode scanning
If the Applets use a hardware scanner, confirm that:
* The scanner is enabled.
* The correct Input field receives the scanned value.
* Scanner-only and keyboard/scanner capture settings behave as intended.
* The barcode type is supported.
* Scan Actions execute in the expected order.
* The captured value reaches the correct bound record.
Camera-based scanning should be tested separately when it is part of the workflow.
### Test database operations
Use test data to confirm that:
* Lookup actions retrieve the intended records.
* Bound fields display the correct values.
* Add Record creates the expected database entry.
* Update Record changes the correct entry.
* Required fields prevent incomplete submissions.
* Delete operations affect only the intended records.
### Test offline operation
If **Offline Support** is enabled:
1. Complete the initial enrollment and download while connected.
2. Confirm that the required Applets and data are available.
3. Disconnect the device from the network.
4. Run the intended offline workflow.
5. Reconnect the device.
6. Confirm that the applicable data synchronizes correctly.
Offline testing should include interruptions during realistic parts of the workflow.
Do not assume that enabling Offline Support makes every operation available offline. Test all required database, API, and device-dependent functions.
### Update a deployed Suite
When **Auto Update** is enabled, deployed devices can receive updated Suite configurations.
After changing the Suite or one of its Applets:
1. Save the changes.
2. Confirm that **Auto Update** is enabled.
3. Open or refresh the Suite on the enrolled device.
4. Allow the update to complete.
5. Retest the affected Applets and workflows.
An **Update Button** can also be added to the Suite launcher when users need a visible update control.
Detailed update testing is covered in **Test and Update a Deployed Suite**.
### Troubleshoot application installation
If the APK does not install:
* Confirm that the download completed.
* Confirm that the device supports the application.
* Review Android’s installation permissions.
* Verify that sufficient storage is available.
* Download the APK again if the file is incomplete.
* Follow the organization’s device-security policies.
### Troubleshoot barcode enrollment
If the enrollment barcode does not scan:
* Increase the barcode size on the display.
* Increase the display brightness.
* Clean the scanner window or camera lens.
* Hold the device steady and adjust the scanning distance.
* Confirm that the correct Suite barcode is displayed.
* Try the hardware scanner and the blue Scan camera option separately.
* Download or print the barcode if scanning from the display remains difficult.
### Troubleshoot Suite download
If enrollment is accepted but the Suite does not download:
* Confirm that the device has a reliable network connection.
* Keep DC Works open until the download completes.
* Confirm that the Suite still exists.
* Verify that the intended Applets are included.
* Review the device assignment in the Suites workspace.
* Retry the enrollment after correcting the issue.
If the Suite opens but appears incomplete, save the Suite again and verify its configuration in the Suite Editor.
### Complete deployment testing
Before placing the device into operation, confirm that:
* Enrollment completed successfully.
* The correct Suite is assigned.
* The current Suite version is installed.
* All Applets open correctly.
* Hardware features work.
* Database actions have been tested.
* Offline behavior has been tested if required.
* Updates can reach the device.
* The device user can complete the workflow without access to the Suite Editor.
### Next
Continue to **Deploy a Suite as a Web App** to learn how to assign a Suite and Web License and make it available through a web browser.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.amltd.com/dc-works/suites-and-deployment/deploy-a-suite-to-an-android-device.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.