Installing Flutter

What you need

Installing

1. Follow the official guide at docs.flutter.dev/get-started/install for your operating system. A common route is installing VS Code and its Flutter extension, which can download the SDK for you; or download the SDK zip and extract it to a simple path like C:\src\flutter (avoid folders with spaces or that need admin rights, such as Program Files).
2. Add flutter\bin to your PATH, so the flutter command works in any terminal.
3. Install Android Studio and, through its SDK Manager, the Android SDK, command-line tools and an emulator image.
4. Run flutter doctor and fix each item it reports.

flutter --version
flutter doctor
flutter doctor --android-licenses     # accept Android SDK licences (type y)
flutter devices                       # list connected phones and emulators

Reading flutter doctor

[✓] Flutter (Channel stable, 3.x.x, on Microsoft Windows ...)
[✓] Windows Version
[!] Android toolchain - develop for Android devices
    ! Some Android licenses not accepted. To resolve this, run: flutter doctor --android-licenses
[✓] Chrome - develop for the web
[✗] Visual Studio - develop Windows apps
    ✗ Visual Studio not installed; this is necessary to develop Windows apps.
[✓] Android Studio
[✓] Connected device (2 available)

A PATH is the list of folders your terminal searches for commands. If "flutter is not recognized" appears, the flutter\bin folder is not on your PATH, or you need to open a new terminal after changing it.

Running on a phone or emulator

For an Android phone: enable Developer options (tap Build number seven times in About phone), turn on USB debugging, connect with a data cable and accept the prompt. For an emulator: create one in Android Studio's Device Manager. Then flutter devices should list it. iPhones and the iOS Simulator need a Mac with Xcode; that is an Apple requirement.

Channels and upgrades

Flutter has release channels; use stable for real work. flutter upgrade moves you to the newest stable release. Upgrading can change behaviour slightly, so upgrade at the start of a task, not the day before a release, and run your tests after.

Common mistakes

• Installing the SDK in a path with spaces or one that needs admin rights: strange build errors. Use a simple path.
• Forgetting to accept Android licences: builds fail until you run flutter doctor --android-licenses.
• Trying to build iOS apps on Windows: not possible without a Mac.
• Ignoring doctor warnings for the platform you actually need.