Technology is always moving - inside Braze and outside it! And we do our best to keep up with it. Here, you’ll find the origins of Braze and it’s technology - how we supported people in the “before time” - before now, anyway…
You might have gotten here from searching a term for an integration or feature that no longer exists. This is our attempt to keep you informed on our progress and movement within the technology industry.
Support withdrawn: August 2019
If you are currently using Apptimize with Braze, you will not experience a disruption of service. You can still set Apptimize custom attributes to Braze user profiles. However, no formal escalation support with the partner will be provided.
Original In-App Messages
Replaced by: In-App Messaging
Support completely withdrawn: February 2019
Braze has improved the look and feel of In-App Messages to adhere to the latest UX and UI best practices and no longer supports original in-app messages.
Braze moved over to a new form of in-app messages with the following SDK releases:
Prior to these releases, Braze supported “original in-app messages.” Previously, support for original in-app messages was provided for any customer who ran an in-app campaign prior to the new release. All of the campaign stats were unaffected by the change, and those who had sent original in-app messages had the opportunity to send others via the “Create Campaign” button on the campaign screen.
Support to be completely withdrawn July 1, 2019.
The Braze SDK provided a feedback widget that could be added to your app to allow users to leave feedback using the submitFeedback method and pass it into either Desk.com or Zendesk and was managed on the dashboard.
Google Cloud Messaging (GCM)
Replaced by: Firebase Cloud Messaging (FCM)
Support to be completely withdrawn between July 2018 (Braze removal of support) and April 2019 (Google removal of support).
Google will be removing support for GCM as early as April 11, 2019. Braze will remove support for GCM from the Android SDKs in July 2018, which will be noted within our Android SDK changelogs. This means that existing GCM tokens will continue to work and you will be able to message your existing users. However, you will not be able to message new users.
Customers that have not already migrated to Firebase Cloud Messaging (FCM) may be affected by this change.
If you have not transitioned to FCM by April 11, 2019, all GCM push tokens registrations will fail. If your apps are currently supporting GCM, you’ll need to work with your development teams on transitioning from GCM to Firebase Cloud Messaging (FCM).
Replaced by: Android Studio
Support withdrawn: 2014-2015
Braze has deprecated support for the Eclipse IDE as Google is sunsetting support for the Eclipse Android Developer Tools Plugin. If you need assistance with your Eclipse integration prior to migration please email Support for assistance.
The Raw Event Stream (RES)
Replaced by: Currents
Support withdrawn: July 2018
The Raw Event Stream was the predecessor to Currents and was deprecated to make room for the future of Braze data.
Delay While Idle
Replaced by: n/a
Support withdrawn: November 2016
The Delay While Idle parameter was previously a part of the GCM push options. Google withdrew support for this option on November 15th 2016. Previously, when set to true, it indicated that the message should not be sent until the device becomes active.