flutter/demos

This repo is for unmaintained code that supports talks, blogs, and other experiments.

149

stars

369

commits

Dart

primary language

Aug 27, 2026

updated

README

Dash Demos

This repo is for code that supports talks, blogs, and experiments.

NOTE: This code is provided for demonstration purposes only. The code is unmaintained, and may not work with newer releases. Demos may get removed when they are no longer in focus.

CI

This repository has CI in the case that you want to test your demo code against the three Flutter channels. CI is not required to merge code, it's simply here as a convenience. It's run every night at midnight, and when you make a PR.

To add your code to CI:

  1. For each Flutter channel, you'll find a CI file in the /tool dir called flutter_ci_script_stable, flutter_ci_script_beta, and flutter_ci_script_master. Open the file(s) that correspond to the channel you want to test your code against.

  2. Add the directory name of your project to this array:

declare -ar PROJECT_NAMES=(
  # add projects here
)

_archive

Projects can be moved here when they're no longer useful. This is purely cosmetic, and really only signals to readers that you no longer care about this code.

Contributors

khanhnwin

177 commits

ericwindmill

41 commits

jwill

39 commits

domesticmouse

26 commits

flutter/demos

This repo is for unmaintained code that supports talks, blogs, and other experiments.

149

stars

369

commits

Dart

primary language

Aug 27, 2026

updated

README

Dash Demos

This repo is for code that supports talks, blogs, and experiments.

NOTE: This code is provided for demonstration purposes only. The code is unmaintained, and may not work with newer releases. Demos may get removed when they are no longer in focus.

CI

This repository has CI in the case that you want to test your demo code against the three Flutter channels. CI is not required to merge code, it's simply here as a convenience. It's run every night at midnight, and when you make a PR.

To add your code to CI:

  1. For each Flutter channel, you'll find a CI file in the /tool dir called flutter_ci_script_stable, flutter_ci_script_beta, and flutter_ci_script_master. Open the file(s) that correspond to the channel you want to test your code against.

  2. Add the directory name of your project to this array:

declare -ar PROJECT_NAMES=(
  # add projects here
)

_archive

Projects can be moved here when they're no longer useful. This is purely cosmetic, and really only signals to readers that you no longer care about this code.

Contributors

khanhnwin

177 commits

ericwindmill

41 commits

jwill

39 commits

domesticmouse

26 commits

Languages

Dart

87.0%

HTML

3.4%

C++

2.9%

CMake

2.3%

TypeScript

1.6%