Package selection guidance compiled from public package information, community data, and project usage.
A Flutter plugin that detects the visibility state of the soft keyboard on Android, iOS, and other supported platforms. It provides real-time updates when the keyboard appears or disappears, enabling developers to adjust UI layouts dynamically. Ideal for forms, chat interfaces, and any app requiring responsive design based on keyboard presence. The plugin works across mobile and desktop platforms, ensuring consistent behavior. It integrates seamlessly with Flutter's state management systems.
Use cases
Dynamic form layout adjustment
Chat interface responsiveness
Auto-scrolling to focused fields
Responsive UI during keyboard input
Cross-platform keyboard detection
Key features
Real-time keyboard visibility events
Supports Android, iOS, Web, macOS, Windows, and Linux
Simple stream-based API
Works with all Flutter state management approaches
Lightweight and reliable
Suitable for
Apps with dynamic UI layouts
Form-heavy applications
Chat or messaging apps
Developers targeting multiple platforms
UI/UX optimization teams
Considerations
Requires handling stream subscriptions properly
May need additional logic for complex layouts
Not suitable for non-interactive UI elements
Limited to keyboard visibility, not input method switching
Best used with proper error handling in streams
Original README
Original README snapshot from the linked source repository. Visit the repository for the latest content.
Flutter Keyboard Visibility
React to keyboard visibility changes.
Note about Flutter Web and Desktop support
Web support is an open issue here, desktop support is an open issue here. Currently this library will just return false for keyboard visibility on web and desktop.
Build your Widget tree based on whether or not the keyboard is visible by using KeyboardVisibilityBuilder.
import'package:flutter_keyboard_visibility/flutter_keyboard_visibility.dart';
/// In any of your widgets...@overrideWidgetbuild(BuildContext context) {
returnKeyboardVisibilityBuilder(
builder: (context, isKeyboardVisible) {
returnText(
'The keyboard is: ${isKeyboardVisible ? 'VISIBLE' : 'NOT VISIBLE'}',
);
}
);
Option 2: Within your Widget tree using a provider
Build your Widget tree based on whether or not the keyboard is
visible by including a KeyboardVisibilityProvider near the top
of your tree.
import'package:flutter_keyboard_visibility/flutter_keyboard_visibility.dart';
// Somewhere near the top of your tree...@overrideWidgetbuild(BuildContext context) {
returnKeyboardVisibilityProvider(
child: MyDemoPage(),
);
}
// Within MyDemoPage...@overrideWidgetbuild(BuildContext context) {
finalbool isKeyboardVisible = KeyboardVisibilityProvider.isKeyboardVisible(context);
returnText(
'The keyboard is: ${isKeyboardVisible ? 'VISIBLE' : 'NOT VISIBLE'}',
);
}
Option 3: Direct query and subscription
Query and/or subscribe to keyboard visibility directly with the
KeyboardVisibilityController class.
Place a KeyboardDismissOnTap near the top of your Widget tree. When a user taps outside of the currently focused Widget, the Widget will drop focus and the keyboard will be dismissed.
import'package:flutter_keyboard_visibility/flutter_keyboard_visibility.dart';
// Somewhere near the top of your tree...@overrideWidgetbuild(BuildContext context) {
returnKeyboardDismissOnTap(
child: MyDemoPage(),
);
}
By default KeyboardDismissOnTap will only dismiss taps not captured by other interactive Widgets, like buttons. If you would like to dismiss the keyboard for any tap, including taps on interactive Widgets, set dismissOnCapturedTaps to true.
import'package:flutter_keyboard_visibility/flutter_keyboard_visibility.dart';
// Somewhere near the top of your tree...@overrideWidgetbuild(BuildContext context) {
returnKeyboardDismissOnTap(
dismissOnCapturedTaps: true,
child: MyDemoPage(),
);
}
The IgnoreKeyboardDismissWidget can be used to further refine which taps do and do not dismiss the keyboard. Checkout the example app for more detail.
Testing
Testing using mocks
KeyboardVisibilityProvider and KeyboardVisibilityBuilder accept a controller parameter that allow you to mock or replace the logic for reporting keyboard visibility updates.
@GenerateMocks([KeyboardVisibilityController])
voidmain() {
testWidgets('It reports true when the keyboard is visible', (WidgetTester tester) async {
// Pretend that the keyboard is visible.var mockController = MockKeyboardVisibilityController();
when(mockController.onChange)
.thenAnswer((_) => Stream.fromIterable([true]));
when(mockController.isVisible).thenAnswer((_) => true);
// Build a Widget tree and query KeyboardVisibilityProvider// for the visibility of the keyboard.bool? isKeyboardVisible;
await tester.pumpWidget(
KeyboardVisibilityProvider(
controller: mockController,
child: Builder(
builder: (BuildContext context) {
isKeyboardVisible =
KeyboardVisibilityProvider.isKeyboardVisible(context);
returnSizedBox();
},
),
),
);
// Verify that KeyboardVisibilityProvider reported that the// keyboard is visible.expect(isKeyboardVisible, true);
});
}
Testing with a global override
Call KeyboardVisibilityTesting.setVisibilityForTesting(false); to set a custom value to use during flutter test. This is set globally and will override the standard logic of the native platform.