I'm building a web app and need browser push notifications plus mobile support

If you want browser push notifications + mobile support, the usual path depends on what kind of “mobile support” you need:

Option 1: Web app + Push Notifications

Use the Web Push API with a service worker.

Works for:

• Chrome, Edge, Firefox, Safari (with some platform differences)
• Desktop browsers
• Mobile browsers to varying degrees

You’ll need:

• HTTPS
• Service worker
• User permission
• Push subscription from the browser
• A backend to send pushes (commonly with VAPID keys)

Good if:

• You want to keep it as a web app
• You mainly need notifications in supported browsers

Option 2: PWA

If by mobile support you mean “installable on phones,” make it a Progressive Web App.

Add:

• manifest.json
• service worker
• responsive UI
• install prompt support

Pros:

• One codebase
• Can be installed on mobile/desktop
• Supports push on some platforms

Limitations:

• iOS support exists but has restrictions
• Background behavior is more limited than native apps

Option 3: Native mobile app wrapper

If you need reliable push notifications on iOS/Android, consider:

• React Native
• Flutter
• Ionic + Capacitor
• A thin native shell around your web app

This gives you:

• Native push notifications via APNs/FCM
• Better mobile integration
• Access to device features

Good if:

• Notifications are core to the product
• You need strong iOS support
• You expect offline/background behavior

Practical recommendation

• If you want the simplest path: build a PWA with web push
• If you need dependable mobile push across iOS/Android: use a native app or hybrid wrapper
• If you want both web and mobile from one codebase: PWA first, then add a mobile wrapper if needed

Typical stack

• Frontend: React / Vue / Svelte / plain JS
• Push on web: Service Worker + Web Push API
• Backend: Node.js / Python / Go
• Mobile push: FCM for Android, APNs for iOS (often via Firebase or wrapper framework)

Important note

Browser push notifications are not the same as SMS or email:

• users must opt in
• browser/platform support varies
• delivery is not guaranteed instantly

If you want, I can help you with:

1. a recommended architecture,
2. a step-by-step implementation, or
3. a stack comparison for web + mobile push.