Publish addon
Developer center

Build and publish UZWay addons

UZWay addons are installable browser tools. Build a focused experience, describe it clearly, request only the capabilities it needs, test it in UZWay Browser, then publish it for users.

What an addon must provide

Every addon needs a clear identity, a user-facing entry point, declared capabilities, a version, and publisher information. Users should understand what the addon does before installing it.

  • Name: short, recognizable, and not misleading.
  • Summary: one or two sentences explaining the practical user benefit.
  • Category: the closest marketplace category for discovery.
  • Version: a visible release number users and support can reference.
  • Capabilities: storage, file access, clipboard, network, or other browser features the addon uses.
  • Install package: a working `.uzwaddon` file that opens in UZWay Browser.

Metadata example

Item Example Why it matters
Addon ID mini-budget Stable identifier for installs, updates, favorites, and support.
Name Mini Budget The title users see in listings and search.
Summary Track a small daily budget locally. Explains value quickly.
Category Finance Places the addon in the right browsing page.
Version 1.0.0 Helps users confirm which release they have.
Capabilities Local storage Tells users what the addon needs to function.
Publisher UZWay Team Shows who maintains the addon.

Development workflow

  1. Choose a narrow use case: calculator, converter, planner, signing helper, clock, dashboard, or another focused tool.
  2. Design the primary screen first: inputs, results, empty states, error states, and save/export behavior.
  3. Implement the addon package and include all assets required at runtime.
  4. Declare only the capabilities the addon actually uses.
  5. Test layout, keyboard input, local storage, file input, and empty states in UZWay Browser.
  6. Package the addon as `.uzwaddon` and test installation in UZWay Browser.
  7. Publish the package with name, summary, version, category, screenshots, and support notes.

Permission guidance

  • Use `localStorage` only for user data that can safely stay in the browser.
  • Use `fileInput` only when the user explicitly selects local files.
  • Do not request broad permissions for features that are not present.
  • Explain sensitive behavior in the addon summary or support notes.
  • Keep private data local unless the addon clearly says it connects to an external service.

Publishing requirements

  • The package must install and open in UZWay Browser.
  • The name and summary must describe the actual addon behavior.
  • Screenshots should show the real interface, not placeholder art.
  • The version must change when behavior or package contents change.
  • The support path must give users a way to report install or runtime problems.