Beeps Safe V2S is designed as a private numeric paging and controlled-contact system. A user can receive Beeps through
a private receiver PIN instead of exposing a personal phone number. Senders can submit short Beeps to that receiver PIN
through the public dialer or authenticated sender/receiver terminal. Receiver retrieval is controlled through authenticated
polling, backend token validation, server-side queue behavior, and entitlement rules.
The Android application is a hybrid release: it is an installable Android app shell, but the active Beeps Safe interface
remains hosted. The app loads the Firebase-hosted Beeps Safe V2S interface and uses the backend for message enqueue,
receiver token validation, polling, delivery, account identity, credit enforcement, payment fulfillment, and notification signaling.
Technical Release Information
Release Identity
| Release name | Beeps Safe V2S 26.3 Basemaster WebWrapper Signed Release |
|---|
| Public product version | Version 2 / V2S / 26.3 |
|---|
| Android package ID | com.beep.beepsbyelectrolips |
|---|
| Owner | Electrolips LLC |
|---|
| Hosted entry | https://beeps-v2s.web.app |
|---|
| Backend / hosting | Firebase Hosting + Firebase Functions Gen 2 / Node.js / Express |
|---|
| Messaging | Firebase Cloud Messaging |
|---|
| Queue / entitlement state | Redis-backed server-side state |
|---|
| Payments | Stripe and PayPal integrations |
|---|
Release Files and Integrity
| APK | Beeps_Safe_V2S_26.3_BASEMASTER_WEBWRAPPER_NO_ASSETS_SIGNED.apk |
|---|
| APK size | 6.8M |
|---|
| APK SHA-256 | f11b501c66fe563f9405acd2fb6c8657eaf155c25d6fcab5da75b4b484ff1b67 |
|---|
| AAB | Beeps_Safe_V2S_26.3_BASEMASTER_WEBWRAPPER_NO_ASSETS_SIGNED.aab |
|---|
| AAB size | 6.1M |
|---|
| AAB SHA-256 | 21816322fccc90a4210db74d36e8fb61bf683fc256d0e1a6f6c1e62079868512 |
|---|
| Checksum generation time | 2026-05-06 19:14:34 UTC |
|---|
Signing Information
APK signing certificate identity:
CN=john pate, OU=Electrolips Pager Link Systems, O=Beeps-Safev2s, L="Berkeley ", ST=California, C=US.
Signer certificate SHA-256 digest:
ba7af85e0c5a240fa88e8163c7769ae56506e2bac4b3723746a5fca69e9d7753
The AAB signing verification reported the bundle as jar verified, while also noting a certificate-chain warning caused by
the self-signed/local signing certificate chain and a no-timestamp warning. That warning is separate from the file checksum
and does not change the APK/AAB SHA-256 values listed above.
Hosted WebWrapper Packaging
This Android release loads the hosted Beeps Safe V2S interface instead of distributing the active HTML, JavaScript,
CSS, or MAP web source files inside the Android assets folder. The app is therefore treated as a hosted web-wrapper package:
the user installs the Android app, opens Beeps Safe, and the wrapper loads the live Beeps Safe web interface from Firebase Hosting.
Source asset scan result: PASS. The checked Android source assets folder contained zero files.
The hosted Firebase deployment remains the live source for menu behavior, receiver access, sender/receiver terminal behavior,
purchase routes, success/cancel pages, legal/support/community paths, and future web interface updates.
Application Architecture
Beeps Safe V2S uses a hybrid architecture consisting of an Android WebView wrapper, Firebase-hosted web application,
Firebase Authentication identity layer, Firebase Functions Gen 2 backend, Express API routes, Redis-backed queue and
entitlement state, Firebase Cloud Messaging, Android notification support, Android audio/Bluetooth permissions,
Stripe checkout and webhook processing, PayPal order and webhook processing, public dialer access, receiver interface,
and sender/receiver terminal behavior.
Core Communication Model
Beeps Safe V2S uses a queue-backed paging model. Messages are submitted to the backend and associated with a receiver PIN.
Receiver interfaces retrieve messages through authenticated polling. The system is designed for short paging payloads,
controlled contact, callback screening, safety-oriented alerting, private field-service signaling, and public sender to
private receiver workflows.
The receiver identity model allows a user to share a Beeps receiver PIN instead of a personal phone number. A sender can
submit a Beep to that PIN without receiving the user's private phone number or direct personal contact information.
Backend Authority and Credit Rules
The backend is authoritative for receiver PIN assignment, receiver token issuance, queue insertion, delivery,
credit-balance enforcement, monthly-cap enforcement, payment fulfillment, webhook idempotency, Android push registration,
replay prevention, and rate limiting. Frontend clients may display balances, statuses, and message views, but they do
not decide whether credits exist and do not perform credit deduction.
Current public rule: one delivered Beep deducts one server-side credit unless an active monthly capped plan applies.
Empty polling does not deduct credits. Failed polling does not deduct credits. Enqueue/send does not deduct credits.
Replayed or duplicate enqueue requests do not deduct credits.
Receiver Polling and Notification Behavior
Receiver and terminal clients use receiver tokens for authenticated polling. Updated clients send the receiver token
through the Authorization header using Bearer-token transport. Polling validates the token and receiver PIN before delivery.
Android push notification support is used as a signal that a Beep is waiting; message content is retrieved inside the
app through authenticated polling instead of being fully exposed in the notification body.
Installation and Device Setup
Users install the APK directly on Android. If prompted, Android users must allow installation from outside the Play Store
for the browser or file manager used to open the APK. After installation, the user opens Beeps Safe, creates an account
or signs in, opens Receiver or Sender / Receiver Terminal, allows notifications, and keeps internet access enabled.
For best notification reliability, users should enable app notifications, allow lock-screen or pop-up notifications if desired,
allow background activity, avoid force-stopping the app, avoid deep sleep restrictions, and avoid restricting background data.
If notifications stop, reopening the Receiver can refresh receiver identity and push registration.
Supported and Future Interfaces
Current supported interface categories include hosted Android WebView operation, sign-in, menu navigation, receiver access,
sender/receiver terminal access, public dialer access, buy page access, success/cancel page behavior, and support/legal/community
links as configured in the hosted Beeps Safe V2S deployment.
Future platform categories can include browser extension packaging, iOS WKWebView packaging, Wear OS receiver behavior,
IoT accessory receivers, audio-only receiver devices, ring/wearable accessories, and other controlled-contact receiver devices.
BEEPS BROWSER ADD-ON
Technical Release Information
Beeps Safe V2S 26.3 — Chromium Family Browser Addon Release
Beeps Safe V2S 26.3 is the browser-addon deployment line of the Electrolips Beeps communications system. Designed for Chromium-family browsers, the release provides a lightweight hosted launcher environment for secure pager-style messaging and controlled-contact communications.
Unlike conventional social messaging applications, Beeps Safe V2S operates through a hosted receiver architecture using compact identities, hosted interface routing, and server-authoritative queue control. The browser addon integrates directly into the browser toolbar while launching the hosted Beeps interface through a popup communications window.
Supported browsers include:
• Google Chrome
• Chromium
• Brave Browser
• Microsoft Edge
• Opera
• Vivaldi
Lightweight Hosted Architecture
Version 26.3 introduces the new “no-assets” browser deployment model.
The browser packages no longer contain embedded HTML application interfaces or bundled frontend assets. Instead, the extension operates as a lightweight launcher shell that connects directly to the hosted Beeps Safe V2S environment.
This architecture provides several advantages:
• reduced package size
• centralized interface updates
• simplified deployment
• reduced client-side exposure
• synchronized hosted releases across platforms
The browser packages are intentionally minimal while the operational interface remains hosted remotely.
Technical Platform
The Beeps Safe V2S browser environment is built using:
• Chromium Manifest V3
• Firebase Hosting
• Firebase Functions Gen 2
• Redis-backed queue infrastructure
• hosted popup launcher architecture
• toolbar-integrated runtime deployment
• secure backend API routing
The addon launches the hosted Beeps interface directly from the production deployment environment.
Toolbar Runtime Integration
Once installed, the Beeps icon attaches directly to the browser toolbar. Activating the extension opens Beeps Safe V2S inside a compact popup communications window designed for fast-access operation and lightweight messaging workflows.
The interface architecture is designed around:
• compact receiver identities
• hosted sender/receiver systems
• public dialer interfaces
• live polling systems
• server-authoritative routing
Security and Backend Design
Critical operational logic remains backend-controlled.
The browser addon itself does not store messaging authority or entitlement control locally. Queue management, receiver authorization, routing logic, and delivery coordination remain hosted within the server infrastructure.
This hosted-authority model allows:
• centralized security updates
• controlled entitlement enforcement
• replay-prevention logic
• authenticated receiver access
• backend-managed routing
Package Characteristics
Approximate package size:
• ~376 KB per browser release
Each package includes:
• manifest configuration
• launcher runtime
• toolbar integration
• browser icons
• installation documentation
• hosted launcher control logic
The final release intentionally excludes:
• embedded interface pages
• local frontend application assets
• bundled hosted environments
Cross-Platform Availability
The Chromium-family deployment line complements the broader Beeps Safe V2S platform ecosystem, including:
• Android wrapper deployments
• hosted web deployments
• future wearable integrations
• future IoT notification interfaces
• future browser-store distribution channels
Release Summary
Beeps Safe V2S 26.3 represents a transition toward a cleaner hosted-browser architecture focused on lightweight deployment, centralized updates, and browser-integrated communications access.
The result is a compact Chromium-family extension that functions as a live launcher interface into the hosted Beeps environment while maintaining a minimal local footprint and a server-authoritative operational model.