You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To permit a complete usage of the app in the mobile, I have previously taken the decision to integrate the KeyboardFX usage in my app.
The goal was to workaround 2 problems that was present with the native keyboard :
When focusing a field in the bottom of the screen, the virtual keyboard hides the field.
When clicking in a numeric field, the full keyboard is shown instead a number-only keyboard.
To solve this, I have previously used the KeyboardFX and permits me to :
if the field will be hidden by the keyboard, automatically translate the root layout up when the keyboard is shown to have the field always displayed
If the focused field has the style class "numeric-input", display the number-only keyboard
I have bad feedbacks of my customers about the KeyboardFX :
There is a latency that make the keyboard not easy to use
The keyboard differs from the one they use for all their mobile usage and the found that not confortable
The keyboard is poor in features in comparison to native keyboards
I must to go back to the native keyboard for software acceptance by the customers but the 1st problem is critical for the app usage and the second is major too as they need in some screen to quickly type quantities.
Please, can you improve the keyboard integration ?
I need 2 things :
A way to translate automatically the field to don't stay under the keyboard similar than behaviour visible in other website.
A way to identifiate some fields as number fields and have the number only keyboard in this case : for the moment, I have put a specific style class to indicate fields that are number only for keyboardFX.
Regards,
The text was updated successfully, but these errors were encountered:
Have you started to work about the moving of the content when keyboard appears ?
It's a blocking point for our customers in the acceptation of our app.
Thank you
Hi Guirak,
Sorry for the late response.
We will need time to really focus on this topic to redesign the mobile experience. We will probably find time for it at the beginning of next year.
Hi Florian,
To permit a complete usage of the app in the mobile, I have previously taken the decision to integrate the KeyboardFX usage in my app.
The goal was to workaround 2 problems that was present with the native keyboard :
To solve this, I have previously used the KeyboardFX and permits me to :
I have bad feedbacks of my customers about the KeyboardFX :
I must to go back to the native keyboard for software acceptance by the customers but the 1st problem is critical for the app usage and the second is major too as they need in some screen to quickly type quantities.
Please, can you improve the keyboard integration ?
I need 2 things :
Regards,
The text was updated successfully, but these errors were encountered: