Pinpoint End Of Support

[NicolasBrandi]

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.

[thisisabhash]

Hello,
Thank you for raising this issue, we are aware of these issues and have been actively discussing our way forward here. When we have more details about our exact replacements or solutions, we will return here with that information.

[mattcreaser]

To answer some of your specific questions @NicolasBrandi we know that the Pinpoint service will stop operating on Oct 30, so the answer for questions (2) and (3) are that this plugin has been deprecated and will stop functioning once the Pinpoint service becomes unavailable. Calls such as registerDevice or recordNotificationOpened will result in errors.

As mentioned above we are actively working on the answers to your other questions.

It might be helpful if you could share more details about how you're using the push capabilities today so that we could better understand your use case. How are you triggering the notification sending? What value are you seeing with the PinpointPushNotificationPlugin today? What functionality would you like to see in a potential a replacement plugin?

Really appreciate any insight you could provide, thanks!