Choosing an Editor: VS Code, Android Studio, IntelliJ
You could build Sprout with a plain text editor and the terminal commands from the last two lessons. An editor with Flutter support makes the loop faster: save a file and the app reloads, click in the margin and execution pauses, hover a widget and see its parameters.
The rule
The editor is a choice; the SDK underneath is the same.
All three popular editors talk to the same Flutter SDK and the same project folder. Nothing about Sprout's files changes when a teammate uses a different one.
| Editor | How you add Flutter | Good fit when |
|---|---|---|
| VS Code | Install the Flutter extension (it brings the Dart extension) | You want something light and fast |
| Android Studio | Install the Flutter plugin | You build for Android and want the emulators and Android SDK tools built in |
| IntelliJ IDEA | Install the Flutter plugin | You already use JetBrains tools for other languages |
What they share once set up:
- Hot reload on save, so you rarely press
ryourself. - Debugging: breakpoints, stepping, and inspecting variables.
- Flutter DevTools, including the widget inspector that shows the live widget tree.
- Quick fixes such as "wrap with widget" and "add const".
One practical point: building for Android needs the Android SDK and, for testing, an emulator. Most people install these through Android Studio even when they write code in VS Code. Building for iOS needs a Mac with Xcode, whatever the editor.
The shortcut
Separate the question into what the project needs and what you like.
What the project needs
The Flutter SDK (pinned with FVM), plus a platform toolchain: the Android SDK for Android, Xcode for iOS.
The trap is believing the editor "owns" the project. If a build fails in one editor, check the SDK version and flutter doctor before blaming the editor.
Drills
Answer fast — trust the rule.
Two teammates use VS Code and Android Studio on Sprout. What must match for identical builds?
What gives VS Code its Flutter features?
You code in VS Code and want an Android emulator. What do most people install?
Which editor feature means you rarely type r in a terminal?
Remember
- The editor is a choice; the SDK underneath is the same.
- Split the setup: what the project needs (SDK, platform tools) versus what you like (editor).
- Trap: blaming the editor for problems that come from the SDK or toolchain.