Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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.

Click below to expand this section for guidance on managing your devices at scale.

...

titleManaging Devices at Scale: Click to Expand

Device Selection and Pre-Installation

The first, and most important, step in this process is selecting the correct device for your project. Keeping the user experience in mind is critical to ensure you choose phones that are of sufficient quality and are software compatible for the app you created.

Make sure to specify minimum requirements for the devices that needed to be procured, in accordance with the project’s objectives. To ensure you choose the correct device and mitigate any mistakes that happen during preinstallation, here are a few key learnings from our pre-procurement experience:

  • Review every feature of the app comprehensively to decide what device specifications are necessary to support your app’s functionalities. From audio format support and processor speed to storage capacity and battery, it is essential to test how the app functions on various devices to hone in on the minimum specifications. You should also consider how the industry landscape is evolving to future-proof the specs as much as possible.

  • Clearly outline minimum specifications and software compatibility checks for device selection. This will help you articulate and standardize the requirements to ensure all stakeholders are aligned.

  • Describe in-detail what state the device should be in after pre-installation is done. Be sure to give clear directions on what the device settings should be, and what the app should look like on the device.

  • Prepare for any eventuality. Specify that the software should be removable and reinstallable from all phones. If all else fails in the field, at least it is possible to start from scratch!

See Mobile Device Selection and Mobile Device Planning for more information.

Sample Testing

If you are working with a vendor and ordering devices, you want to ensure that what you choose is compatible with the app, and that pre-installation is done correctly.

...

  1. Select devices that meet the minimum quality and software compatibility requirements for your project.

  2. 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).

  3. Outline minimum specifications and software compatibility checks to standardize requirements and align all stakeholders.

  4. Detail the expected state of the device post-pre-installation, including device settings and app appearance.

  5. Ensure software can be removed and reinstalled if necessary.

  6. Refer to detailed guidelines at Mobile Device Selection

Sample Testing

  1. Request a sample of re-installed devices from the vendor.

  2. Define testing requirements to

...

  1. align with the vendor

...

  1. .

...

  1. Assign accountability for specifications

...

  1. outside

...

  1. your scope (e.g., touchscreen life

...

  1. , processor configuration

...

  1. ) and request manufacturer certification if needed.

  2. Conduct high-load and field sanity tests on the sample device with the application

...

  1. (see here: Test your Application Size (Load Testing) )

...

Quality Check

...

  1. Perform quality checks on each device consignment within a few days of receipt.

...

  1. Define and document QC criteria

...

  1. based on minimum specs and pre-installation documents

...

  1. .

...

  1. Determine sample size

...

  1. and

...

  1. thresholds for

...

  1. consignment approval.

  2. Align responsibilities

...

  1. for

...

  1. QC

...

  1. outcomes before

...

  1. procurement

...

  1. begins, including ensuring vendor accountability for addressing hardware or pre-installation issues

...

  1. .

...

Test devices on-site and build capacity for local or regional teams to be responsible for this exercise.

Device Set-up

...

  1. Document and

...

  1. share step-by-step guidelines

...

  1. for device configuration to ensure uniform setup. See here for help: Preparing Android Devices

  2. Account for logistics such as seating arrangements, device transport, Wi-Fi connectivity,

...

  1. device

...

  1. tracking, and boxing.

  2. Include essential user information (e.g., username, password, Google account credentials

...

  1. ) with each device.

  2. Arrange a well-trained setup team in advance by planning venue details, meals, and energizer activities

...

See this for more information: Preparing Android Devices

Distribution and Management

You’re ready to distribute your phones! Before the job is done, we must prepare for a few scenarios, such as: What if a phone is damaged or stolen? Who should a user contact if he/she has an issue with the application or a SIM card? How are the devices tracked if a user resigns and a new person joins in that role? Thinking through device and SIM card management is an important step of this process.

...

  1. to support the setup process.

Distribution and Management

  1. Distribute devices at training sessions to ensure correct allocation and address issues in person.

  2. Maintain a master spreadsheet

...

  1. with all relevant device and user information (e.g.,

...

  1. phone

...

  1. numbers, usernames

...

  1. )

  2. Set up a call center or help desk

...

  1. for

...

  1. first-line

...

  1. support for

...

  1. hardware or software issues.

  2. Record and analyze

...

  1. reported issues and field feedback to

...

  1. continuously improve the application and implementation.