-
-
Notifications
You must be signed in to change notification settings - Fork 107
feat: KeyboardExtender
#982
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Images automagically compressed by Calibre's image-actions ✨ Compression reduced images by 46.2%, saving 13.58 KB.
205 images did not require optimisation. |
📊 Package size report
|
ab5a457
to
b11f5df
Compare
Images automagically compressed by Calibre's image-actions ✨ Compression reduced images by 46.2%, saving 13.58 KB.
205 images did not require optimisation. |
|
The latest updates on your projects. Learn more about Argos notifications ↗︎
|
fdf95fc
to
7cff86c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
documentation
Improvements or additions to documentation
e2e
Anything about E2E tests
enhancement
New feature or request
KeyboardExtender 🧩
Anything about keyboard extending (i. e. `KeyboardExtender` component)
🚨 requires API changes 🚨
Changes that requires changes in library API
tests
You added or changed unit tests
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
📜 Description
Added
KeyboardExtender
component.💡 Motivation and Context
This is a part of a big research that I did over several months.
This PR implements
KeyboardExtender
component. On iOS it utilizes native capabilities of the OS and on Android it uses polyfill (KeyboardBackgroundView
+KeyboardStickyView
+useKeyboardAnimation
foropacity
animation).That component aims to help developers to build various keyboard extensions which will be shown above the keyboard and visually mimic to it. The initial idea of implementation was inspired by Revolut app:
IMG_3374.MP4
And the
KeyboardExtender
ideally fits for building such things, another example is:And I think developers can take inspiration and build even more advanced features (such as voice search etc.)
To implement this on iOS I used UIInputView with keyboard style.
Warning
On iOS 26 it looks bad and the view is not getting embedded into the keyboard. See tweet about it. For now let's wait for Apple fixes and if they are not going to fix it, then most likely we'll have to write separate implementation for iSO 26 to use liquid glass design.
On Android I'm trying to re--create iOS effect, but it's obviously not possible to match it fully, so I'm trying to make it looking as close as possible to. For sure I can not fully hide the view and make it moving together with keyboard from the very beginning, so I decided to use
opacity
interpolation and always show it above the keyboard (usingKeyboardStickyView
).Last but not least - for now I decided to make this component very simple and barely customizable (I expose only
enabled
property). And it can cause certain issues, for example if you switch between QWERTY keyboard (where you don't wantKeyboardExtender
to be present) to numeric (where you'd like to seeKeyboardExtender
), then you will see how react updates everything asynchronously and for a fraction of a second you will see QWERTY-keyboard withKeyboardExtender
. Theoretically I could introduce binding throughnativeID
and "connect" specific inputs with specific extenders, but for now let's not do an over-engineering and try to handle all cases. Let's handle everything step-by-step and when we get a bug report then we can do another round of investigation how such thing can be implemented 👀📢 Changelog
Docs
KeyboardExtender
;Components Overview
;KeyboardExtender
feature inREADME
;E2E
KeyboardExtender
;JS
KeyboardExtender
component;KeyboardExtender
spec;KeyboardExtender
mock.iOS
KeyboardExtender
view;C++
KeyboardExtender
;🤔 How Has This Been Tested?
Tested manually on:
📸 Screenshots (if appropriate):
Simulator.Screen.Recording.-.iPhone.16.-.2025-06-23.at.13.43.22.mov
Screen.Recording.2025-06-23.at.13.32.59.mov
📝 Checklist