From 53c96f4ce63b764338181070b46d64f307575a4c Mon Sep 17 00:00:00 2001 From: finalerock44 <77282157+finalerock44@users.noreply.github.com> Date: Wed, 2 Sep 2026 12:31:07 +0100 Subject: [PATCH 1/5] Add device configuration support policy --- getting-started/devices-configuration.md | 39 ++++++++++++++++++++++++ 1 file changed, 39 insertions(+) diff --git a/getting-started/devices-configuration.md b/getting-started/devices-configuration.md index a319773..1a01d44 100644 --- a/getting-started/devices-configuration.md +++ b/getting-started/devices-configuration.md @@ -88,3 +88,42 @@ The flags above set the device for the whole upload. When only one flow needs a ### Running your suite across several devices To run every flow against several devices from a single `dcd cloud` invocation use a [device matrix](../configuration/device-matrix.md). + +## Device Support Policy + +We aim to provide a wide range of devices and OS versions so that you can test your apps as thoroughly as you need. However, due to storage constraints we can only provide access to certain devices and OS levels. Our policy on this is written below so you know what to expect. + +If you need a device or OS that we don't currently offer, please feel free to reach out to support on [Discord](https://discord.gg/gm3mJwcNw8) or Slack (Enterprise customers only) or via email at [support@devicecloud.dev](mailto:support@devicecloud.dev) and we'll see what we can do. + +### iOS Support Policy + +We will always aim to have the following devices available as a baseline: + +- The latest even-numbered iPhone model & it's variations, i.e. iPhone 18, 18 Plus, 18 Pro & 18 Pro Max. +- The previous two supported generations of iPhones, i.e. iPhone 16 & iPhone 14. +- The latest generation of iPad Pro. +Additionally we will aim to provide the latest odd-numbered iPhone in it's base configuration if there is a noticeable difference in dimensions however this may not always be possible. + +We will always aim to have the following iOS versions available as a baseline: + +- The latest version plus the previous two. +- These should always be the latest point release. + +It may be possible in some cases to provide support for a beta version however this will be on a case-by-case basis; please contact our Support team if you would like to request this. + +The default configuration will always be the latest even-numbered base iPhone we support running the previous version of iOS, i.e. iPhone 16 running iOS 26. + +### Android Support Policy + +We will always aim to have the following devices available as a baseline: + +- The two latest Google Pixel models & all variations. +- A generic-tablet model. + +We will always aim to have the following Android versions available as a baseline: +- The latest version. +- Any version still supported by Google Play Services. + +It may be possible in some cases to provide support for a beta version however this will be on a case-by-case basis; please contact our Support team if you would like to request this. + +The default configuration will always be the latest base Pixel we support running the previous version of Android, i.e. Pixel 10 running Android 16/API 36. From 735ccee3b4d6ec4a1f3d60728269850915ea58f3 Mon Sep 17 00:00:00 2001 From: finalerock44 <77282157+finalerock44@users.noreply.github.com> Date: Wed, 2 Sep 2026 12:34:13 +0100 Subject: [PATCH 2/5] Add commitment to 30d notice for default changes --- getting-started/devices-configuration.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/getting-started/devices-configuration.md b/getting-started/devices-configuration.md index 1a01d44..727187e 100644 --- a/getting-started/devices-configuration.md +++ b/getting-started/devices-configuration.md @@ -111,7 +111,7 @@ We will always aim to have the following iOS versions available as a baseline: It may be possible in some cases to provide support for a beta version however this will be on a case-by-case basis; please contact our Support team if you would like to request this. -The default configuration will always be the latest even-numbered base iPhone we support running the previous version of iOS, i.e. iPhone 16 running iOS 26. +The default configuration will always be the latest even-numbered base iPhone we support running the previous version of iOS, i.e. iPhone 16 running iOS 26. Before we change the default, we will always provide a minimum of 30 days notice. ### Android Support Policy @@ -126,4 +126,4 @@ We will always aim to have the following Android versions available as a baselin It may be possible in some cases to provide support for a beta version however this will be on a case-by-case basis; please contact our Support team if you would like to request this. -The default configuration will always be the latest base Pixel we support running the previous version of Android, i.e. Pixel 10 running Android 16/API 36. +The default configuration will always be the latest base Pixel we support running the previous version of Android, i.e. Pixel 10 running Android 16/API 36. Before we change the default, we will always provide a minimum of 30 days notice. From 06a9b83f377b04e79ede57711dc65d6876f2e064 Mon Sep 17 00:00:00 2001 From: finalerock44 <77282157+finalerock44@users.noreply.github.com> Date: Wed, 2 Sep 2026 12:51:42 +0100 Subject: [PATCH 3/5] Add Maestro policy & clarify deprecation warning --- configuration/maestro-versions.md | 12 ++++++++++++ getting-started/devices-configuration.md | 4 ++++ 2 files changed, 16 insertions(+) diff --git a/configuration/maestro-versions.md b/configuration/maestro-versions.md index e58c97a..21ecefe 100644 --- a/configuration/maestro-versions.md +++ b/configuration/maestro-versions.md @@ -38,3 +38,15 @@ dcd cloud ... --maestro-version 2.1.0 # Always use the most recent version of Maestro available dcd cloud ... --maestro-version latest ``` + +## Maestro Support Policy + +We will always aim to support the following versions of Maestro: + +- The latest version plus the previous three. + +We additionally will aim to continue supporting previous versions up to a maximum of ten. + +The default version will always be at maximum, four minor releases behind the latest. For example if the latest is 2.9.0, then the default is 2.5.0. We will always provide at least 30 days of notice before changing the default version. + +We will also always aim to provide at least 30 days of warning before removing support for previous Maestro versions. \ No newline at end of file diff --git a/getting-started/devices-configuration.md b/getting-started/devices-configuration.md index 727187e..8bb136f 100644 --- a/getting-started/devices-configuration.md +++ b/getting-started/devices-configuration.md @@ -113,6 +113,8 @@ It may be possible in some cases to provide support for a beta version however t The default configuration will always be the latest even-numbered base iPhone we support running the previous version of iOS, i.e. iPhone 16 running iOS 26. Before we change the default, we will always provide a minimum of 30 days notice. +Additionally when removing Device and OS support, we will always provide a minimum of 30 days notice. + ### Android Support Policy We will always aim to have the following devices available as a baseline: @@ -127,3 +129,5 @@ We will always aim to have the following Android versions available as a baselin It may be possible in some cases to provide support for a beta version however this will be on a case-by-case basis; please contact our Support team if you would like to request this. The default configuration will always be the latest base Pixel we support running the previous version of Android, i.e. Pixel 10 running Android 16/API 36. Before we change the default, we will always provide a minimum of 30 days notice. + +Additionally when removing Device and OS support, we will always provide a minimum of 30 days notice. From 8c672131d248dd29aaf04680981bc705456c42da Mon Sep 17 00:00:00 2001 From: finalerock44 <77282157+finalerock44@users.noreply.github.com> Date: Wed, 2 Sep 2026 15:05:16 +0100 Subject: [PATCH 4/5] Amend Maestro policy --- configuration/maestro-versions.md | 16 ++++++++++++---- 1 file changed, 12 insertions(+), 4 deletions(-) diff --git a/configuration/maestro-versions.md b/configuration/maestro-versions.md index 21ecefe..1784d0a 100644 --- a/configuration/maestro-versions.md +++ b/configuration/maestro-versions.md @@ -41,12 +41,20 @@ dcd cloud ... --maestro-version latest ## Maestro Support Policy -We will always aim to support the following versions of Maestro: +We will always aim to support the latest versions of Maestro and additionally continue to provide support for previous versions. Our policy for this is as follows: -- The latest version plus the previous three. +- We will always add support for new versions. +- Once a new minor version has been released (i.e. 2.x.0), we'll mark all previous patches of the previous minor (i.e. 2.6.x) bar the latest as deprecated. +- Once a minor version is five versions old, we'll mark it as deprecated. +- Once a version reaches below 1% usage, we'll mark it as deprecated. +- Deprecated versions are then removed after six weeks provided total usage is less than 0.5%. -We additionally will aim to continue supporting previous versions up to a maximum of ten. +% hint style="info" % +For example, Maestro 2.0.0 received 10 patch releases (2.0.1 -> 2.0.10) and we would provide support for all of them. Once Maestro 2.1.0 released, we would then remove support for 2.0.0 -> 2.0.9 and retain 2.0.10. -The default version will always be at maximum, four minor releases behind the latest. For example if the latest is 2.9.0, then the default is 2.5.0. We will always provide at least 30 days of notice before changing the default version. +Once Maestro 2.5.0 is released, we would then mark 2.0.10 as deprecated unless usage dropped below 1% before then. +% endhint % + +We may change the default version from time to time and we will always provide at least 30 days of notice before changing the default version. We will also always aim to provide at least 30 days of warning before removing support for previous Maestro versions. \ No newline at end of file From 9eeb0a054dfd35c5a668e84c5b9c36c11c2d645d Mon Sep 17 00:00:00 2001 From: finalerock44 <77282157+finalerock44@users.noreply.github.com> Date: Wed, 2 Sep 2026 15:09:20 +0100 Subject: [PATCH 5/5] Fix formatting --- configuration/maestro-versions.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/configuration/maestro-versions.md b/configuration/maestro-versions.md index 1784d0a..1bce7e9 100644 --- a/configuration/maestro-versions.md +++ b/configuration/maestro-versions.md @@ -49,11 +49,11 @@ We will always aim to support the latest versions of Maestro and additionally co - Once a version reaches below 1% usage, we'll mark it as deprecated. - Deprecated versions are then removed after six weeks provided total usage is less than 0.5%. -% hint style="info" % +{% hint style="info" %} For example, Maestro 2.0.0 received 10 patch releases (2.0.1 -> 2.0.10) and we would provide support for all of them. Once Maestro 2.1.0 released, we would then remove support for 2.0.0 -> 2.0.9 and retain 2.0.10. Once Maestro 2.5.0 is released, we would then mark 2.0.10 as deprecated unless usage dropped below 1% before then. -% endhint % +{% endhint %} We may change the default version from time to time and we will always provide at least 30 days of notice before changing the default version.