Skip to content

Example apps

Fluvie ships a set of small, kitten-themed example apps under examples/. Each one exercises a different way to turn a Fluvie composition into a real MP4, so together they cover every rendering path. They share one cohesive look through the examples/kitten_kit package (theme, sample media, and reusable composition builders), so each app stays tiny.

AppWhat it showsRenders with
galleryThe twelve lessons and the scrubbable inspectorCLI (desktop) and the server (web)
cli_quickstartInstall the CLI and render from the terminalfluvie_cli
desktop_studioA Linux desktop studio that renders to a filefluvie_cli, in-process
mobile_purrfectAn Android app that renders on the phonefluvie_mobile_encoder
web_browser_studioA meme maker that renders in the browserfluvie_web_encoder (ffmpeg.wasm)
web_server_studioA promo studio that renders on a serverfluvie_server

A tiny project with one composition and a capture harness. Render it with the CLI and you get an MP4.

Terminal window
cd examples/cli_quickstart
dart run fluvie_cli:fluvie render whisker_standup --out build/whisker.mp4

Pick a template, then render it to a file. The app shells out to the CLI.

Terminal window
cd examples/desktop_studio
flutter run -d linux

Name your cat, optionally add a photo, and render a birthday card on the device. Nothing leaves the phone.

Terminal window
cd examples/mobile_purrfect
flutter run -d android

Renders fully in the browser with ffmpeg.wasm, no backend. Vendor the wasm core once, then run.

Terminal window
cd examples/web_browser_studio
bash tool/fetch_ffmpeg.sh
flutter run -d chrome

Customize a promo and render it on a Fluvie render server. Point it at a running server (see Rendering on a server).

Terminal window
cd examples/web_server_studio
flutter run -d chrome --dart-define=FLUVIE_API_URL=http://localhost:8080

The twelve lessons plus the inspector. Run it from the repo root so its render button can find the CLI.

Terminal window
cd examples/gallery
flutter run

Each app is verified end to end in CI: the build compiles, unit tests cover the view-models and services, and a real render produces an MP4 that is probed for a valid video stream. The web apps print a FLUVIE_E2E_RESULT marker the headless harness reads; the desktop and mobile apps assert the written file. See Testing.