...
| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Considerations for All Projects
How many devices should you buy?
When planning to purchase devices for a project, it's advised to buy an extra 10% on top of your total user count to compensate for potential losses, breakages, or for use in training and technical support. Historical data suggests a 2-3% rate of loss or theft over three years.
Will you have network coverage?
For selecting a data plan, ensure the network provider offers robust coverage in your project area. Consulting local residents or conducting field tests can help determine the best provider.
Below are some tools that you can use:
...
https://www.opensignal.com/coverage-maps
...
How should you select your devices?
See here: Mobile Device Selection
How should you test your devices?
Check each device shipment a few days after you get it, and note the Quality Control (QC) criteria based on the minimum specs and pre-installation documents. Decide on the sample size and approval thresholds, and make sure everyone knows their responsibilities for QC outcomes before procurement starts, including making sure vendors fix any hardware or pre-installation issues.
You should also conduct high-load and field sanity tests on the sample device with the application (see here: Test your Application Size (Load Testing) )
How much data should you purchase?
Many projects find that a monthly data allowance of 100 MB is sufficient. To estimate usage, consider that each form submission is roughly 7-10kb. For instance, submitting 20 forms daily over 25 working days requires about 5MB per month. For example, for a project where the FLW submits 20 forms a day, 25 days a month: 20 forms x 25 days a month x 10kb/form = 5MB
For selecting a data plan, ensure the network provider offers robust coverage in your project area. Consulting local residents or conducting field tests can help determine the best provider.
Below are some tools that you can use:
How will you charge your devices?
Device charging is crucial, especially in areas with limited electricity. Solutions include home charging for those with electricity, providing solar chargers, or establishing central charging stations, which are cost-effective but have higher theft risks. In some cases, reimbursing charging costs may be necessary.
How will you set up your devices?
See Preparing Android Devices and Installing CommCare on Android Devices
How will you distribute your devices?
We recommend distributing devices at training sessions to ensure correct allocation and address issues in person.
How will you
...
manage your devices?
Below are some apps that we have used to support device management.
https://play.google.com/store/apps/details?id=com.teslacoilsw.launcher&hl=en
https://play.google.com/store/apps/details?id=com.gears42.surelock
https://play.google.com/store/apps/details?id=com.kiddoware.kidsplace&hl=en_US&gl=US
How will you manage your devices
Device management requires a clear contract and protocol to outline phone use and procedures for lost or damaged equipment. For comprehensive guidance, Dimagi's toolkit on device management at scale offers valuable resources.
Considerations For Projects at Scale
For projects that will be operating at scale, this pages provides guidance and key learnings from Dimagi project managers who have supported projects with hundreds of thousands of devices. This section looks back at our key learnings for managing devices at scale, from selection all the way to delivery.
Device Selection and Pre-Installation
Select devices that meet the minimum quality and software compatibility requirements for your project.
Specify minimum device requirements based on the project’s objectives, ensuring the chosen devices can support your app’s functionalities (e.g., audio format support, processor speed, storage capacity, battery life).
Outline minimum specifications and software compatibility checks to standardize requirements and align all stakeholders.
Detail the expected state of the device post-pre-installation, including device settings and app appearance.
Ensure software can be removed and reinstalled if necessary.
Refer to detailed guidelines at Mobile Device Selection
Sample Testing
Request a sample of re-installed devices from the vendor.
Define testing requirements to align with the vendor.
Assign accountability for specifications outside your scope (e.g., touchscreen life, processor configuration) and request manufacturer certification if needed.
Conduct high-load and field sanity tests on the sample device with the application (see here: Test your Application Size (Load Testing) )
Quality Check
Perform quality checks on each device consignment within a few days of receipt.
Define and document QC criteria based on minimum specs and pre-installation documents.
Determine sample size and thresholds for consignment approval.
Align responsibilities for QC outcomes before procurement begins, including ensuring vendor accountability for addressing hardware or pre-installation issues.
Device Set-up
Document and share step-by-step guidelines for device configuration to ensure uniform setup. See here for help: Preparing Android Devices
Account for logistics such as seating arrangements, device transport, Wi-Fi connectivity, device tracking, and boxing.
Include essential user information (e.g., username, password, Google account credentials) with each device.
Arrange a well-trained setup team in advance by planning venue details, meals, and energizer activities to support the setup process.
Distribution and Management
...
Distribute devices at training sessions to ensure correct allocation and address issues in person.
...
Make sure that you maintain a master spreadsheet with all relevant device and user information (e.g., phone numbers, usernames)
...
Set up a call center or help desk for first-line support for hardware or software issues.
...
. Once devices are out, record and analyze reported issues and field feedback to continuously improve the application and implementation.