How do I Deploy the Read&Write for iOS App to Multiple Devices?

Deploying and Licensing Read&Write for iOS via MDM

This guide provides instructions for IT administrators to deploy the Read&Write for iOS app and activate premium features across multiple devices using a Mobile Device Management (MDM) solution.

Prerequisites

Before you begin, please ensure you have the following:

• An MDM solution (e.g., Jamf School, Jamf Pro, Microsoft Intune, Kandji, Mosyle).

• Apple School Manager or Apple Business Manager.

• Read&Write for iOS app licenses acquired through the Apps and Books program (formerly VPP).

• Target devices that are supervised (recommended for best results).

Method 1: Using Managed App Configuration (Recommended)

This is the most efficient method for licensing the app in bulk. It allows you to remotely push the license information directly to the app on each device.

Step 1: Deploy the App as a Managed App

For Managed App Configuration to work, Read&Write for iOS must be deployed as a managed app from your MDM solution. Do not have users install it manually from the App Store.

1. Log in to your MDM dashboard.

2. Ensure you have licenses for Read&Write for iOS available in your Apps and Books library.

3. Assign the app to your target device groups and push the installation.

Step 2: Create and Apply the Configuration

Your MDM will have a section for the app titled "Managed Configuration," "App Configuration," or similar. In this section, you will provide a key-value pair to license the app.

Note: Keys are case-sensitive and must be entered exactly as shown.

Most MDM platforms provide a simple interface where you enter the Key (e.g., RWTakeHomeCode) and the Value (your actual code) into separate fields.

If your MDM requires you to use .plist or .xml format, use the template below. Paste this into the configuration field and replace the key and value with your information.  Use RWTakeHomeCode, RWEmail or RWSerial as required.

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">

<dict>

    <key>RWTakeHomeCode</key>

    <string>YOUR_CODE_HERE</string>

</dict>

</plist>

If you get format errors, your MDM probably expects a different format, so try removing the following:

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

If you still get format errors; try removing the following as well:

<plist version="1.0"> and </plist>

Step 3: Scope and Save

Assign or "scope" this configuration to the same devices that received the app. Once saved, your MDM will send the configuration to the devices, and the app's premium features will be unlocked automatically.

Method 2: Alternative Activation Methods

Use these methods if your MDM does not support Managed App Configuration or for non-MDM deployments.

Read&Write Domain License Sign-in

If your organisation has a domain-wide license, no extra configuration is needed. Simply deploy the app and instruct users to sign in with their Google or Microsoft school/work account to activate their premium features.

Activation via URL Link

You can send users a special URL to activate their app. The app must be installed before the user clicks the link.

1. Construct the URL:

• For App Version 7.10 or newer: readwriteforipad://register?email=YOUR_EMAIL_ADDRESS

• For App Version 7.9 or older: readwriteforipad://register?serial=YOUR_SERIAL_CODE

2. Distribute the Link: Email the link to your users or post it on an internal website.

• Important: Do not add http:// or https:// to the beginning of the link.

• For security, consider masking the link behind text (e.g., "Click here to activate Read&Write") to avoid exposing your license code.

For Small Deployments (Not Recommended for Volume)

In-App Purchase

This method is intended for individual users, not institutional deployment. In-App Purchases are tied to a single Apple ID and do not support volume purchasing. Each device would need to complete the purchase process manually. We do not recommend this for licensing more than a few devices.