Flutter Production Setup for Every Platform in 2026

Flutter 3.41 (February 2026) is the latest stable release, bundled with Dart 3.11, and getting the installation right from day one makes a real difference. Broken PATH variables, missing Android SDK command-line tools, and CocoaPods failures on Apple Silicon are the three problems that consume hours of developer time every week. None of them should catch you by surprise.

This guide covers the exact commands and configuration for macOS, Windows, and Linux, with a focus on the professional workflow used in production teams. It also covers integrating Shorebird for over-the-air updates from the start of a project, not as an afterthought. macOS remains the only platform that can target all six Flutter output formats (iOS, Android, web, macOS desktop, Windows via cross-compilation, and Linux), which is why it's the dominant choice for mobile development shops.

---

System requirements across all platforms

Flutter's SDK weighs roughly 2.8 GB on disk, but a realistic production setup, including Android SDK, emulator images, and an IDE, requires 10 GB or more of free space. The official docs don't specify a hard RAM floor, but community consensus and practical experience put the minimum at 8 GB, with 16 GB strongly recommended when running Android emulators or iOS simulators alongside an IDE.

Every platform requires Git 2.x as a prerequisite. On macOS, Git ships with Xcode Command-Line Tools. On Windows, install Git for Windows. On Ubuntu, sudo apt-get install git handles it. Verify with git --version before proceeding.

Here's a quick rundown of the requirements for each platform:

Requirement	macOS	Windows	Linux (Ubuntu LTS)
OS version	macOS 10.15 Catalina through macOS 26 Tahoe	64-bit Windows 10 or 11	64-bit Debian-based or Fedora
Disk space	10 GB+ recommended	10 GB+ recommended	10 GB+ recommended
RAM	8 GB min, 16 GB ideal	8 GB min, 16 GB ideal	8 GB recommended
Git	Via Xcode CLI tools	Git for Windows	apt-get install git
Additional	Xcode, CocoaPods	Visual Studio 2022+ (for desktop)	curl, unzip, xz-utils, zip, libglu1-mesa

Flutter bundles the Dart SDK, so no separate Dart installation is needed.

One thing worth noting: the documentation site currently references Flutter 3.38.6 in many pages, while the actual latest stable is 3.41. Always use the stable channel for production work. Four stable releases are planned for 2026.

---

macOS installation

macOS setup is the most complex of the three platforms because it's the only one supporting both iOS and Android development simultaneously. The single biggest architectural decision is whether you're on Apple Silicon (M1/M2/M3/M4) or Intel, because Homebrew install paths, Ruby environments, and emulator image choices all differ between the two.

Installing the Flutter SDK

The fastest method is Homebrew:

brew install --cask flutter

Homebrew automatically selects the correct architecture. On Apple Silicon, Homebrew lives at /opt/homebrew/. On Intel, it's at /usr/local/.

If you prefer manual installation, download the architecture-specific zip from the Flutter SDK archive. Apple Silicon uses the flutter_macos_arm64_*.zip bundle and Intel uses flutter_macos_*.zip.

Once downloaded, extract the zip to a development directory:

mkdir -p ~/develop
unzip ~/Downloads/flutter_macos_arm64_3.41.0-stable.zip -d ~/develop/

For manual installs, add Flutter to your PATH. Since macOS defaults to zsh (since Catalina), edit ~/.zshrc:

export PATH="$HOME/develop/flutter/bin:$PATH"

For bash users, add the same line to ~/.bash_profile. Apple Silicon users also need Homebrew's shell environment configured:

eval "$(/opt/homebrew/bin/brew shellenv)"

Intel users must substitute /usr/local/bin/brew. You can verify your Flutter CLI installation with the which flutter and flutter --version commands.

Xcode and iOS toolchain

Install Xcode from the Mac App Store (Flutter 3.38+ fully supports Xcode 26 and iOS 26), then run these commands in sequence:

xcode-select --install
sudo sh -c 'xcode-select -s /Applications/Xcode.app/Contents/Developer && xcodebuild -runFirstLaunch'
sudo xcodebuild -license accept
xcodebuild -downloadPlatform iOS

