Fission 0.3.0: async images, native capabilities, GPU-first web and server rendering

Fission 0.3.0 focused on the gaps that show up when an app has to do more than render a screen. It improved media loading, native capability providers,…
2026-05-29
By Fission Team
Releases
Fission 0.3.0 focused on the gaps that show up when an app has to do more than render a screen. It improved media loading, native capability providers, platform launch behaviour, GPU-first Web rendering, iOS safe areas, Static site and SSR workflows, Docker packaging, and security controls.
The common thread is making these paths usable in an app a person can actually use. A feature that works only in a demo is not finished.
Image handling moved beyond a source field on a widget. Typed image sources and renderer-managed loading now cover remote images, loading and error states, cache policy, intrinsic sizing, and refresh behaviour. The product browser example uses real remote data, which exposed layout issues a counter demo would never find.
Capabilities became more concrete too. Fission added native hosts and generated target metadata for capability families, then added the field-inspector example to exercise them on macOS, Web, iOS, and Android. Development app bundles on macOS mean capability prompts and native entitlements behave as they do in an app, rather than in a loose executable. The release also fixed Web passkeys, scheduled notifications, native macOS notifications, and iOS simulator dispatch linkage.
Web and iOS rendering improved as well. Web moved to a GPU-first path, keeping Canvas2D software rendering as a fallback. Software frames now render at device scale where needed, so browser output is not blurry on high-density screens. iOS received safe-area and text-layout fixes, plus a fallback for cases where the native GPU path is unavailable.
This release also introduced the server shell and a revised site model. A Pokémon card-store example brings together static pages, SSR routes, signed action forms, progressive workers, browser islands, session-backed state, cache controls, and Docker packaging. The point is to combine static output, server-rendered pages, browser interaction, and typed Fission state without asking you to build a separate web framework around the app.
Packaging and deployment moved forward with Docker images for Static site and SSR projects, artifact manifests, registry publishing, and packaging guides. The CLI is becoming a tool for the full app lifecycle, not just a way to launch a project.
The server shell also needed clear security boundaries. This release added signed server-action forms, runtime security configuration, cache tests, session and island coverage, and guidance for SSR security. Server-side interaction raises the cost of getting a boundary wrong, so the framework needs to make those boundaries visible and controllable.
Fission 0.3.0 brought several important parts of the platform together: real media loading, native capabilities, better Web and iOS rendering, SSR, sessions, browser bridges, Docker packaging, and security guidance.

What this means for developers

Remote media, device access, and server actions all have a failure boundary outside rendering. Exercise those failures as well as success: an image can fail to load, a permission can be denied, and a session-specific page must not enter a public cache. The examples provide integration paths to inspect, not permission to omit the application's own security and recovery rules.