Examples

The smallest complete Fission app loop, plus a modal, checkbox, text input, selector, animation requests, and a small custom canvas example.

Open this example when you specifically want to study typed actions and reducers, selector-backed view model, and modal overlay and animation wiring. The goal is not to copy the crate line for line. The goal is to see how one question is solved in a running app that already matches the real runtime.

A broad survey of the built-in widget surface, useful when you want to see how common controls, overlays, and data widgets already behave.

Open this example when you specifically want to study layout, input, navigation, and feedback widgets, and semantic tree and screenshot checks. The goal is not to copy the crate line for line. The goal is to see how one question is solved in a running app that already matches the real runtime.

The focused proving ground for text input, comboboxes, menus, modal focus, and input method editor-sensitive flows.

Open this example when you specifically want to study single-line and multiline editing, combobox overlay teardown, and modal text flow and focus handling. The goal is not to copy the crate line for line. The goal is to see how one question is solved in a running app that already matches the real runtime.

A product-like mail app that exercises portals, theme switching, locale switching, routing, and host capabilities in one shell.

Open this example when you specifically want to study translation bundles and locale sync, OPEN_URL host capability flow, and drawer and overlay-heavy navigation. The goal is not to copy the crate line for line. The goal is to see how one question is solved in a running app that already matches the real runtime.

Proves `TerminalView`, timer-driven polling, and clipboard-sensitive keyboard flows for a long-lived embedded session.

Open this example when you specifically want to study long-lived session state, timer resource polling, and copy and paste behavior. The goal is not to copy the crate line for line. The goal is to see how one question is solved in a running app that already matches the real runtime.

The deepest example in the repo: custom editing surface, jobs, timers, portals, terminal panel, and extensive live tests.

Open this example when you specifically want to study custom render node path, resource-driven jobs and timers, and command palette, menus, hover interactions, and tabs. The goal is not to copy the crate line for line. The goal is to see how one question is solved in a running app that already matches the real runtime.

Combines chart widgets with the current 3D embed path through `Scene3D`.

Open this example when you specifically want to study chart series and dataset surface, and Scene3D embed example. The goal is not to copy the crate line for line. The goal is to see how one question is solved in a running app that already matches the real runtime.

Shows runtime-owned opacity, translation, scale, rotation, clip, and scroll-linked motion in isolation.

Open this example when you specifically want to study stable widget IDs, and Transition widget and raw animation requests. The goal is not to copy the crate line for line. The goal is to see how one question is solved in a running app that already matches the real runtime.

Exercises the bundled Material icon set and gives you a fast visual pass over available icon assets.

Open this example when you specifically want to study bundled icon assets, and gallery-style inspection. The goal is not to copy the crate line for line. The goal is to see how one question is solved in a running app that already matches the real runtime.

A minimal app that isolates the host-backed video embed contract and its rendered surface placeholder.

Open this example when you specifically want to study video registration, bounded embed layout, and surface display op test. The goal is not to copy the crate line for line. The goal is to see how one question is solved in a running app that already matches the real runtime.

A minimal app that proves WebView registration, explicit embed sizing, and deterministic surface rendering.

Open this example when you specifically want to study web state registration, explicit embed size, and surface display op test. The goal is not to copy the crate line for line. The goal is to see how one question is solved in a running app that already matches the real runtime.

A minimal app that isolates the Scene3D custom embed path inside ordinary Fission layout.

Open this example when you specifically want to study custom embed payload, bounded 3D viewport, and surface display op test. The goal is not to copy the crate line for line. The goal is to see how one question is solved in a running app that already matches the real runtime.

The checked-in WebAssembly and browser host path, plus the clearest reference for generated web launcher folders.

Open this example when you specifically want to study wasm-pack build script, and browser host bootstrap. The goal is not to copy the crate line for line. The goal is to see how one question is solved in a running app that already matches the real runtime.

The checked-in host path for Android emulator and iOS simulator packaging and launch around shared app code.

Open this example when you specifically want to study shared mobile runtime host, test control port forwarding on Android, and generated host-folder reference. The goal is not to copy the crate line for line. The goal is to see how one question is solved in a running app that already matches the real runtime.