CocoaPods: the Apple Silicon pain point

CocoaPods remains required for Flutter plugins that use native iOS/macOS code, and it's the single most common source of build failures on Apple Silicon.

Install CocoaPods via Homebrew:

brew install cocoapods

The system Ruby shipped with macOS (2.6.x) is typically too old. If the above doesn't work, install a modern Ruby first and then install CocoaPods via gem:

brew install ruby
echo 'export PATH="/opt/homebrew/opt/ruby/bin:$PATH"' >> ~/.zshrc
source ~/.zshrc
gem install cocoapods

If you encounter ffi gem errors on Apple Silicon, run sudo gem install ffi. Rosetta 2 may still be needed for some edge-case components, which you can install by running sudo softwareupdate --install-rosetta --agree-to-license.

A word of caution: never use sudo gem install with the system Ruby. It can corrupt future macOS updates.

A notable 2025/2026 development worth knowing about is that Swift Package Manager is now supported as an alternative to CocoaPods for Flutter plugins, documented in the Flutter Swift Package Manager guide.

---

Windows and Linux installation

Windows 10/11 setup

After installing Git for Windows, the Flutter team recommends the VS Code quick-install path: install VS Code, add the Flutter extension, open the Command Palette (Ctrl+Shift+P), type Flutter: New Project, and VS Code will prompt you to download the SDK and add it to PATH automatically.

For manual installation, download the latest .zip from the Flutter SDK archive and extract it to a path without spaces or special characters. Never use C:\Program Files\. A good choice is %USERPROFILE%\develop\:

Expand-Archive -Path $env:USERPROFILE\Downloads\flutter_windows_3.41.0-stable.zip -Destination $env:USERPROFILE\develop\

To add Flutter to your path, configure PATH through System Properties → Advanced → Environment Variables. Edit the Path user variable and add C:\Users\{username}\develop\flutter\bin. Move this entry to the top of the list, then close and reopen all terminal windows to apply the change.

Three Windows-specific gotchas trip up nearly every developer.

First, Windows Defender scanning Flutter's hundreds of thousands of small files causes severe performance degradation. Add exclusions for the Flutter SDK directory and the pub cache (%LOCALAPPDATA%\Pub\Cache):

Add-MpExclusion -ExclusionPath "C:\Users\{username}\develop\flutter"

Second, Developer Mode must be enabled for building Windows apps with plugins (Settings → Privacy & Security → For Developers → Developer Mode: On).

Third, for Windows desktop development, you need Visual Studio 2022+ with the "Desktop development with C++" workload. This is Visual Studio, not VS Code, and it's a common source of confusion.

Linux (Ubuntu LTS) setup

Start by installing the required dependencies:

sudo apt-get update -y && sudo apt-get upgrade -y
sudo apt-get install -y curl git unzip xz-utils zip libglu1-mesa

The simplest method to install Flutter is via snap:

sudo snap install flutter --classic

For a manual install, download the .tar.xz from the SDK archive and extract:

mkdir -p ~/develop
tar -xf ~/Downloads/flutter_linux_3.41.0-stable.tar.xz -C ~/develop/

Then add Flutter to your PATH:

echo 'export PATH="$HOME/develop/flutter/bin:$PATH"' >> ~/.bashrc
source ~/.bashrc

For Linux desktop development, additional packages are required as documented in the Flutter Linux desktop setup guide:

sudo apt-get install clang cmake git ninja-build pkg-config libgtk-3-dev liblzma-dev libstdc++-12-dev

Never run Flutter commands with sudo on Linux. It creates permission issues that are genuinely painful to unwind.

---

Android SDK setup

Regardless of your operating system, the Android toolchain is where most flutter doctor failures occur.

Start by installing the latest Android Studio from the Android Studio download page. During the setup wizard, Android Studio installs the base SDK, but the wizard does not install everything Flutter needs.

Open the SDK Manager (Tools → SDK Manager, or from the welcome screen: More Actions → SDK Manager) and configure two tabs:

In the SDK Platforms tab, install the platform for API Level 36 (Android 16).

