Beeprd Notification Roadmap: V1, V2, and V3

Beeprd Notification Roadmap: V1, V2, and V3

Beeprd is designed around signal quality and cost-controlled delivery.

V1: in-app pings plus installed-app Web Push

V1 delivers every matching subscriber signal into Beeprd's in-app Notifications.

Users who install Beeprd as a mobile web/PWA app and grant permission can also receive Web Push phone alerts. V1 phone alerts identify the sender where available, may use the sender profile photo as the notification icon, and keep the Beeprd logo as the badge/fallback.

V1 does not send every signal through Resend email.

V2: broader push infrastructure

V2 expands phone notification infrastructure beyond the first Web Push layer.

Planned V2 areas include:

• stronger push-token lifecycle management
• APNs for iOS app users when the native app scope requires it
• Android push when Android scope requires it
• deeper opt-in controls
• quiet hours
• throttling
• category-aware priority rules

V3: Enterprise delivery

V3 is for Enterprise customers.

Enterprise can support advanced/high-volume delivery where Beeprd supplies the technology and the customer pays for usage.

Enterprise email delivery may include:

• usage-priced email sending
• dedicated sender/domain strategy
• approval workflows
• compliance logs
• delivery reporting
• contract-specific limits

Why email is not default for V1

If one user has 1 million subscribers, one email to all subscribers is 1 million emails.

That can create major provider cost and deliverability risk.

Beeprd protects margins and subscriber trust by making in-app notifications and push the early realtime layers, while email stays digest-first and enterprise-priced at scale.