Push Notifications Without Apple or Google: How Maritime PWAs Solve the App Store Problem

The App Store Dependency Problem

Every iOS app that sends push notifications must route them through Apple's APNs infrastructure. Every Android notification goes through Google's FCM. This is not optional — it's how mobile operating systems work.

For most applications, this is a reasonable trade-off. For maritime operations, where internet connectivity is unreliable or absent, it's a fundamental architectural problem.

APNs and FCM are cloud services. If your vessel has no internet connection, no push notification reaches crew devices — regardless of how urgently the alarm needs to be delivered.

Why This Matters for Safety-Critical Communication

A fire alarm, a medical incident, a man-overboard alert: these notifications must reach crew devices even when the ship is beyond satellite coverage. Routing them through California or Ireland is not an option.

This is the case for every notification-dependent application currently distributed through the App Store or Google Play Store. The push notification stack is inherently cloud-dependent, which means it's inherently unsuitable for offshore maritime operation.

What Progressive Web Apps Change

Progressive Web Apps (PWAs) are web applications that install to the home screen, work offline, and — critically — can receive push notifications without involving Apple or Google infrastructure.

This is possible through Web Push, a W3C standard that allows push notifications to be delivered through a server you control. The notification path is:

Your on-vessel server detects an incident or alarm

It sends a push notification to the Web Push endpoint stored on crew devices

The Service Worker on the device receives the notification — even with the browser closed

The notification appears on screen

There is no APNs. No FCM. No internet required. The entire path operates within the vessel's local network.

The Technical Components

To implement autonomous push notifications on a maritime PWA:

Service Worker — A JavaScript file that runs in the background of the browser. It intercepts network requests and handles push events. This is what makes the notification appear even when the browser isn't open.

Web Push Protocol — The standard that defines how push messages are encrypted and delivered to browsers. Uses VAPID keys for authentication between the server and client.

Push Subscription — When a crew member opens the PWA, their browser creates a push subscription — essentially an endpoint address for their specific device. This is stored on the vessel server, not in any cloud service.

On-Vessel Push Server — A small service running on the vessel's local infrastructure that holds push subscriptions and sends notifications. No external dependency.

iOS: The Last Frontier

Until iOS 16.4, iPhones couldn't receive Web Push notifications at all. Apple's implementation remains more restrictive than Chrome/Android — notably, the PWA must be added to the Home Screen before Web Push works.

For maritime operations, this means onboarding includes a brief setup step ("open the app, add to home screen"). Once done, push notifications work autonomously on iOS, Android, and any other device.

What This Enables

• Medical alerts delivered to duty crew within 1 second of incident creation
• Engine room alarms routed to on-watch engineering crew
• Muster notifications reaching every connected device on vessel simultaneously
• Zero dependency on internet connectivity, satellite, or cloud services

The Operational Implication

For maritime operators evaluating communication platforms, the right question is not "does it have push notifications" — every platform does. The right question is: "Does the push notification infrastructure work without internet?"

If the answer is no, the platform has a dependency that makes it unsuitable for deep-sea operations.

A PWA-based platform with on-vessel Web Push infrastructure is the only architecture that answers yes.