Push Direct — $49, one-time

Push notifications without Firebase on iOS.

Apple already runs a push service. This plugin talks to it directly with a .p8 key — no Firebase SDK, no GoogleService-Info.plist, no Google dependency on the Apple side. Android uses FCM, because on Android there is nothing else.

The push plugins listed on the NativePHP marketplace today, free and paid, link Firebase's iOS SDK to do this.

Buy — $49One-time payment. Your Composer key arrives by email.

Recorded on an iPhone XR · APNs sandbox

Why this one

There are other push plugins for NativePHP Mobile, and some are free. The ones listed on the marketplace today — free and paid — link Firebase's iOS SDK. This one does not.

No Firebase project for iOS	Apple already runs a push service. The others make you stand up and maintain a Firebase project to reach it. Here you generate a `.p8` key in the account you already have, and that is the whole setup.
No Google SDK in an Apple app	FirebaseMessaging arrives with its own initialisation, its own disk footprint and its own entries in your privacy manifest — for a platform that needs none of it.
One less vendor	Your iOS dependency graph stays between you and Apple. Nothing to audit, nothing to explain in review, nothing to migrate when someone else's SDK changes.
The whole surface	Taps including cold start, unenrolment at logout, the badge, and the payload of a message while the app is open. Free options stop at the device token and a single delivery event.

If Firebase on iOS is fine by you, take a free plugin — it will work. This one exists for teams for whom it is not fine.

What it adds

The payload, not just the token. The core tells your app that a push arrived. This tells it what the push said — title, body and your own data — while the app is open.
Notification taps, including cold start. The user taps, your app opens on the right screen. Android carries the payload on the launch intent, iOS through the notification delegate. On Android, send data-only messages: a message with a notification block is drawn by Android itself, and the tap reaches your app only if it cold-starts it.
Unenrolment. The call you need at logout. Without it a signed-out device keeps receiving the previous user's notifications until the token rotates, which may never happen.
Badge control. Set and clear the number on the app icon.
Deep links. Configure which payload keys carry a URL; the tap event hands it back to you already resolved.
Same contract on both platforms. One set of events, one set of permission states.

How it looks

use Guppylab\Push\Events\NotificationTapped;
use Native\Mobile\Attributes\OnNative;

#[OnNative(NotificationTapped::class)]
public function onTap(string $payload = '{}', ?string $link = null): void
{
    $this->redirect($link ?? route('inbox'));
}

Requirements

NativePHP Mobile	3.x
iOS	15+. An APNs authentication key (`.p8`) from your Apple Developer account.
Android	API 21+. A Firebase project and its `google-services.json` — FCM is the push transport on Android devices with Google Play services. Send data-only messages if you rely on taps or deep links.
Your backend	Sends the notifications. The plugin is the device half; it does not send pushes for you.

What this is not.

It does not send push notifications. It receives them. Your server still talks to APNs and FCM, and you still own those credentials — which is the point: no third party sits between your app and Apple.

Licence and delivery

One-time payment of $49. No subscription.
One legal entity, unlimited applications, distributed in compiled form.
Installed with Composer from a private repository; credentials arrive with your purchase.
Full source — PHP, Swift, Kotlin.

Buy — $4914-day refund, no questions asked.

Questions first? suporte@guppylab.com.br