Pinpoint End Of Support

Hi team,

I’m looking for guidance on the future of push notifications in Amplify Android now that Amazon Pinpoint is being
deprecated.

My app currently uses Amplify only for push notifications. I'm not using Pinpoint campaigns, journeys,
analytics, or other engagement features in the app. The main concern is continued support for device registration and push delivery compatibility.

Questions:

1. What is the Amplify Android plan for push notifications after October 30, 2026?
2. If an app still includes AWSPinpointPushNotificationsPlugin only for push notifications, will that remain supported for backward compatibility, or should we expect runtime failures?
3. If an app still calls Amplify.Notifications.Push.registerDevice(), what will happen after Pinpoint end of support?
- no-op
- failure callback / exception
- runtime crash
- still works through AWS End User Messaging Push
4. Is there a planned replacement for the Pinpoint push plugin in Amplify Android?
5. If the recommended path is AWS End User Messaging Push, what is the expected migration path for Android apps using Amplify today?
6. Are there plans to publish official migration guidance specifically for Amplify Android push users?

From an app developer perspective, the most important thing to understand is whether continuing to build with the Pinpoint push plugin or calling registerDevice() will break apps after Pinpoint end of support, and what the supported long-term path is for continuing to use push notifications with Amplify Android.

Thanks.

Start by reviewing the behavior and support status of AWSPinpointPushNotificationsPlugin and Amplify.Notifications.Push.registerDevice() in Amplify Android, then compare them with AWS End User Messaging Push. The issue provides no file or test to run; done would require confirmed answers about post-2026 behavior, a supported replacement or migration path, and official guidance for Android users.

Written by the indexing model from the issue text.