Build the Flutter app. Keep the device beside the code.
Develop Flutter apps in Flame IDE with an integrated mobile preview, Android and iOS device selection, hot reload, project terminals, and AI coding agents.
The Mobile Preview panel displaying Flame Mobile, a native app built with Flutter. The capture uses a recorded app frame and sample workspace data. Select the image to enlarge.
WHY IT HELPS
Keep the next decision in context.
Flutter development is a constant conversation between Dart code and a running app. Flame keeps that loop in one workspace: open the project, choose a device, run the app, and inspect its screen beside your editor. Keep terminal output, Git changes, backend repositories, and AI assistance close when the next fix crosses more than one part of the stack.
Keep the feedback loop visible
Use the full-height Mobile panel beside your editor to inspect the selected device. Interact with supported device controls, then return to the source or terminal without moving the preview into another window.
Choose a real run target
Browse physical and virtual devices, favorite regular targets, and start configured emulators or simulators. The Flutter status bar can use the running Mobile Preview device as a run target once Flutter detects it.
Reload while you iterate
Flutter run controls and Mobile options expose supported app actions, including hot reload. Use hot restart or a full restart when the change needs it, and keep compiler output in the project's terminal.
Keep the rest of the app in reach
Group your Flutter app with its API and shared packages. Use project terminals for Flutter commands, inspect Git changes, and give an AI agent the files and context needed for a focused implementation or fix.
IN YOUR PROJECT TERMINAL
Useful commands for the development loop.
flutter doctor
Check the SDK and target-platform requirements on the computer running Flame.
flutter devices
Verify which devices Flutter currently recognizes before choosing a run target.
flutter pub get
Resolve the Flutter project's package dependencies from its project directory.
flutter run -d <device-id>
Start a debug session on an explicit target from a project terminal when you need command-line control.
flutter test
Run the project's Flutter tests and inspect the results before landing the change.
HOW TO USE IT
A practical starting point.
Prepare Flutter and the target platform
Install the Flutter SDK and make the flutter command available to Flame. Run flutter doctor in a project terminal and resolve the requirements for your target platform. Android needs SDK tooling and a configured emulator or authorized phone. iOS needs a macOS host with Xcode and its command-line tools.
Open the project and Mobile Preview
Open the Flutter repository containing pubspec.yaml. Select Mobile on the right activity bar, then use Devices to choose a connected phone or start a configured virtual device. Use Refresh devices after authorizing a phone or changing SDK tools. Favorites keep frequent targets close.
Select the Flutter run device
In the Flutter status bar device menu, find the Mobile Preview section and select the running preview device. A preview marked Not detected by Flutter is not yet a usable Flutter target. Check flutter devices and the platform setup before starting the app.
Run, change, reload, and inspect
Run the app using Flutter's controls and inspect it beside the editor. Edit Dart code and use the available hot reload action for a debug session. Read build and runtime output in the project terminal. Finish by running relevant tests and checking the Git diff before committing.
REQUIREMENTS & LIMITS
Know what the tool depends on.
The Flutter SDK, Android tooling, Xcode, app dependencies, and signing configuration live on your development host. Flame uses those tools rather than bundling a complete mobile toolchain.
Android device and emulator support depends on the host SDK, authorization, and virtualization setup. iOS Simulator and physical iPhone workflows require macOS and Xcode; installing Flame on Windows does not enable an iOS simulator.
Hot reload requires a running Flutter debug session and does not apply every kind of change. Native platform changes or some initialization changes may require a restart or rebuild.
A decorative phone-frame preset changes the preview shell. It does not change the emulator's actual device profile, screen dimensions, or operating system.
FAQ
Flutter Development: common questions
Yes. Flame detects Flutter projects from pubspec.yaml and provides Flutter device and run controls alongside project terminals, Git, and Mobile Preview. Install and configure the Flutter SDK and platform tools on the host first.
Flame's Flutter controls support hot reload for a running compatible session. Mobile options also exposes Flutter hot reload when available. Flutter requires debug mode, and some changes require hot restart or a full restart.
Yes. Open Mobile, use Devices to select a running Android target or start a configured AVD, and inspect it in the panel. The host needs Android SDK tooling and a working emulator configuration.
No. iOS development and simulator workflows require macOS and Xcode. On Windows or Linux, use supported Android targets and the Flutter targets available on that host.
The device is visible to Mobile Preview, but Flutter has not identified it as a run target. Check flutter devices, wait for startup to complete, confirm SDK setup and authorization, then refresh discovery. An offline or booting device cannot be selected as a Flutter run target.
They serve different workflows. Mobile Preview is the desktop panel for developing and inspecting an app on a device. Flame Mobile is the native companion for controlling supported tools on your Flame workstation from your phone, and will be available soon.