Getting started

Clone, run, and find your way around in about five minutes.

Requirements

Tool	Version	Notes
Flutter	3.47+	Dart 3.13 comes with it
Xcode	16+	iOS and macOS builds only
Android SDK	34+	Android builds only

Nothing else. No code generation step, no build_runner, no environment file to fill in before the app will start.

Run it

git clone https://github.com/ColorlibHQ/kite-flutter-admin-dashboard
cd kite-flutter-admin-dashboard
flutter pub get
flutter run

Sign in with any email — the field is prefilled and the session is in-memory, so a page reload signs you out again. That is deliberate: see State.

Pinning the SDK

Kite pins Flutter with fvm so local builds match what CI builds. If you use it:

fvm use 3.47.1
fvm flutter run

First things to look at

The Components screenEvery control in the template, live and stateful. The fastest way to see what is here. lib/core/data/The DataProvider contract and the mock adapter. One line swaps it for your backend. lib/kite_ui/The design layer. The one architectural rule lives here.

Try the command palette

Press ⌘K (or Ctrl+K) anywhere. It searches the real data through DataProvider, not a hardcoded list — point Kite at a REST backend and search hits that backend with no work in the palette.

Everyday commands

flutter run -d chrome          # web
flutter run -d macos           # desktop
flutter test                   # 26 tests
flutter analyze                # strict: casts, inference, raw types
dart format .                  # CI checks the whole tree, not just lib/

Run dart format . from the project root, not dart format lib/. CI checks everything including test/, and this is the most common reason a first push fails.