The plugins for IntelliJ IDEA provide a fully integrated development experience in the IntelliJ IDE.
- Installation and setup
- Creating projects
- Editing code, and viewing code problems
- Running and Debugging
- Fast edit and refresh development cycle
- Tips and tricks
Installation and setup
Please follow the IntelliJ setup instructions to install IntelliJ and the Dart and Flutter plugins.
Updates to the plugins will be shipped on a regular basis. You should get prompted in IntelliJ when an update is available.
To check for updates manually:
Open preferences (IntelliJ IDEA>Check for Updates… on macOS, Help>Check for Updates… on Linux).
flutterare listed, update them.
Creating a new project
To create a new Flutter IntelliJ project from the Flutter starter app template:
In IntelliJ, click Create New Project from the ‘Welcome’ window or File>New>Project… from the main IDE window.
Select Flutter in the menu, and click Next.
Enter your desired Project name and Project location.
Creating a new project from existing source code
To create a new Flutter IntelliJ project containing existing Flutter source code files:
- In IntelliJ, click Create New Project from the ‘Welcome’ window or
File>New>Project… from the main IDE window.
- Note: Do not use the New>Project from existing sources… option for Flutter projects.
Select Flutter in the menu, and click Next.
Under Project location enter, or browse to, the directory holding your existing Flutter source code files.
- Click Finish.
Editing code, and viewing code problems
The Dart plugin performs code analysis that enables:
Code completions based on rich type analysis.
Navigating to type declarations (Navigate>Declaration), and finding type usages (Edit>Find>Find Usages).
Viewing all current source code problems (View>Tool Windows>Dart Analysis). Any analysis issues will be shows in the Dart Analysis pane:
Running and Debugging
Running and Debugging is controlled from the main toolbar:
Selecting a target
When a Flutter project is open in IntelliJ, you should see a set of Flutter specific buttons on the right-hand side of the toolbar.
- Locate the Flutter Target Selector drop-down button. This will show a list of available targets. Select the target you want your app to started on.
- When you connect devices, or start simulators, additional entries will appear.
Run app in release mode
- Click the Play icon in the toolbar, or invoke Run>Run.
- The bottom Run pane will show logs output:
Run app in debug mode
If desired, set breakpoints in your source code.
Click the Debug icon in the toolbar, or invoke Run>Debug.
The bottom Debugger pane will show Stack Frames and Variables.
The bottom Console pane will show detailed logs output.
Debugging is based on a default launch configuration. To customize this, click. the drop-down button to the right of the device selector, and select Edit configuration.
Fast edit and refresh development cycle
Flutter offers a best-in-class developer cycle enabling you to see the effect of your changes near instantly.
To edit your code and hot reload changes:
Start your app with ‘Run’ (without breakpoints) or ‘Debug’ (with breakpoints).
Make desired changes in your source code
Do not press the ‘Stop’ button; rather, to see your changes just click the Hot Reload button.
Advanced debugging with Observatory
Observatory is an additional debugging and profiling tool presented with an html-based UI. For details see the Observatory page.
To open Observatory:
Run your app in debug mode.
In the Debug panel at the bottom, click the Stopwatch icon (‘Open Observatory’).
IntelliJ keyboard shortcuts
On Linux (IntelliJ keymap Default for XWin) the keyboard shortcut is CTRL+F5.
On macOS (IntelliJ keymap Mac OS X 10.5+ copy) the keyboard shortcut is ⌘F5, which unfortunately is already mapped to macOS VoiceOver. The Flutter team is working on better default keybindings. For now you can remap the keybinding through the IntelliJ settings as shown below.
Full Application Restart
On Linux (IntelliJ keymaps Default for XWin) the keyboard shortcut is CTRL+Shift+F5.
On macOS (IntelliJ keymap Mac OS X 10.5+ copy) the keyboard shortcut is ⇧⌘F5.
Keyboard mappings can be changed in IntelliJ Preferences/Settings: Select Keymap, then enter flutter into the search box in the upper right corner. Right click the binding you want to change and Add Keyboard Shortcut.
‘Hot Reloads’ vs ‘Full Application Restarts’
Hot Reload works by injecting updated source code files into the running Dart VM (Virtual Machine). This includes not only adding new classes, but also adding methods and fields to existing classes, and changing existing functions. A few types of code changes cannot be hot reloaded though:
Global variable initializers.
Static field initializers.
main()method of the app.
For these changes you can fully restart your application, without having to end your debugging session:
- In the Debug panel at the bottom, click the Full Application Restart button (shown with an icon containing a circular arrow).
Tips and tricks
- JetBrains has a good Keyboard Shortcuts You Cannot Miss overview
- Customize the shortcuts to your preferences in Preferences > Keymap
To navigate quickly in your code:
- Switch between recent files:
ctrl-e(Windows & Linux)
- Navigate between all files:
alt-Home(Windows & Linux)
- Code completions will be shown as you type, or can be invoked at any time with
- IntelliJ code completion matches are per-default case sensitive on the first letter. You can change this in Preferences > Editor > General > Code Completion
Opening a Flutter project in IntelliJ from the terminal:
- Create a terminal config for IntelliJ: In IntelliJ, select Tools > Create Command-line Launcher
- You can now open a project with
idea ., e.g.:
cd <flutter sdk dir>\examples\flutter_gallery` idea .
Tuning the IntelliJ UI setup: Please see this wiki page for tips.
Known issues and feedback
Important known issues that may impact your experience are documented in the Flutter plugin README file.
All known bugs are tracked in the issue trackers:
We very much welcome feedback, both on bugs/issues and feature requests. Prior to filing new issues, please:
do a quick search in the issue trackers to see if the issue is already tracked.
make sure you have updated to the most recent version of the plugin.
When filing new issues, please include the output of