In the SDK Tools tab (this is the critical step that most guides gloss over), make sure all four of these are checked:

• Android SDK Command-line Tools (latest), the number one most common missing component
• Android SDK Build-Tools (latest)
• Android SDK Platform-Tools (includes adb)
• Android Emulator

Click Apply and confirm. Without the command-line tools specifically, flutter doctor will fail with: cmdline-tools component is missing.

Environment variables for the Android SDK

Set ANDROID_HOME and add platform-tools to PATH. The default SDK locations differ by OS.

macOS (~/.zshrc):

export ANDROID_HOME="$HOME/Library/Android/sdk"
export PATH="$PATH:$ANDROID_HOME/platform-tools"
export PATH="$PATH:$ANDROID_HOME/cmdline-tools/latest/bin"
export PATH="$PATH:$ANDROID_HOME/emulator"

Windows (System Environment Variables):

• Variable: ANDROID_HOME = C:\Users\{username}\AppData\Local\Android\Sdk
• Add to PATH: %ANDROID_HOME%\platform-tools and %ANDROID_HOME%\cmdline-tools\latest\bin

Linux (~/.bashrc):

export ANDROID_HOME="$HOME/Android/Sdk"
export PATH="$PATH:$ANDROID_HOME/platform-tools"
export PATH="$PATH:$ANDROID_HOME/cmdline-tools/latest/bin"

After configuring the SDK, accept all Android licenses:

flutter doctor --android-licenses

Type y at each prompt. This step is mandatory before Flutter can build any Android app.

---

Shorebird belongs in your initial setup, not as an afterthought

Shorebird, founded by Flutter creator Eric Seidel, enables over-the-air code push, sending Dart code updates directly to users' devices without App Store or Play Store review cycles.

Installing it alongside Flutter from day one avoids the common "retrofit under pressure" scenario where teams scramble to add OTA capability while rushing to fix a production bug. Patches are tied to exact release versions, so having Shorebird configured early prevents version-matching headaches down the road.

Installation commands

macOS / Linux:

curl --proto '=https' --tlsv1.2 https://raw.githubusercontent.com/shorebirdtech/install/main/install.sh -sSf | bash

Windows (PowerShell):

Set-ExecutionPolicy RemoteSigned -scope CurrentUser
iwr -UseBasicParsing 'https://raw.githubusercontent.com/shorebirdtech/install/main/install.ps1' | iex

Shorebird installs to ~/.shorebird/bin and automatically adds itself to PATH. It also installs a private copy of Flutter inside ~/.shorebird/bin/cache/flutter. This is Shorebird's modified Flutter for code push and should not be added to your PATH. The total installation size is approximately 300 MB.

Verify the installation by running:

shorebird --version
shorebird doctor

The shorebird doctor output checks connectivity to Shorebird's API, console, OAuth, storage, and CDN endpoints, and verifies that the Flutter installation is correct. A clean output looks like this:

✓ https://api.shorebird.dev OK
✓ https://console.shorebird.dev OK
✓ Shorebird is up-to-date
✓ Flutter install is correct
No issues detected!

The core workflow from there is straightforward: shorebird login authenticates via Google OAuth, shorebird init initializes your project and creates shorebird.yaml with your app ID, shorebird release android or shorebird release ios creates a release, and shorebird patch android/ios pushes OTA updates. The shorebird create command also scaffolds new projects with OTA, CI/CD, and release tooling baked in from the start.

Shorebird is purely CLI-driven and works seamlessly alongside the standard Flutter and Dart VS Code extensions.

---

VS Code configuration for Flutter development

Install the Flutter extension (ID: Dart-Code.flutter) from the VS Code marketplace. It automatically installs the Dart extension (Dart-Code.dart-code) as a dependency. These two extensions provide debugging, hot reload, widget inspector, code completion, refactoring, and snippets.

After installation, open the Command Palette and run Dart: Use Recommended Settings to apply sensible defaults, or add these to your settings.json:

