Flight Check is a development time tool for Flutter that lets you preview your app across different mobile device profiles — so you'll know what it looks like without guesswork.
We support a broad range of device profiles covering common screen sizes, device types, and notch type and safe areas sizes.
We use binding-layer emulation, so MediaQuery and safe areas report what a
real device would. And Flight Check is tree-shaken out in release mode, so you
don't ship any unnecessary code.
Add flight_check as a regular dependency:
flutter pub add flight_check
In your main.dart, call FlightCheck.configure(); you want to it before the
call to runApp():
import 'package:flight_check/flight_check.dart';
void main() {
FlightCheck.configure();
runApp(const MyApp());
}Then run your app as a regular Flutter Desktop app on macOS, Linux, or Windows;
the preview UI appears automatically. You can even leave the call to
FlightCheck in unconditionally; when doing a release build Flight Check is
tree-shaken out at compile time.
- Release / profile builds — tree-shaken out at compile time
- iOS / Android devices — skipped at runtime so real-device debug sessions are unaffected
- Flutter Web — excluded via a conditional import
| Device | Size | Device category |
|---|---|---|
| iPhone SE (3rd gen) | 375x667 | Flat-edge, no cutout, small screen — budget / upgrade path |
| iPhone 14 | 390x844 | Notch, 390×844 — covers iPhone 12, 13, 14 |
| iPhone 15 | 393x852 | Dynamic Island, 393×852 — proxy for iPhone 14 Pro, 15 Pro, 16, 16e |
| iPhone 15 Pro Max | 430x932 | Dynamic Island, 430×932 — covers iPhone 15 Plus, 16 Plus |
| iPhone 17 | 402x874 | Current standard iPhone, 402×874 — same geometry as iPhone 17 Pro |
| iPhone 17 Air | 420x912 | Dynamic Island, 420×912 — iPhone 17 Air |
| iPhone 17 Pro | 402x874 | Dynamic Island, 402×874 — covers iPhone 16 Pro, 17 Pro |
| iPhone 17 Pro Max | 440x956 | Largest iPhone screen, 440×956 |
| Google Pixel 7a | 411x914 | Mid-range Pixel, small punch hole — covers Pixel 7a, 8, 8a |
| Google Pixel 10 | 411x923 | Large punch hole, 411×923 — covers Pixel 9 and 10 |
| Google Pixel 10 Pro | 410x914 | High-DPR Pixel (3.125), 410×914 |
| Samsung Galaxy A15 | 411x892 | Budget Samsung Infinity-U notch, 411×892 — covers A15, A25 |
| Samsung Galaxy A16 | 411x892 | Budget Samsung Infinity-U notch, 411×892 — covers A06, A16, M16 |
| Samsung Galaxy A55 | 384x854 | Mid-range Samsung A-series, 384×854 — covers A54, A55 |
| Samsung Galaxy A56 | 412x915 | Mid-range Samsung A-series, 412×915 — covers A36, A56 |
| Samsung Galaxy S25 | 360x780 | Flagship Samsung S25, 360×780 — slightly rounder corners than S24/S26 |
| Samsung Galaxy S26 | 360x780 | Flagship Samsung, 360×780 — covers S24, S26 |
| iPad mini (A17 Pro) | 744x1133 | Compact iPad, 744×1133 |
| iPad (A16) | 820x1180 | Standard iPad, 820×1180 |
| Galaxy S24 | iPhone 17 | Pixel 10 |
|---|---|---|
 |
 |
 |
If your app calls WidgetsFlutterBinding.ensureInitialized(), place the call to
FlightCheck.configure() before the WidgetsFlutterBinding call.
- Font hinting and sub-pixel rendering match the host display, not the emulated device.
- Platform plugins (maps, camera, webviews) receive spoofed
FlutterViewmetrics but their native rendering surfaces are unaffected. - Safe area insets are static per profile; dynamic changes such as keyboard appearance are not emulated.
MediaQuery.devicePixelRatioreflects the derived window DPR rather than the device's nominal DPR; apps that branch on this value may behave differently than on a real device.defaultTargetPlatformis overridden to match the emulated device's platform, giving correct scroll physics, page transitions, and haptic feedback patterns; however, text-field keyboard shortcuts may not match the host keyboard when the host OS and emulated platform differ (e.g. Android on macOS)- back-navigation assumptions (system back button on Android, swipe-back on iOS) cannot be satisfied on desktop
- Flutter Web is not supported.
BSD 3-Clause — see LICENSE.