DMBProgressiveWebAppBuilder 0.27.0

DMBProgressiveWebAppBuilder

DMBProgressiveWebAppBuilder provides a secure Progressive Web App foundation for PageBuilder-based ASP.NET Core websites.

The package registers:

• a global manifest link through DMBPageBuilder;
• a global service-worker registration script;
• dynamic endpoints for the web app manifest, registration script, service worker, and offline fallback page;
• conservative service-worker behavior that only caches explicitly configured same-origin static assets.
• optional browser push notification display and notification-click navigation in the generated service worker.

Security Model

The default service worker never caches authenticated HTML pages, API responses, non-GET requests, or cross-origin resources. Navigation requests use the network first and only fall back to the offline page when the network fails. The generated offline fallback is a self-contained HTML document with embedded CSS, brand colors, and a retry link to the configured start URL. Static assets are cached only when they are present in StaticAssetUrls. Static cache failures are best-effort: a missing or temporarily unavailable asset must not prevent service-worker activation. Push notification click targets are constrained to same-origin paths. After same-origin validation, notification clicks open the absolute target URL so browser implementations do not silently ignore relative window targets.

Basic Usage

DMBProgressiveWebAppBuilderConfiguration.LoadCommonConfig(builder);
DMBProgressiveWebAppBuilderConfiguration.Config.Options.AppName = "My App";
DMBProgressiveWebAppBuilderConfiguration.Config.Options.ShortName = "My App";

WebApplication app = builder.Build();
DMBProgressiveWebAppBuilderConfiguration.UseApp(app);

Push Notifications

DMBProgressiveWebAppBuilderOptions.PushNotificationsEnabled enables generic service-worker handling for browser push events. The generated service worker can display a notification payload and open or focus a same-origin target path when the notification is clicked.

This package does not create browser push subscriptions and does not send Web Push messages from the server. Feature modules must own subscription endpoints, VAPID key configuration, and server delivery.