Fission 0.9.0: native packaging, accessibility, and desktop polish

Fission 0.9.0 improves packaging, signing, desktop behaviour, accessibility, and repeatable UI tests—the work that is easy to postpone and painful to handle…
2026-07-19
By Fission Team
Releases
Fission 0.9.0 improves packaging, signing, desktop behaviour, accessibility, and repeatable UI tests—the work that is easy to postpone and painful to handle differently on each platform.
Package builds now take native inputs from the project manifest. Desktop interactions preserve more of the user's context, and the docs explain how to ship and test the result.

Native packaging is more explicit

You can now describe package variants, native-module Cargo products, desktop assets, platform scripts, and release-signing overlays in fission.toml. That gives the project one place to describe the native pieces around its shared Fission core.
This release improves the package path for:
•
Android and iOS generated targets with native modules;
•
macOS app bundles, signing inputs, provisioning profiles, entitlements, and notarization;
•
Windows native module builds and package resources;
•
Linux native Cargo products and custom run installers;
•
desktop project assets included in package artifacts.
Supporting more targets is only part of it. The package tool now reads native Cargo products from Cargo metadata and resolves project-relative paths before it runs scripts. A generated package script no longer needs to depend on an absolute path from one developer's machine.

macOS release signing is a first-class path

macOS packaging now has an explicit release-signing overlay. Applications can configure the app identity, provisioning profile, entitlements, notarization credentials, package identity, and whether a native product should produce package artifacts.
Your app still owns its signing setup. Fission does not invent credentials or put private signing material in fission.toml. Keep secrets in the local environment, a CI secret store, a keychain, or the provider that owns them; use the manifest to describe what the package needs.

Desktop interactions are tighter

This release also tightens a set of desktop behaviours that are easy to notice once an app is in regular use:
•
tray applications can choose whether they appear in the Dock, taskbar, or app switcher;
•
tray-style apps are hidden from app switchers by default where the platform supports that behavior;
•
modal and barrier lifecycles capture and restore focus;
•
native notification response callbacks are delivered back into the app;
•
tooltip and flyout surfaces preserve intrinsic sizing instead of filling the window;
•
reducer-bound effect callbacks are retained long enough for delayed shell callbacks.
There is one default worth checking: tray apps are now hidden from app switchers where the platform supports it. If your app should stay visible in the Dock, taskbar, or app switcher after it moves to the tray, set that policy explicitly.

Drag, drop, selectable text, and context menus

Drag and drop now has a complete runtime path. Fission tracks the drag session, external file drops, dropzone state, previews, accepted effects, copy or move behaviour, and cancellation. The widget gallery shows the interactions in use, so you don't have to infer them from pointer events.
Text and RichText can now opt into selection, and context menus are widgets rather than shell-specific extras. The default stays simple; when selection is enabled, apps can expose familiar actions such as copy and select all. Context menus accept child widgets, so their labels can use the app's normal i18n setup and the menu can contain more than a fixed list of commands.

More reliable state and input behavior

This release fixes several issues that only show up once an app has multiple routed screens, controlled inputs, and long-running effects:
•
stale scroll state is pruned when widgets unmount;
•
route and tab content state is isolated so slider and scroll positions do not leak between pages;
•
slider thumbs align with their tracks and click positions map to the expected values;
•
controlled text inputs reconcile pending edits against transformed model values;
•
oversized ScrollIntoView targets stay anchored at the leading edge for nearest alignment.
Each fix is small on its own. Together they stop one screen's retained state from unexpectedly showing up on another, and make input and scrolling behave consistently after navigation.

Accessibility docs are now part of the public contract

Fission already exposes semantics through the runtime and native shells. What was missing was clear guidance on what app developers should set and what they can test.
0.9.0 adds:
•
a Learn page for accessible Fission app structure;
•
a Cookbook page for adding semantic metadata to widgets and regions;
•
a Reference page with platform support levels, expected assistive technology compatibility, and known gaps.
The guidance is practical: give interactive widgets stable semantic identifiers, choose labels and roles that describe what they do, report disabled, read-only, and checked states accurately, and test both the LiveTest semantic tree and the platform's assistive technology.

Documentation catches up with the CLI

The build and package docs now match the CLI. Platform pages cover generated target files, package resources, native modules, signing inputs, and real fission.toml values instead of leaving you with disconnected snippets.
The testing docs cover unit tests, integration tests, and LiveTest—including selector-driven /cmd requests. The command API reference shows how to target semantic identifiers, widget IDs, roles, labels, and scoped selectors without hard-coded coordinates.
Maintainers also get a release checklist that follows the whole process: agree the scope, update versions and release notes, run the checks, publish crates in order, tag the release, verify the website, and smoke-test the result.

Migration notes

Update Fission dependencies to 0.9.0:
fission = { version = "0.9.0", default-features = false, features = ["desktop"] }
If your app uses tray behavior and should remain visible in the Dock, taskbar, or app switcher, configure the tray app switcher policy explicitly. The default now follows tray-app conventions and hides the app from switchers where the platform supports it.
If your app has custom package scripts or native package resources, move those declarations into fission.toml where possible. The CLI can now resolve native package variants and products from the manifest and Cargo metadata, which is more portable across local machines and CI.
If you rely on generated app-agent guidance, regenerate or copy the updated AGENTS.md content so agents get the current rules for responsive UI, design tokens, i18n, semantics, shared multi-platform cores, and LiveTest screenshot QA.