Hierarchy and flow

Fission

Product

▾

Setup

›

The Hierarchy and flow family contains 14 renderer-backed chart variants. Use this page as the entry point for choosing the right variant, then open the variant page for the screenshot, data shape, Rust API notes, and example code.

The chart family is still ordinary Fission UI. Each variant is constructed from typed Rust data, participates in layout and theme decisions, and can be driven by app state, reducers, resources, jobs, or services just like any other widget.

Variants

Chart	Data shape	Use when
Budget treemap	Nested value nodes.	Use it for budget or storage breakdowns.
Circular-like graph	Graph nodes plus edges.	Use it for relationship overview surfaces.
Demand theme river	Time/value/category tuples.	Use it for campaign or demand mix.
Dependency graph	Graph nodes plus edges.	Use it for dependency and topology diagrams.
Energy sankey	Vertex list plus edges.	Use it for material, energy, or revenue flow.
File-system tree	Nested nodes with values.	Use it for product and resource hierarchies.
Org tree	Nested nodes.	Use it for organization and ownership charts.
Product sunburst	Nested value nodes.	Use it for hierarchy depth and composition.
Radial taxonomy	Nested nodes.	Use it when hierarchy symmetry matters.
Revenue sunburst	Nested value nodes.	Use it for nested part-to-whole data.
Service graph	Graph nodes plus edges.	Use it for systems maps and service graphs.
Storage treemap	Nested value nodes.	Use it for disk and memory allocation.
Traffic theme river	Time/value/category tuples.	Use it for composition changing over time.
User-flow sankey	Vertex list plus edges.	Use it for conversion path analysis.

Choosing within this family

Start with the user's question, not the visual effect. Pick the simplest variant that makes the answer clear, add interaction only when it reduces work for the user, and keep animation purposeful enough that it explains a change rather than decorating the page.

Authoring from a Fission component

Use this reference page as the chart expression inside ordinary Fission component conversion. The chart is a Widget, so it can sit inside a Card, Grid, Scroll, responsive page section, or any other layout container.

use fission::prelude::*;
use fission::charts::{Axis, Chart, LineSeries};

pub struct HierarchyAndFlowChart;

impl From<HierarchyAndFlowChart> for Widget {
    fn from(_: HierarchyAndFlowChart) -> Widget {
        Chart::new()
            .title("Hierarchy and flow")
            .x_axis(Axis::category(vec!["A", "B", "C"]))
            .y_axis(Axis::value())
            .series(vec![LineSeries::new("Series").data(vec![1.0, 2.0, 3.0]).into()])
            .into()
    }
}

Keep expensive data loading outside component conversion. A reducer, job, service, or server route should prepare the typed chart data, then the component should read that state and construct the chart deterministically.

Options, accessibility, and diagnostics

Area	What to decide	How to verify
Data shape	Keep source rows in typed Rust structs, then map them into the series type shown in the example.	Unit test the mapping separately from rendering.
Options	Choose axes, legends, labels, animation, and interaction based on the user's task.	Add a screenshot test when changing visual behavior.
Accessibility	Provide a clear title and adjacent summary text for important trends or outliers.	Inspect the generated semantics and make sure the chart is understandable without color alone.
Failure handling	Render an empty, loading, or error state before constructing the chart if data is unavailable.	Test empty data, partial data, and failed fetches.
Performance	Prefer summarized or windowed data for very large datasets; keep full raw history in the data layer.	Profile frame time and interaction latency with representative data volumes.

Variants

Choosing within this family

Authoring from a Fission component

Options, accessibility, and diagnostics

Fission

A cross-platform, GPU-accelerated user interface framework for Rust. MIT licensed.

Ready to use today. Widget APIs are expected to remain stable; some runtime and shell APIs may change before 1.0.0.

GitHub

Quickstart

Reference

Fission 0.7.0