Pulsar
StoreSign in
Developers

Build extensions for Pulsar

Pulsar extensions are normal WebExtensions with one extra manifest key. They can talk to Pulsar, show their controls in Pulsar’s own drawer, and reach people through the Pulsar Store.

What an extension is in Pulsar

An extension is a Manifest V3 (or V2) WebExtension, like one for desktop Firefox: a manifest, a background script, content scripts and pages. Pulsar runs on GeckoView, Firefox’s engine for Android, so the browser.* APIs you know work.

Add "pulsar": {"api": 1} to the manifest and your extension can talk to Pulsar through the Pulsar API: draw its drawer and settings, show a status line, run background jobs and call Pulsar’s engines.

  • People tap the puzzle button (or your pinned tile) and your drawer slides up from the bottom of the screen.
  • Your settings live in Settings › Extensions, next to Pulsar’s own.
  • Pulsar decides where you may run: people can switch you off on a site, and you must stop there.
  • Store extensions are checked by a person and signed twice: by Mozilla and with the Pulsar seal.

Two ways to build your screens

You can mix both in one extension. Most extensions use native specs for the drawer and keep HTML for bigger pages.

Native specs (recommended)Send a small JSON description; Pulsar draws the drawer and settings page with its own switches, chips, sliders and buttons. It looks native in light and dark, opens instantly and needs no HTML.Your own HTML, with the UI kitKeep a default_popup, an options page or full pages. Pulsar shows popups and options in the same drawer. Use pulsar-ui.css and pulsar-ui.js so they match Pulsar.

Quick start in 5 steps

  1. Download the starter

    A complete extension (Easy Read) with a native drawer, a settings page, a content script and two pages built with the UI kit. Download pulsar-starter.zip.

  2. Make it yours

    Change the name, the id (you@yourdomain) and the tint in manifest.json. Keep pulsar.js first in background.scripts.

  3. Try the pages on your computer

    Serve the folder and open options.html in a phone-sized window. The pages use sample data outside Pulsar.

  4. Test on your phone

    Sign a test copy on Mozilla’s unlisted channel, turn on Developer mode in Pulsar and load it from a link, a QR code or a file. See Quick start.

  5. Send it to the store

    Zip the folder and submit it at pulsarbrowser.com/account/developer. We sign it and a person reviews it, usually in 1–2 days.

Downloads

Everything is free to use in your extensions. Copy the files into your extension: pages inside an extension can’t load files from the web.

Starter extensionpulsar-starter.zip · Easy Read, ready to changepulsar-ui.cssTokens and every componentpulsar-ui.jsToasts, sheets, menus, dialogs, wiringpulsar-icons.svgThe icon set as an SVG spritepulsar.jsThe Pulsar API client

All the docs

Quick startBuild, load, test, package and submit the starter.ManifestThe pulsar key: API version, permissions, tint, icon, engines.Pulsar APIEvery method and event, with parameters, results and examples.Native UIEvery spec item, how Pulsar draws it, the rules and the icons.UI kitA live gallery of every component, light and dark, with HTML to copy.Design guidelinesSpacing, type, motion, dark mode, touch targets and words.Background workJobs, schedules and the limits that keep phones fast.EnginesCall Pulsar’s Player, Files and Converter from your extension.Lite extensionsPage scripts and styles in a zip. Nothing to sign.Store and updatesThe seal, updates, and an install button on your own site.PublishingThe review checklist and what gets rejected.