{
    "[dart]": {
        "editor.formatOnSave": true,
        "editor.formatOnType": true,
        "editor.rulers": [80],
        "editor.selectionHighlight": false,
        "editor.wordBasedSuggestions": "off",
        "editor.tabCompletion": "onlySnippets"
    },
    "editor.codeActionsOnSave": {
        "source.fixAll": true
    },
    "debug.internalConsoleOptions": "openOnSessionStart"
}

A few shortcuts worth committing to memory: F5 starts debugging, Ctrl+F5 / Cmd+F5 triggers hot reload, Ctrl+Shift+F5 performs a hot restart, and Ctrl+. / Cmd+. opens quick-fix actions for wrapping or extracting widgets. Creating a new project goes through the Command Palette: Flutter: New Project → select Application → choose directory → enter name.

---

Reading flutter doctor output and fixing common errors

Run flutter doctor -v (verbose mode) after completing setup. The command checks eight categories: Flutter SDK, Android toolchain, Xcode (macOS only), Chrome, Android Studio, VS Code, connected devices, and network resources. Each line is prefixed with one of three symbols:

Symbol	Meaning	Action needed
[✓]	Passed	None
[!]	Warning	May need attention, development often still works
[✗]	Error	Must fix before building for that platform

A fully healthy macOS output looks like this:

[✓] Flutter (Channel stable, 3.41.1, on macOS 26.2 25C56 darwin-arm64, locale
    en-IN) [605ms]
    • Flutter version 3.41.1 on channel stable at
      /Users/<username>/development/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 582a0e7c55 (5 days ago), 2026-02-12 17:12:32 -0800
    • Engine revision 3452d735bd
    • Dart version 3.11.0
    • DevTools version 2.54.1

[✓] Android toolchain - develop for Android devices (Android SDK version 36.1.0)
    [1,702ms]
    • Android SDK at /Users/<username>/Library/Android/sdk
    • Platform android-36-ext19, build-tools 36.1.0
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 26.2) [1,475ms]
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.16.2

[✓] Chrome - develop for the web [7ms]
[✓] Connected device (3 available) [7.2s]
[✓] Network resources [6.8s]

• No issues found!

The most frequently encountered errors and their fixes:

flutter: command not found means Flutter is not in PATH. Re-add the export PATH=... line to the correct shell config file (~/.zshrc, ~/.bashrc, or Windows Environment Variables) and restart your terminal.

cmdline-tools component is missing means you need to open Android Studio → Tools → SDK Manager → SDK Tools tab → check "Android SDK Command-line Tools (latest)" → Apply.

Android license status unknown is fixed by running flutter doctor --android-licenses and accepting each license with y.

Unable to find bundled Java version happens because newer Android Studio versions renamed the jre directory to jbr. On macOS, create a symlink: cd "/Applications/Android Studio.app/Contents" && ln -s jbr jre. This issue is resolved in recent Flutter and Android Studio combinations, but persists if either is outdated.

CocoaPods failures on Apple Silicon typically mean you're using system Ruby instead of Homebrew Ruby. Run which ruby and confirm it shows /opt/homebrew/opt/ruby/bin/ruby, not /usr/bin/ruby. Reinstall CocoaPods via brew install cocoapods if needed.

Lock file errors during pub get are resolved by running flutter clean, then flutter pub cache repair, then flutter pub get. If the problem persists, delete pubspec.lock and retry.

"No devices available" means either no emulator is running, no physical device is connected, or platform support isn't enabled. Start an emulator from Android Studio's Device Manager or run flutter emulators --launch with an available emulator name.

---

Wrapping up

The 2026 Flutter installation process has matured considerably. The VS Code quick-install path now handles SDK download and PATH configuration in one step, and Swift Package Manager offers a welcome alternative to the historically fragile CocoaPods dependency chain.

Three setup decisions matter most for production teams: choosing Homebrew on macOS (it handles architecture differences automatically), installing Android SDK Command-line Tools explicitly via SDK Manager (the universal failure point that no automated wizard handles for you), and integrating Shorebird from project inception rather than retrofitting it under deadline pressure.

Run flutter doctor -v and shorebird doctor after every installation step. If both report no issues, your environment is production-ready.