README.md

stream_chat_jaspr example

A chat application built with stream_chat_jaspr. The channel list and message search sit on the left, the active conversation in the middle, and an open thread on the right. Below 1100 px the thread replaces the channel list, and below 760 px the layout collapses to a single pane with a back control.

It is deployed at https://getstream.github.io/stream-chat-jaspr/.

Running

dart pub get
dart run tool/dev.dart

The application is served at http://localhost:8080.

Flag	Effect
--port <n>	Serve on a different port
--host any	Bind every interface so other devices on the network can connect
--release	Optimised build (-O2) with watching disabled
--no-serve	Build only
--output <dir>	Write a publishable directory and exit

--host any prints the LAN addresses it is reachable on, which is the practical way to try the single pane layout on a real phone.

--output assembles the directory that gets published: the compiled bundle and the hand-written assets, without the Dart entrypoint or the compiler's .map and .deps sidecars. .github/workflows/pages.yml runs it on every push to master, gated on dart analyze and the test suite. Because index.html references the bundle relatively and the app has no router, the same output works at a domain root or a repository subpath with no base href.

tool/dev.dart replaces jaspr serve, which cannot resolve on this SDK. See Toolchain constraints in the repository README. The script compiles with dart compile js and rebuilds when any Dart file under lib/, web/, or the component library changes.

Credentials

lib/demo_credentials.dart contains two public sandbox accounts, the same credentials used by the Stream Flutter tutorials.

Account	Application	Contents
Sample app user	s2dxdhpxd94g	Multiple channels with message history
Tutorial user	b67pax5b2wdq	A single flutterdevs channel

These tokens are committed intentionally. They belong to Stream's public demo applications and grant no other access.

In a production application, user tokens must be generated on a server using your API secret. The secret must never be exposed to the browser. See Tokens and authentication.

Project structure

Path	Role
web/index.html	Document shell
web/main.dart	Client entry point, calls runApp
lib/app.dart	Owns the client lifecycle and the active theme
lib/sign_in_page.dart	Demo account picker
lib/chat_shell.dart	Pane layout, channel selection, search, and thread hosting
lib/app_styles.dart	Styles for the application shell
lib/demo_credentials.dart	Sandbox credentials
tool/dev.dart	Build and serve script

Styling inside the chat surface comes from streamChatStyles in the component library. app_styles.dart covers only the sign in screen and the sidebar header.