guppylab

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.

Push without Firebase — $49One-time payment. Your Composer key arrives by email.
Recorded on an iPhone XR · pushes sent by the Guppylab server

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.

KeepMail app icon
In production: KeepMail A business email app on the App Store. New-mail notifications go straight from its Laravel server to Apple, and a tap opens the message, even when the app was closed.
See it on the App Store →

Between your app and Apple: nothing

What it adds

How it works

Install

composer require guppylab/push-direct. The key from your purchase email unlocks the private repository.

Enrol the device

PushNotifications::enroll() asks for permission and hands you the token: raw APNs on iPhone, FCM on Android, plus the APNs environment to store next to it.

Send and handle the tap

Your Laravel backend posts to APNs with your .p8 key, or to FCM. NotificationTapped brings the link back, even when the tap started the app.

Where it fits

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 Mobile3.x and 4.x
iOS15+. An APNs authentication key (.p8) from your Apple Developer account. Pictures need one more App ID and provisioning profile, for the notification extension; php artisan push:export-ios exports the build with both.
AndroidAPI 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 backendSends 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

Push without Firebase — $4914-day refund, no questions asked.

Questions first? suporte@guppylab.com.br