Run the example app

Every component in the catalog, on a simulator, in about five minutes and with no backend.

Neon Kicks is the example app in the repository. It has two screens worth knowing about: a scripted shop with five registered actions covering every risk level, and a component gallery that draws all twenty-one catalog blocks from fixtures.

The gallery is the fastest way to see what this product actually renders. It is completely offline — no API, no key, no model — so it runs the moment the package resolves.

git clone https://github.com/neon-apps/rendel.git
cd rendel/sdk/flutter/rendel/example
flutter run

Open the gallery from the app bar. Every block is drawn by the real renderer through ComponentRegistry.build, which is the same path a live thread takes, so what you are looking at is what a thread shows.

The token switch

The gallery's app bar toggles between RendelTheme.paper() and RendelTheme.deep(). It is there because the SDK has no dark mode of its own — it has the role map you hand it — so both maps have to be looked at before you map your own. See Map your brand to the catalog.

Talking to a real copilot

The shop screen needs a key and an API. Point it at your own app with two defines:

flutter run \
  --dart-define=RENDEL_KEY=rd_pk_test_yourapp_... \
  --dart-define=RENDEL_API=https://api.rendel.ai

Without them it defaults to a local seed key against http://localhost:3200, which only resolves against a stack you are running yourself.

You do not need any of this to try the product. The console's Test page holds a real conversation on your app's test key from the browser, with no build and no simulator.