BrowserUX Starter: Not just a template. A standards-first web foundation.

A standards-first front-end foundation.

BrowserUX Starter is not trying to replace Next, Nuxt, Astro, Remix, or any full-stack application framework. It answers a different need: static sites, PWAs, and client-side apps where you keep explicit control over HTML, CSS, browser APIs, service workers, cache strategies, and deployment.

• 📱

  PWA by default

  Web App Manifest, service worker registration, Cache API strategies, install flow, and offline fallback are part of the foundation.

• 🧩

  Native Web Standards

  Theme switcher, share button, PWA install/update UI, and navigation feedback are built with Custom Elements, browser APIs, and progressive enhancement.

• ⚡

  Native CSS & browser APIs

  CSS variables, media queries, native user interface patterns, semantic HTML, Web Share API, View Transitions API, and localStorage stay visible and editable.

• 🔧

  Framework optional

  Use raw or vite-vanilla without React or Vue, or choose React and Vue as optional UI layers on top of the same standards-first BrowserUX base.

What the foundation gives you.

• 📱

  PWA & Offline

  • Web App Manifest, app icons, theme colors, and standalone display mode.
  • Service worker registration and offline fallback included in every template.
  • Direct Cache API learning path in raw, Workbox injectManifest in Vite templates.
  • Static asset precaching through generated sw-assets.js entries.
  • Install and update UI through the BrowserUX PWA Web Component.
• ⚡

  Build & Performance

  • Vite-powered builds for the Vanilla, React, and Vue templates.
  • Image optimization with AVIF/WebP generation and manifest output.
  • SEO file generation for sitemap and robots files.
  • Config-driven app metadata shared across manifest, SEO, and install surfaces.
  • Typed configuration where TypeScript is enabled.
• 🧩

  Web Standards

  • Web Components: Custom Elements, Shadow DOM, slots, and HTML attributes.
  • Native CSS: variables, media queries, native elements, and user preferences.
  • Native user interface patterns built from platform behavior first.
  • Browser APIs such as Web Share, beforeinstallprompt, View Transitions, and localStorage.
  • Semantic HTML and native interactions before proprietary abstractions.
• 🔧

  Developer Experience

  • One CLI command to choose a template, language, package manager, and install flow.
  • Raw, Vite Vanilla, Vite React, and Vite Vue templates sharing the same foundation.
  • JavaScript and TypeScript variants where they make sense.
  • Template tests that protect generated projects and expected dependencies.
  • Optional React and Vue layers for teams that want framework ergonomics without hiding the browser.