This topic provides an overview of Clover hardware lifecycle stages, including End-of-Sale (EOS) and End-of-App-Update (EOAU) policies.

Device lifecycle policy

Clover continuously introduces new hardware to leverage the latest advancements in security, processing power, and operating system capabilities. As new devices launch, older generations eventually reach the limit of their ability to support modern software and security standards.

Understanding the device lifecycle helps you plan your app development roadmap and ensures a seamless experience for merchants using Clover devices.

Lifecycle stages

Clover hardware moves through three primary lifecycle stages:

1. Launch (General Availability): The device is available for purchase in specific regions and is fully supported for all app updates and OS patches.
2. End-of-Sale (EOS): Clover no longer sells the device directly to merchants. However, the device remains supported. Developers can still release app updates to these devices, and Clover continues to provide critical security updates.
3. End-of-App-Update (EOAU): This is the final stage for third-party developers. When a device reaches EOAU:
   • No new installs: Merchants cannot discover or install new apps on these devices from the Clover App Market.
   • No app updates: Developers cannot push new APK versions to these devices. Existing apps continue to function but remain frozen at the last version installed before the EOAU date.
   • Limited maintenance: Clover may continue to provide limited OS security patches; however, feature development will cease.

Devices approaching End-of-App-Update (EOAU)

The following Gen 1 devices are approaching their EOAU date. After the mentioned date, you can no longer distribute app updates to these specific models.

Recommended action for developers

1. Inform your merchants: If your app relies on hardware-specific features of the devices listed, we recommend communicating with your merchants to encourage a hardware refresh before the EOAU date.
2. Check your device support: Verify which devices currently run your app to understand the impact on your merchants:
   1. Log in to the Developer Dashboard.
   2. Click App Settings > App Type.
   3. In the Clover Devices column, review the device names and generations your app currently supports.
3. Target the latest SDK: Ensure your build.gradle targets the most recent Clover Android SDK to support the latest devices, such as Station Duo 2 and Flex 3.
4. Manage backward compatibility: If you must support legacy devices until their EOAU date, use Android's minSdkVersion and build variants to serve appropriate APKs to different device generations.

Support

If you have questions about the lifecycle policy or need assistance with your app update, contact Clover Developer Support.

Related topics

• Clover devices
• Create new apps
• Build Clover Android apps
• Integrate with Clover Android SDK