Conversation

Replying to and
I wonder if better UX would be allowing easy bypass of the error, but: 1. showing site as insecure 2. disabling all cookies/localstorage for the site 3. disabling form entry/submission for the site 4. severe warning or blocking [executable] file download from site
2
Replying to and
FWIW, Hacker's Keyboard can do this. I don't like it as a default keyboard but it has a few nice features. I think long pressing the menu button does it for the AOSP keyboard and Gboard but phones don't include physical buttons anymore, let alone the menu button.
1
1
Kinda similar to how AOSP has generic support for undo / redo in standard widgets like text fields, but most keyboards don't provide an undo / redo button and the ctrl-z / ctrl-shift-z keybinds aren't exposed via most virtual keyboards in their layout since they don't offer ctrl.
1
1
Replying to and
All the Android keyboards are so bad. I use an abandoned one called multiling. That and hacker's are least-bad. A good one would provide blank keycaps matching compact pc physical layout and let you apply any xkb layout file on top of it.
1
1
Replying to and
It's unfortunate that Google stopped developing their keyboard (Gboard now) as an enhancement to the open source AOSP keyboard project. They've made massive improvements which would have been included in it and it serves as the basis for most of the alternate keyboard projects.
2
Replying to and
It's support for alternate input methods in general. It covers the input method (typing on keys, swipe, more complex methods for other languages), suggestions, spelling correction, clipboard management (no longer allowed to be done by other apps) and approaches to multi-language.
2
1
There are keyboards supporting configuring the layout. AOSP keyboard has internal support for it but doesn't expose much of it. AnySoftKeyboard exposes a lot of functionality for this, but it suffers from offering too much configuration without actually being a good keyboard.
1
Originally, the only real difference between it and Google Keyboard was that the Google Keyboard version provided a library for mapping swipe patterns to possible inputs. AOSP keyboard supported swipe, but the library for doing the mapping was proprietary and not included.
1
They eventually forked away from it and it eventually ended up becoming Gboard which has a ton of improvements. It has a lot of nice things like moving the cursor by swiping on the keyboard and way better suggestions, auto-correction, multi-language support at the same time, etc.
1
Show replies