NewAdvertise is free on every plan
memberside

Add-on

The only thing that reaches a member who closed your app

Everything else in your app works for the people already inside it. Push is what brings back the ones who are not — a reply, a message, a mention, on their lock screen.

Sent with your own Apple and Firebase credentials
Start freeTry the live demo

Free while in beta. No credit card needed.

The problem

Your community is talking to an empty room

A community app is only a community while people open it. Nothing inside it can ask somebody to come back, because reaching them means reaching a phone that is in a pocket.

the silent majority

Most of your community is not looking

At any moment almost everyone who has your app installed does not have it open. Everything else in a community app — live chat, an instant feed, an unread badge — only reaches the people already inside it.

answered in minutes, or never

A message with nobody to hear it

Someone sends a direct message and the recipient finds it three days later, if at all. The conversation that would have happened does not, and neither member blames the app — they just use it less.

the quiet exit

Members do not leave, they drift

Almost nobody uninstalls a community app. They simply stop opening it, because nothing ever asked them to. By the time it is obvious in your numbers, the habit is months gone.

Realtime makes an open screen update instantly. It can do nothing at all for the member who closed the app yesterday — and that is the member you are losing.

What changes

A reason to open it again

Replies reach people who left

A reply, a mention, a friend request or a new message reaches the member on their lock screen, whether the app is closed, backgrounded, or has not been opened in a week.

Tapping opens the right screen

A notification about a message opens that conversation; one about a reply opens the notification centre. It does not dump somebody on a home screen to go looking.

Your keys stay yours

Notifications are sent with your own Apple key and your own Firebase project — held on your WordPress, never uploaded. Delete a key there and it is genuinely revoked, not queued for us to action.

What gets sent

Only what already happened on your site

Notifications come from your own community's activity. Nothing here lets us — or anyone else — notify your members.

  • Notifications

    Whatever your site already raises a bell for — replies, reactions, mentions, friend requests — reaches the member on their phone as well as in the app.

    Built in. Several people reacting to the same post arrive as one notification, not five.

  • BuddyPress notifications

    Mentions, replies, friend requests, group invitations and the rest can move from BuddyPress’s own notification list to your app — one event at a time, so nothing switches over in a single step.

    Members are told once, not twice, and anyone who opted out of a BuddyPress email stays opted out.

  • Direct messages

    A message notifies its recipient, titled with the sender’s name. Several messages in the same conversation replace one another rather than stacking up five banners.

    Needs Better Messages. Members can switch chat notifications off without losing the rest.

  • Nothing you did not ask for

    There is no broadcast tool, no marketing blast and no way for us to notify your members. Every notification comes from something that happened on your own site.

    Campaigns and segments are on the roadmap, and are not part of this.

Memberside → Notifications on a demo community: every notification the site raises, a Push switch on each, and its wording

Being straight with you

What we run, and what we do not

Delivery to a phone belongs to Apple and Google. It is built into the operating systems and nobody sells an alternative — so here is exactly where the line falls.

What we run

  • Which devices belong to which member, kept current as phones change.
  • Sending, retrying a failure, and giving up sensibly.
  • Removing a phone that was reset, so you stop paying to notify it.
  • Collapsing five messages from one conversation into one banner.
  • Your allowance, and a warning long before you reach it.

What Apple and Google run

  • The last step: waking a closed app on a locked phone.
  • Whether a notification is shown, and how it looks there.

We send to them directly with your credentials. On iOS that is Apple alone — your notifications do not pass through Google on their way to an iPhone.

On memberside.app

Your allowance, and how delivery is going

Notifications sent this month against your plan, the devices registered, and the ones that failed or were removed — on your account page, beside the domains you have connected.

The Push Notifications page on memberside.app: 11,782 of 500,000 notifications sent this month to 360 registered devices, with charts of notifications sent, delivery problems and registered devices over thirty days
Sample usage history on a demo community

How it works

Three steps, then nothing to think about

  1. Step 1

    Add your credentials

    An Apple push key for iOS, a Firebase service account for Android — or just one, if you ship one platform. They go into Memberside → API Keys on your own site.
  2. Step 2

    Authorize your domain

    Open Memberside → Services → Push Notifications and choose Authorize. You approve the domain here and land back in WordPress connected.
  3. Step 3

    Rebuild your app

    The next build registers each member’s device on launch. Nothing else to configure — no notification composer to learn, no audience to define.

Plans

Priced on how much you send

Included with Pro at 25,000 notifications a month and with Unlimited at 500,000. These tiers are for communities that outgrow what their plan includes — pooled across every domain you register, staging sites included.

Starter

A community of a few thousand, with an active notification bell.

$9 / month
  • 100,000 notifications a month
  • Up to 10 domains, staging included
  • Unlimited devices per member
  • Your own Apple and Firebase credentials
Most popular

Growth

A busy community where chat carries most of the volume.

$29 / month
  • 500,000 notifications a month
  • Up to 25 domains, staging included
  • Unlimited devices per member
  • Your own Apple and Firebase credentials

Scale

Several large communities, or one that notifies constantly.

$79 / month
  • 2,000,000 notifications a month
  • Up to 100 domains, staging included
  • Unlimited devices per member
  • Your own Apple and Firebase credentials

Prices in USD, billed monthly, cancel any time. Account holders can subscribe from the Push page in the dashboard, so create a free account and connect your site first.

Questions

Push FAQ

No — and nobody can. APNs and FCM are built into iOS and Android, and they are the only way to wake an app that is closed. What we run is everything above that: which devices belong to which member, sending to them, retrying a failure, removing a phone that was reset, and keeping count. That is the part you would otherwise pay a notification provider for.

On your own WordPress, and nowhere else. Your site signs a token with them that lasts about an hour, and only that short-lived token reaches our edge — so the worst case for a breach on our side is an hour, and removing a key on your site actually revokes it.

They stop being sent. This is worth being blunt about, because our other add-ons degrade gently and this one does not: a notification past your allowance is not delayed, it is not queued, and the member it was for never learns it existed. We warn you at 80% for exactly that reason.

Not yet. Today every notification comes from something that happened on your site — a reply, a message, a mention. A composer with audiences and scheduling is the obvious next thing and it is not built, so please do not buy this expecting it.

Yes, on both platforms — iOS has always asked, and Android has since version 13. A member who declines simply receives nothing; nothing else about your app changes, and they can turn it on later from their phone’s settings.

Yes, and it has to: a closed app has nothing to fetch with, so the title and body travel with the notification. That is the one place this differs from Realtime, which carries no content at all. Treat a notification as readable on a locked phone, because it is.

Give them a reason to come back

Create an account, connect your site, and reach the members who stopped opening your app — with your own credentials, from your own server.
Start freeTry the live demo