lapa.page
DISPATCH MANIFESTO & SYSTEM GUIDE

About lapa.page

A direct, algorithm-free wire between creators and their audience. Real-time web push alerts with zero intermediaries.

PROJECT PHILOSOPHY

Why lapa.page Exists

Modern publishing is fragmented by algorithmic feeds that decide who sees your work, email spam filters that hide your dispatches, and walled-garden platforms that hold your subscribers hostage.

lapa.page was created to restore simplicity: when a creator, developer, podcaster, or writer publishes an update, it arrives directly on their subscriber's screen in milliseconds via standard, native Web Push.

  • Zero algorithms: 100% of your subscribers receive your broadcast immediately.
  • Privacy-friendly: No tracking pixels, no cookies, no third-party ad networks. This site uses Umami for basic site analytics.
  • One-click subscriptions: No email forms to fill, no passwords to remember, no confirmation links.
  • Creator ownership: Each channel has an independent, cryptographically secure API key.
Crafted with care: This project was vibecoded with Google Antigravity, fusing human creative vision and real-time agentic pair programming into an agile, privacy-first software system.
THE CREATOR

Author & Community Support

Author avatar

Armands Leimanis

CREATOR OF LAPA.PAGE • INDIE DEVELOPER

Hello! I'm a front-end developer with more than 10 years of experience. I have worked for several digital agencies and built more than 100 projects. This is my first time using AI for building an application.

If you find lapa.page useful for broadcasting software updates, newsletters, podcasts, or blog posts to your community, supporting this project helps keep the infrastructure clean, independent, and privacy-friendly.

If you want to get in touch with me, drop an e-mail to armands@gmail.com

TROUBLESHOOTING GUIDE

Why Didn't I Receive a Notification? (Common Gotchas)

Web Push is robust and native to the browser, but operating systems and browser security policies frequently silence or queue alerts. Here are the most common reasons alerts don't appear on screen:

GOTCHA #1 • WINDOWS FOCUS ASSIST / MACOS DO NOT DISTURB
Operating System Focus Modes Silently Queue Alerts
When Windows 10/11 "Focus Assist" or "Do Not Disturb" is active (or when gaming/presenting), Windows suppresses notification popups completely. The alert was delivered successfully, but it went silently into your Windows Action Center (bottom-right tray icon Win + N). The same applies to macOS Focus profiles.
Solution: Open Windows Settings → System → Notifications → Turn off "Do not disturb", or click the bottom-right clock/tray icon to inspect your Notification Center tray.
GOTCHA #2 • OS-LEVEL BROWSER PERMISSION DISABLED
Your Operating System Has Blocked Browser Notifications Entirely
Even if you click "Allow" in Chrome, Edge, or Brave, if your operating system does not grant the browser application permission to spawn notifications, nothing will display on your monitor.
Solution: In Windows, go to Settings → System → Notifications, scroll down to Google Chrome or Microsoft Edge, and verify that the toggle is ON with "Show notification banners" checked. On macOS, check System Settings → Notifications → [Browser].
GOTCHA #3 • INCOGNITO / PRIVATE BROWSING MODES
Private Browsing Blocks Service Worker Push Registrations
By W3C specification, Service Workers and background push subscription registrations are disabled in Incognito / InPrivate windows to prevent cross-session fingerprinting.
Solution: Subscribe to your favorite channels using a normal, non-incognito browser window.
GOTCHA #4 • SITE PERMISSIONS BLOCKED PREVIOUSLY
Browser Site Permission Set to "Block"
If you accidentally clicked "Block" or dismissed the native browser prompt multiple times, the browser enters a silent deny mode and will never ask again.
Solution: Click the padlock or site settings icon directly to the left of lapa.page in your address bar, find Notifications, and change it from Block to Allow, then reload.
GOTCHA #5 • MOBILE BATTERY SAVER / BACKGROUND APP REFRESH
Battery Optimization Killing Background Service Workers
On Android and iOS, aggressive battery savers put background browser processes into deep sleep, delaying web push dispatches until the browser is reopened.
Solution: Exclude your primary browser from aggressive battery optimization in your device's Power/Battery settings.
GOTCHA #6 • SECURE CONTEXT REQUIREMENT (HTTPS)
Web Push Mandates a Secure Context
The Web Push and Service Worker APIs are strictly restricted to https:// domains (or http://localhost for local development). An insecure HTTP connection cannot register push managers.
Solution: Always access channels over https://lapa.page/.

Want to test your notification pipeline right now?

Head over to our live sandbox playground to dispatch real push alerts and verify system delivery on your current device.

Open Live Demo Playground ↗