fps_monitor
2.0.0, released 6 years ago by an unverified publisher
On-screen FPS and frame duration monitoring tool for Flutter debug and profile modes.
What it does
Collects per-frame build and raster rendering timings via WidgetsBinding callbacks in debug and profile modes. Displays interactive overlay charts categorizing frames into fluidity levels (smooth, good, slight lag, severe lag). Provides metrics like maximum, average, and total frame durations to help evaluate UI performance.
AI-written summary of version 2.0.0, based on the package's README and metadata. Report an inaccuracy
Use it when
- You need an on-device visual overlay to benchmark frame rendering and detect UI stutter during profile/debug builds.
- You want detailed frame breakdown statistics instead of the raw charts provided by PerformanceOverlay.
- Testing performance specifically on 60Hz display refresh rate devices.
Skip it when
- Monitoring performance in production release builds (it operates only in profile/debug mode).
- Profiling devices with high refresh rates (>60Hz) due to fixed 16.7ms frame duration floor assumptions.
Strengths
- Categorizes frame times into clear color-coded smoothness tiers.
- Built-in overlay UI allows instant inspection of recently recorded frames without external tooling.
- Easy widget-level integration wrapping the app's root builder.
Weaknesses
- Hardcodes frame calculations based on 60Hz display intervals (normalizes frame times < 16.7ms).
- Requires manual overlay state configuration using a global navigator key.
Setup
- Kind
- Flutter widgets
- Effort
- Low
- Code generation
- No
- Direct dependencies
- 0
Requires assigning a GlobalKey<NavigatorState> to MaterialApp to pass overlayState, and wrapping the app root via MaterialApp.builder.
MaterialApp(
navigatorKey: globalKey,
builder: (ctx, child) => CustomWidgetInspector(child: child),
home: const MyHomePage(),
);Alternatives
Packages that do the same job and could replace fps_monitor.
- newrelic_mobile
Provides production-grade performance tracking and analytics rather than local debug overlays.
86Compare