Fission 0.2.0 expands the project beyond desktop. It adds charting, Web and mobile scaffolding, typed host capabilities, richer text and input behaviour, documentation with local search, and the first release-management commands.
Together, these additions bring more of the work to build and ship an app into Fission itself.
Charting started with fission-charts and grew into a native gallery. It includes datasets, layout algorithms, interaction options, 3D scenes, and a broad set of chart types. The important part is that charts can be real Fission widgets in a data-heavy app, not screenshots or controls bolted on from another system.
Web and mobile moved forward too. Fission gained project scaffolding and smoke-test paths for Web, the iOS simulator, Android, and the shared winit shells. We also improved mobile input, target-compatible dependencies, app icons, software rendering fallbacks, viewport handling, and platform guidance. The Web shell became runnable, while mobile smoke examples gave us concrete checks across targets.
Host work became more explicit. The release added asynchronous jobs, services, runtime resources, and typed capabilities in place of ad hoc system effects. A capability gives app code a portable way to ask the host to do work—such as access a file, device, or platform service—while reducers remain explicit and testable.
Text and input also received a lot of attention. Rich text gained locale, selection, inline-widget, hover, and span-action support. Text input gained paragraph-aware rendering, input-method editor synchronisation, tap-outside actions, decoration APIs, and a clearer event lifecycle. We backed that work with tests and example updates; text editing is a good way to find gaps in a UI runtime quickly.
Developer experience was another large part of 0.2.0. We introduced the documentation site and expanded it with guided learning, reference material, widget pages, platform guidance, and local search. The structure began to follow the app lifecycle: setup, learn, build, test, and publish. The docs still had a long way to go, but this release made them part of the product rather than something to add later.
The CLI and release workflow started to take shape as well. This release added fission init, target scaffolding, diagnostic checks, packaging support, credential handling, store metadata flows, and release recipes. The aim is to help you ship an app, not only open a window.
Fission 0.2.0 is where the project began to look like a cross-platform app framework, not just a desktop UI foundation. Charts, shells, capabilities, documentation, examples, and release tools were starting to meet around the same application model.
What this means for developers
For a data-heavy app, the important boundary is now clearer: a job or service
loads the data, a reducer records its result, and a chart renders the available
snapshot. For Web or mobile, the generated host supplies the platform setup,
not another copy of those product rules. Validate that host on its own terms;
shared runtime tests do not prove emulator launch or device permissions.