KeyboardObserver
A Swift library that simplifies iOS keyboard event handling by replacing NotificationCenter with a typed event-based API.
What is KeyboardObserver?
KeyboardObserver is a Swift library that simplifies keyboard event handling in iOS applications. It replaces the traditional NotificationCenter approach with a clean, event-based API that automatically extracts keyboard properties like frame, duration, and animation curve from notifications. This eliminates the boilerplate code typically required for observing keyboard events and makes the implementation more maintainable.
iOS developers building applications that need to respond to keyboard show/hide events, particularly those working with text input interfaces who want cleaner code than NotificationCenter provides.
Developers choose KeyboardObserver because it dramatically reduces the complexity of keyboard event handling, provides type safety, eliminates manual observer management, and makes code more readable compared to raw NotificationCenter usage.
Overview
For less complicated keyboard event handling.
Use Cases
Best For
- Adjusting UI layout when keyboard appears/disappears
- Creating smooth keyboard animations in iOS apps
- Simplifying keyboard event handling in Swift projects
- Reducing boilerplate code for keyboard observers
- Building text-heavy interfaces with dynamic content adjustment
- Replacing NotificationCenter-based keyboard handling with cleaner APIs
Not Ideal For
- iOS applications built exclusively with SwiftUI, as KeyboardObserver relies on UIKit APIs and requires bridging
- Projects already using reactive frameworks like RxSwift or Combine, where keyboard events can be integrated natively without an additional library
- Teams seeking a drop-in solution with pre-built UI adjustments; KeyboardObserver only provides event data, not animation or layout logic
Pros & Cons
Pros
The README shows a direct comparison where KeyboardObserver replaces multiple lines of NotificationCenter setup with a single observe call, significantly reducing code complexity.
Uses structured types like KeyboardEvent and KeyboardEventType, making code less error-prone by avoiding manual parsing of notification dictionaries, as highlighted in the features.
Observer instances automatically stop observing when deinitialized, preventing memory leaks without the need for manual removal, which is a key advantage over raw NotificationCenter.
Provides a closure-based approach that improves readability and maintainability compared to selector-based notification methods, as demonstrated in the usage example.
Cons
Designed for UIKit, so integrating with SwiftUI requires additional bridging code, limiting its usefulness in modern iOS development where SwiftUI is prevalent.
While it simplifies event handling, developers must still write custom animation and layout code to respond to keyboard events, as seen in the example where insets are manually adjusted.
The README is brief and lacks detailed examples for edge cases or advanced scenarios, potentially forcing developers to rely on source code or trial and error.
Frequently Asked Questions
Related Projects
IQKeyboardManagerCodeless drop-in universal library allows to prevent issues of keyboard sliding up and cover UITextField/UITextView. Neither need to write any code nor any setup required and much more.
TPKeyboardAvoidingA drop-in universal solution for moving text fields out of the way of the keyboard in iOS
IHKeyboardAvoidingIHKeyboardAvoiding is an elegant solution for keeping any UIView visible when the keyboard is being shown - no UIScrollView required!
TypistSwift UIKit keyboard manager for iOS apps.
Found a gem we're missing?
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.