G2

Yashashvi R.

Technical Solutions Engineer

Mid-Market (51-1000 emp.)

10/29/2026

"Server-Side Push Credentials Make Fixes Instant—No App Rebuilds Needed"

5/5

What do you like best about SuprSend?

What I like best is that push credentials are stored on the server, not in the app. When an app's Firebase or APNs credential is wrong, we replace it on the SuprSend side and notifications start arriving within minutes. There's no new build and no new App Store or Play review, which saves days on mobile. I can also see which Firebase project a stored credential belongs to, so I can find mismatches fast. And when a notification is shown wrong, one template fix on the SuprSend side reaches every app at once. Review collected by and hosted on G2.com.

What do you dislike about SuprSend?

Most of what I'd change is about failures that don't announce themselves. The notification template HTML-escaped push text, so "&" showed up as "&" on the device. Push titles and bodies are plain text, so escaping should be off by default for APNs and FCM. A Firebase credential that points at a project that has been shut down also fails quietly, so it looks like a bug in the app. A health check that flags it would save hours. And when two backends send to the same users from different workspaces, tokens registered in one can't be seen from the other. A hint like "this user exists in another workspace" would make that obvious right away. Review collected by and hosted on G2.com.

What problems is SuprSend solving and how is that benefiting you?

SuprSend handles push delivery to iOS and Android, so the people building apps on Emergent never have to write Apple or Firebase sending code or store push credentials in their app. Credentials are kept on the server and each app has its own workspace, so one app's users, tokens and keys never mix with another's. For me in L3 mobile support, the biggest benefit is speed. When push breaks because of a wrong or outdated credential, I fix it on the SuprSend side and delivery comes back within minutes, with no rebuild and no new store review. Because I can see each app's stored credentials and registered devices, I can tell whether the problem is in the app, the credential or delivery itself. That turns a long back-and-forth with the customer into one clear answer. Review collected by and hosted on G2.com.